Markdown presentation layer used to build documentation and demonstration pages with enhanced visual and interactive blocks.

Wider project ecosystem that can use FrontMark as a documentation and lightweight frontend publishing layer. Its generator, runtime, contracts and deployment model remain outside the FrontMark documentation scope.

Responsibility boundary where FrontMark turns Markdown source into rendered documentation surfaces without becoming the source of truth for generated application behavior.

Markdown extended with visual blocks, tabs, tables, admonitions, media embeds and publishing components.

Temporary presentation version used to validate positioning, navigation, content structure and rendering before a more complete release.

Astro documentation framework used as the base for the documentation section, sidebar, page layout and build integration.

Static site framework powering the project build, routes, Markdown collections and frontend components.

Documentation syntax and design reference that FrontMark follows for many Markdown patterns, including admonitions, tabs, annotations, icons and code blocks.

Metadata block at the top of a Markdown file. It defines values such as title, description and tags.

Public URL generated from a source file. For example, src/content/docs/forms.md is published as /docs/forms/.

Navigation entry declared in astro.config.mjs. FrontMark sidebar items can include labels, links and icon names.

Inline icon reference such as :material-alert-outline: or :simple-n8n:. Shortcodes are resolved through configured Iconify icon sets.

Callout block created with syntax such as !!! note "Title". It highlights notes, tips, warnings, examples and related content.

Numbered inline marker that points to an explanatory note. It is useful for adding context without interrupting the main paragraph.

Tabbed content block used to group related snippets, alternatives or platform-specific instructions in one compact area.

Triple-backtick block that declares a language or special renderer, such as js, mermaid, chart, form, hexa or asciinema.

Code fence intercepted by FrontMark and rendered as a richer component instead of plain code, for example charts, forms, hexadecimal viewers or n8n workflows.

Full-width Markdown section with configurable background, mask, spacing, transition or animation options.

Layered visual section where images move at different speeds to create depth during scrolling.

Grid layout for feature lists, references and compact navigation cards.

Markdown table used to compare features, list parameters or present structured reference information.

Rendered visual description of a process, architecture or relationship. FrontMark supports Mermaid and Kroki-style diagram fences.

Data visualization rendered from Markdown code fences. Chart examples include Chart.js, Vega-Lite and mind map blocks.

Markdown-authored form rendered from a form code fence with fields, validation, choices and submission behavior.

FrontMark block that displays text or file content as hexadecimal output for inspection and debugging.

Copyable workflow JSON block rendered from an n8n or n8n-workflow code fence.

Terminal recording format used to embed command-line sessions in documentation.

Media embed syntax for YouTube or local videos, with layout options such as full-width or centered display.

Bottom toolbar that lets visitors switch between English, French and Spanish. The English Markdown source remains the canonical content.

Bottom toolbar control that changes the reading size of documentation text.

Generated data used by tag pages and tag navigation. It is refreshed by the tag build script.

Content management interface included with the site for future editorial workflows around Markdown content.

PNG logo asset with an alpha channel. Its background is transparent so the mark can sit cleanly on dark, light or gradient surfaces.