v 0.4.0
de en

Inline Demos

DocEngine allows you to place JSON tags inside your markdown files to embed inline demos into your documents.

The purpose of inline demos is to show your users features and examples of the documented entity right beside your descriptive texts.

Besides of displaying a visual example and letting users peek into the source code, the inline demo element also allows users to modify the predefined sources in a sandboxed environment so they can play around with your examples to get a better understanding.

Inline demo security

Inline demos can only serve static resources. You cannot create demos that incorporate any kind of serverside language like PHP or Ruby. If you list such files in a demo block, their plain source will be served to the user.

Editable inline demos will create a fresh sandbox instance on every pageload. This means that any changes a user makes in the demo will be discarded when he reloads the page or navigates away.

Sandboxes are tied to a users browser session. This way its impossible to access other people's sandboxes.

Embedding an inline demo

First, prepare a folder with all the assets needed for your demo in a subfolder of docs/demos/. You are free to decide about the folder structure inside your demos folder so it fits the best to the kind of documentation you write.

Here's an example of a inline demo:

To embed a inline demo into your markdown element, you simply use a JSON block inside your markdown file, describing the settings of your demo element.

For the above demo, we used the following JSON block:

    "target": "en/inlineDemoExample/",
    "display": [
    "links": {
        "An Outlink": "http://google.com"
    "notice": "I can even show a dismissable notice!",
    "editable": true

First, you specify the target folder where your demo data is stored. We created a subfolder for each language inside our demos folder to provide demos in multiple languages. Keep in mind that the inline demo presenter always looks for a index.html inside your target folder to display it as the result document.

The display array specifies which files from the folder should be displayed to the user in a source window.

You can define one or more outbound links in the links object. Use the object key as the label text of the button and the value for the URL.

If you want to display a little notice inside the demo (for example what to do to trigger an action), set the notice property with a string. The notice is displayed on top of the demo view and can be dismissed with a click.

The editable property defines if a user should be able to modify the displayed code in the source windows, or not. In order to make editable demos work, you need to make sure that docEngine has write access to the lib/cache/ folder.