Syntax testing ExL for fun

Heading 1 Level

This is heading 1: ##.

Heading 2 Level

This is heading 2: ###.

Heading 3 Level

This is heading 3: ####.

Heading 4 Level

This is heading 4: #####.

Heading 5 Level

This is heading 5: ######.

####### Heading 6 Level

This is heading 6: #######.

Code block tabs

console.log("hello");

print("hello")

These files/URLs these reference at the bottom of this article.

See the Google.

See the Validation article.

See the Hidden guide

Using the Google works well for common searches.

Relative link: [See Acrolinx](/docs/authoring-guide-exl/using/authoring/style-guide/acrolinx.html?lang=en){target="_blank"}

Absolute link: [See Adobe](https://www.adobe.com){target="_blank"}

HTML: <a href="https://www.adobe.com" target="_blank">Adobe in new tab</a>

Relative link: See Acrolinx

Absolute link: See Adobe

HTML: Adobe in new tab

Loose URLs

http://www.google.com

http://www.google.com

SVG file

svg star

Block quote

This is a block quote. What happens?

link to Ad Specs PDF

Note Rendering

We support Note, Tip, Important, Caution, and Warning. New tags include Prerequisites, Admin, and Availability.

Note

NOTE

This is a standard NOTE block.

Tip

TIP

This is a standard tip.

Important

IMPORTANT

This is an important note.

Warning

WARNING

This is a warning.

Caution

CAUTION

This is a caution.

Admin

ADMINISTRATION

This is an admin note. EXL only.

Availability

AVAILABILITY

This is an availability note. EXL only.

Prerequisites

PREREQUISITES

This is a Prerequisites note. EXL only.

Escaping characters

$

$

$

$

${USER_ID}

&lbrack;Brackets&rbrack;

[Brackets]

&lbrace;Braces&rbrace;

\[Brackets\]

[Brackets]

Escape test

*Bob*

_Bill_

[Nancy]

(Esmerelda)

<Variable>

# Biff

+ Hank

- Clarice

. Period

! Exclamation

& Ampersand

TarMK Online indexing with oak-run.jar in heading

Testing 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.

Unescaped brackets

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.

Task List

Not supported in AEM pipeline; no longer supported in EXL.

  • [x] Write the press release
  • [ ] Update the website
  • [ ] Contact the media

Code Blocks

Code block sloppiness

  1. Step 1

    This is line 1 of the javascript
47

  2. Step 2.

  3. Step 3.

Code block line numbering

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>

Misc Syntax

Emoji

Looks like this is ignored.

That is so funny! 😂

😃

Abbreviation

<abbr title="Hyper Text Markup Language">HTML</abbr>

Not supported in our HTML validation

Container

here be dragons

Strikethrough

Not supported in AEM pipeline.

I like Corona Dos Equis beer.

HTML: Donald TrumpJoe Biden is POTUS.

Redline

I like <del>soccer</del> <ins>football</ins>.

Not supported in our HTML validation

Definition lists

Looks like this is ignored.

First Term
This is the definition of the first term.

<dl>Definition list</dl>

Not supported in our HTML validation

Footnote

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.

Logo alt text

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.
}

Syntax that breaks in AEM pipeline

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.

Admonitions

Table Test

XDM type MongoDB Aerospike Protobuf 2
String string String string
Double double Double double
Long long Integer int64
Integer int Integer int32
Short int Integer int32
Byte int Integer int32
Date date Integer
(Unix milliseconds)		 int64
(Unix milliseconds)
DateTime timestamp Integer
(Unix milliseconds)		 int64
(Unix milliseconds)
Boolean bool Integer
(0/1 binary)		 bool
Map object map map<key_type, value_type>
XDM type JSON Schema Example
String 
{"type": "string"}
 "Platinum"
Double 
{"type": "number"}
 12925.49
Long 
{
  "type": "integer",
  "maximum": 9007199254740991,
  "minimum": -9007199254740991
}
 1478108935
Integer 
{
  "type": "integer",
  "maximum": 2147483648,
  "minimum": -2147483648
}
 24906290
Short 
{
  "type": "integer",
  "maximum": 32768,
  "minimum": -32768
}
 15781
Byte 
{
  "type": "integer",
  "maximum": 128,
  "minimum": -128
}
 90
Date* 
{
  "type": "string",
  "format": "date"
}
 "2019-05-15"
DateTime* 
{
  "type": "string",
  "format": "date-time"
}
 "2019-05-15T20:20:39+00:00"
Boolean 
{"type": "string"}
 true

See the Google

Using the Google works well for common searches.

See the Validation article.

See the Hidden guide

  1. This is the first footnote. ↩︎

On this page