Which Markdown specification is used in Pushword — CommonMark, GFM, or something else?
The default Markdown implementation in Pushword is based on CommonMark, with a few customizations designed to make it easy to switch between Markdown and a WYSIWYG block editor.
The difference is almost invisible — your usual Markdown syntax will continue to work as expected.
Markdown content is parsed block by block, rather than as a single document. Blocks are separated by two blank lines.
Attributes can be defined using the syntax {#attribute-name}, placed on a separate line just before the Markdown block it applies to. This is conflicting with Prettier Markdown.
Advanced content types such as galleries, attachments, or page lists are supported through Twig functions.
You can use twig syntax inside markdown inline code or markdown code block, it will not be parsed by twig. If you want to use twig inside inline code or code block, use html directly (<pre></pre>).
Two filters expose the parser in templates:
{{ text|markdown }} — full block-level rendering (paragraphs, headings, lists, tables…). The output is wrapped in block tags: a one-liner becomes <p>…</p>.{{ text|markdown_inline }} — inline-only rendering, for text injected inside existing markup (a component lede, a caption, a subtitle): <p class="lede">{{ lede|markdown_inline }}</p>. Links, emphasis, inline code, strikethrough, {attributes} and Pushword inline shortcodes render exactly as with markdown, but no block tag is ever emitted. Block syntax (#, -, >, tables…) stays literal text, and blank lines don’t create paragraphs — meant for one-line inputs.Both filters mark their output HTML-safe and pass raw inline HTML through as-is.
Consecutive blocks can be wrapped in a single <div> by placing an opening and a closing tag as blocks of their own (blank-line separated). The markdown between the two lines is rendered normally — CommonMark passes the wrapper through as-is:
<div id="pricing" class="grid md:grid-cols-2">
## Plan A
## Plan B
</div>
The block editor shows the pair as Group markers carrying the anchor and the classes; the markers are inserted and deleted together. It only claims a <div> line whose attributes are id and/or class — anything richer stays a Raw block.
A group can wrap its blocks in a collapsible block instead of a <div> — the Collapsible checkbox on the Group marker, or the call written by hand:
{{ startShowMore('itinerary', 'mt-8') }}
## Day 1
## Day 2
{{ endShowMore() }}
#itinerary) and to remember that the reader opened it. Omitted, it is derived from the page slug, so it stays the same from one render to the next.{{ startShowMore(showMoreExtraClass: 'mt-8') }}.endShowMore() takes the gradient classes fading the cut-off text, when the page background is not white: {{ endShowMore('via-gray-100 to-gray-100') }}./component/show_more.html.twig — override it in your theme to restyle the button or the fade.An older spelling, <!--start-show-more--> / <!--end-show-more-->, still renders the same and still shows up as a Group in the editor. It carries neither id nor class: pw:show-more:convert rewrites it to the call above.
A blockquote whose first line is a > [!label] marker renders as a notice — the syntax DocFX introduced and GitHub adopted, with Obsidian’s tolerance: the label is case-insensitive, and a title may follow it on the same line.
> [!warning] Version
>
> Last updated: August 2026. Corrections welcome via [GitHub issues](/contribute).
note, tip, important, warning and caution ship with a palette; any other label (sponsored, deprecated…) renders neutral and is yours to style — the wrapper always carries notice notice-<label>.[!note] → “Note”), so the level never rests on colour alone.{#anchor .class} line placed above the notice applies to it, as for any block. It can also close the marker line — > [!warning] Version {#version} — the way a heading takes its anchor; write both and they merge./component/notice.html.twig: override it in your theme to change the palette, add icons, or drop the wrapper entirely.A blockquote that does not open with a marker stays a plain blockquote, so quoting someone is unaffected.
A label can own a template of its own: > [!faq] renders through /component/notice/faq.html.twig when the site defines one, and through the generic notice otherwise. That turns the marker into the Markdown syntax for any block-level component whose content is editorial — a FAQ entry, a definition, a step — without a Twig include and its quoted parameters in the middle of the page:
> [!faq] Can luggage be carried between night stops? {#carry-luggage}
>
> Wherever a road serves the night stop, yes — it works on the Tour du Mont-Blanc.
>
> It does not on high-altitude refuges, where you carry what you sleep with.
The template receives the same variables as the generic notice — title (the text after the label), content (the body, already rendered), id, class — plus params, the other attributes of the {…} line, so {#carry-luggage tag="h2"} reaches it as params.tag. The body being ordinary Markdown is the point: links stay [text](/url), paragraphs stay paragraphs, and the text is reviewable in a diff.
Multi-field components (a call-to-action with a title, a button label and a URL) do not fit a title-plus-body shape: use a snippet and its parameter schema for those.
Standard GFM table syntax is supported. You can merge cells horizontally using -> as the cell content — it merges into the preceding cell via colspan.
| Service | Identifiant | -> |
| --------------- | ----------- | -------------- |
| Authentication | auth | oauth.provider |
Renders as a table where “Identifiant” spans two columns. Multiple -> cells can follow each other to span more columns.
Note: -> in the first cell of a row has no effect (no preceding cell to merge into).
Per-column alignment uses the GFM delimiter row: :--- (left), :--: (center), ---: (right). The block editor’s column menu writes these markers for you.
| Name | Price | Qty |
| :---- | ----: | :--: |
| Apple | 1.20 | 3 |
Add the {.table-sticky-header} block attribute on the line before a table to pin its heading row while scrolling (in the editor and on the front). The block editor’s “Sticky heading” toggle adds it for you.
{.table-sticky-header}
| Col 1 | Col 2 |
| ----- | ----- |
| Val | Val 2 |
{#example-content}
## Example Content
{#mainParagraph}
This is a paragraph.
{#mainGallery}
{{ gallery(['piedweb-logo.png', '1.jpg', '2.jpg', '3.jpg']) }}
Rendered text gets locale-aware typography — smart quotes ("…" becomes « … » in French, “…” in English, „…“ in German), curly apostrophes (l'ami → l’ami), ellipsis (... → …), dimensions (30 x 40 → 30 × 40), (c) (r) (tm), and the French non-breaking spaces before : ; ! ?. Dashes are never touched.
The sources stay plain ASCII: the characters above only exist in the rendered HTML, applied by the Typography entity filter after markdown rendering. pre, code, script, style, svg and comments are left untouched, and the flat export straightens any typographic quote or non-breaking space that found its way into a page, so .md files remain greppable and diff-friendly.
Disable it per page with filter_typography: 0 in the front matter, or per site by overriding the filters config key.