This is a block quote. What happens?
We support Note, Tip, Important, Caution, and Warning. New tags include Prerequisites, Admin, and Availability.
This is a standard NOTE block.
This is a standard tip.
This is an important note.
This is a warning.
This is a caution.
This is an admin note. EXL only.
This is an availability note. EXL only.
This is a Prerequisites note. EXL only.
[Brackets]
[Brackets]
{Braces}
\[Brackets\]
[Brackets]
Escape test
*Bob*
_Bill_
[Nancy]
(Esmerelda)
<Variable>
# Biff
+ Hank
- Clarice
. Period
! Exclamation
& Ampersand
These are currently work in AEM pipeline, but there are questions about ExL pipeline.
Rendered (note on two lines):
Note on two lines.
>[!NOTE]
>Note on two lines.
Rendered (note above tip):
Note on three lines, no spaces, above TIP.
Tip on three lines, no spaces, below TIP.
>[!NOTE]
>
>Note on three lines, no spaces, above TIP.
>[!TIP]
>
>Note on three lines, no spaces, below NOTE.
oak-run.jar
in headingTesting inline code in a heading. This renders in ExL. But it doesn’t look right. Perhaps we should render inline code as a monospace font, no color, preserve font size.
In AEM pipeline, using [1] instead of [1]
or [1] or [1 ] renders improperly, and the square brackets must be escaped.
What happens to [1] in ExL pipeline? Looks like it renders as is.
Not supported in AEM pipeline; no longer supported in EXL.
Step 1
This is line 1 of the javascript
47
Step 2.
Step 3.
Turned off because no {#value}
syntax allowed in code blocks.
<html>
<head>
<title>Adobe Document Cloud View SDK Sample</title>
<meta charset="utf-8"/>
</head>
<body style="margin: 0px">
<div id="adobe-dc-view"></div>
<script src="https://documentcloud.adobe.com/view-sdk/main.js"></script>
<script type="text/javascript">
document.addEventListener("adobe_dc_view_sdk.ready", function()
{
var adobeDCView = new AdobeDC.View({clientId: "<YOUR_CLIENT_ID>", divId: "adobe-dc-view"});
adobeDCView.previewFile(
{
content: {location: {url: "https://documentcloud.adobe.com/view-sdk-demo/PDFs/Bodea Brochure.pdf"}},
metaData: {fileName: "Bodea Brochure.pdf"}
});
});
</script>
</body>
</html>
Emoji
Looks like this is ignored.
That is so funny! 😂
Strikethrough
Not supported in AEM pipeline.
I like Corona Dos Equis beer.
HTML: Donald TrumpJoe Biden is POTUS.
Definition lists
Looks like this is ignored.
Image with hover text
Hover text is currently rendered improperly (centered, with hover text as heading) in AEM pipeline. In EXL, we need to support it after cutover. Right now, we strip it out.
Syntax highlighting
Language is ignored in AEM pipeline.
JSON lowercase
{
"firstName": "John",
"lastName": "Smith",
"age": 25
}
JSON uppercase
{
"firstName": "John",
"lastName": "Smith",
"age": 25
}
JAVASCRIPT (both javascript and js)
{
"firstName": "John",
"lastName": "Smith",
"age": 25
}
{
"firstName": "John",
"lastName": "Smith",
"age": 25
}
JAVA (both java and JAVA)
{
"firstName": "John",
"lastName": "Smith",
"age": 25
}
{
"firstName": "John",
"lastName": "Smith",
"age": 25
}
Nonsense language
{
"firstName": "John",
"lastName": "Smith",
"age": 25
}
Italics to indicate variable (javascript)
{
Congratulations, <i>yourname</i>!
You have won.
}
Footnotes
Footnote syntax is ignored.
Here’s a simple footnote.[1]
Superscript
E=mc2
Horizontal line
---
(not supported)
Underlines
This is underlined text.
Accordions
Accordions in HTML (<details>
) work, but we have them turned off for now until we can fully support them.
This is the first footnote. ↩︎