MarkBind Syntax Overview
[_User Guide → MarkBind Syntax Overview_](markBindSyntaxOverview.html)A MarkBind source file may contain a mix of several popular syntax schemes used in creating web pages. MarkBind source file can be as simple as basic Markdown, and you can use progressively more complicated syntax to create progressively more sophisticated Web pages while optimizing other aspects such as content reuse.
Given below is an overview of the syntax schemes supported by MarkBind.
Exact usage of various MarkBind syntax is described in separate sections such as User Guide → Formatting Contents
MarkBind supports all basic Markdown syntax.
MarkBind supports additional Markdown features provided by GitHub-Flavored Markdown (GFMD).
MarkBind adds several Markdown-like features on top of GFMD.
Given below are some examples of custom syntax added by MarkBind.
Nunjucks variables are ideal for reusing small bits of code in multiple places; you can define a variable to represent the code bit in question and reuse it anywhere in the site by referring to the variable instead of duplicating the code bit.
MarkBind has a powerful <include> mechanism which allows you to create documents by combining other content fragments.
MarkBind provides a number of components (e.g., expandable panels, tabbed displays, navigation bars, etc.) that you can use to enhance the appearance/behavior of your pages.
A MarkBind source file can contain a mixture of HTML, JavaScript, and CSS as a normal web page would.
MarkBind has Vue.js components built on the popular BootStrap framework. Much of Bootstrap's features are supported in and out of these components as well. However, interactive BootStrap components like dismissible alerts and toasts are not supported.
Nunjucks is a JavaScript based templating tool. Here is a simple example:
CODE:
<ul>
{% for item in [1, 2, 3, 4] %}
<li>Item {{ item }}</li>
{% endfor %}
</ul>
OUTPUT:
As MarkBind uses Nunjucks behind the scene, MarkBind is generally compatible with Nunjucks, which means you can use Nunjucks templating in your source files. Note that the code is processed for Nunjucks syntax before the rest of the MarkBind syntax are processed.
Here is the footnote. Footnotes will appear at the bottom of the page.
Here's one with multiple blocks.
Subsequent paragraphs are indented to show that they belong to the previous footnote.
Inline notes are easier to write, since you don't have to pick an identifier and move down to type the note.