Page-level Configuration Reference

2026-07-16T00:00:00+00:00

This page documents the [extra]</code> front-matter keys Tapestry reads on individual pages (e.g. content/about.md</code>, a blog post). These override their site-level</a> equivalents where noted. For Zola's own standard front matter (title</code>, description</code>, date</code>, updated</code>, authors</code>, draft</code>, weight</code>, slug</code>, path</code>, template</code>, insert_anchor_links</code>, [taxonomies]</code>, and so on), see Standard Zola front matter</a> at the bottom of this page.

sidebar</code>#</a> </h2> +++ title = "My Page" # [extra] # sidebar = "sidebar-snippet.md" # custom content # sidebar = false # force off +++</code></pre> The single-article template's columns 9–12 sidebar region is content-driven, not unconditionally reserved: Left unset, a sidebar renders automatically once the page has 2 or more headings, as an "on this page" table of contents.</li> Set to a string, that path is loaded as a colocated Markdown snippet (relative to the page's own directory) and rendered into the sidebar instead of/alongside the auto TOC.</li> Set to false</code>, no sidebar renders regardless of heading count or a custom snippet, and the article reclaims the full 12 columns.</li> </ul> stylesheets</code>#</a> </h2> +++ [extra] stylesheets = ["css/one-off-page-style.css"] +++</code></pre> Additive with the site- and section-level stylesheets</code> — see site-configuration.md</a>. All three levels' stylesheets are linked together, not just the most specific one. katex</code>#</a> </h2> +++ [extra] katex = true +++</code></pre> Overrides the site- and section-level katex</code> setting for this page only — see site-configuration.md</a> for the full precedence chain. An explicit true</code>/false</code> here always wins over whatever is set at the section or site level. social_media_image</code>#</a> </h2> +++ [extra.social_media_image] path = "share-card.png" alt_text = "A diagram of the proposed architecture." +++</code></pre> path</code> is a colocated image (relative to the page's own directory), automatically resized to 1200×675 and emitted as og:image</code> / twitter:card</code> meta tags.</li> alt_text</code> is optional but recommended; it becomes og:image:alt</code>.</li> If unset, the page falls back to the section-level social_media_image</code> (see section-configuration.md</a>), if any.</li> </ul> </div> copy_button is inert extra.copy_button</code> is a leftover terminus key. Tapestry deliberately ships no copy-to-clipboard JavaScript (per CONSTITUTION.md §2), so setting it here or at the section/site level is a silent no-op. </div> </section> Quick reference#</a> </h2> Key</th> Type</th> Default</th> Notes</th></tr></thead> sidebar</code></td> string | bool</td> auto (TOC if ≥2 headings)</td> Custom snippet path, or false</code> to force off.</td></tr> stylesheets</code></td> array of paths</td> []</code></td> Additive with section/site level.</td></tr> katex</code></td> bool</td> inherited</td> Overrides section/site level for this page.</td></tr> social_media_image.path</code></td> path</td> unset</td> Colocated image, resized to 1200×675 for og:image</code>.</td></tr> social_media_image.alt_text</code></td> string</td> unset</td> og:image:alt</code>.</td></tr> copy_button</code></td> bool</td> —</td> Inert (terminus leftover).</td></tr> </tbody></table> Standard Zola front matter#</a> </h2> Keys like title</code>, description</code>, date</code>, updated</code>, authors</code>, draft</code>, weight</code>, slug</code>, path</code>, template</code>, insert_anchor_links</code>, and [taxonomies]</code> are standard Zola front matter, not Tapestry-specific — see Zola's own page content documentation</a> for the full reference. Section-level Configuration Reference 2026-07-16T00:00:00+00:00 This page documents the [extra]</code> front-matter keys Tapestry reads on a section's _index.md</code> (e.g. content/docs/_index.md</code>, content/archive/_index.md</code>). Some of these override their site-level</a> equivalents; others are section-specific. For Zola's own standard section front matter (title</code>, description</code>, sort_by</code>, paginate_by</code>, template</code>, redirect_to</code>, transparent</code>, and so on), see Standard Zola front matter</a> at the bottom of this page. framed</code>#</a> </h2> +++ [extra] framed = true +++</code></pre> Adds a framed</code> class to the section header. Used by the front page, section listing, and archive templates. section_path</code>#</a> </h2> +++ [extra] section_path = "docs/_index.md" +++</code></pre> Used by the front-page (index.html</code>) and archive templates to pull posts from a different section than the one the template is attached to — e.g. your homepage _index.md</code> can list posts from content/docs/</code> without being that section itself. On the archive template, this defaults to /blog/_index.md</code> if unset — a fallback path used only when your site has no such section and doesn't set section_path</code> explicitly. max_posts</code>#</a> </h2> +++ [extra] max_posts = 5 +++</code></pre> Front-page only: caps how many posts from the section named by section_path</code> are listed. Defaults to that section's own paginate_by</code>, or all of its pages if paginate_by</code> is unset. stylesheets</code>#</a> </h2> +++ [extra] stylesheets = ["css/section-style.css"] +++</code></pre> Additive with the site- and page-level stylesheets</code> — see site-configuration.md</a>. katex</code>#</a> </h2> +++ [extra] katex = true +++</code></pre> Sets the KaTeX default for every page in this section (and its subsections), unless a page overrides it directly — see site-configuration.md</a> for the full precedence chain. social_media_image</code>#</a> </h2> +++ [extra.social_media_image] path = "section-share-card.png" alt_text = "A photo representing this section." +++</code></pre> Same behaviour as the page-level key (see page-configuration.md</a>) — used as the og:image</code> fallback for any page in this section that doesn't set its own. </div> copy_button is inert extra.copy_button</code> is a leftover terminus key with no effect under Tapestry — see page-configuration.md</a> for why. </div> </section> Quick reference#</a> </h2> Key</th> Type</th> Default</th> Notes</th></tr></thead> framed</code></td> bool</td> false</code></td> Adds a framed</code> class to the section header.</td></tr> section_path</code></td> path</td> /blog/_index.md</code> (archive only)</td> Section to pull posts from (front page, archive).</td></tr> max_posts</code></td> integer</td> section's paginate_by</code>, or all pages</td> Front-page post-count cap.</td></tr> stylesheets</code></td> array of paths</td> []</code></td> Additive with page/site level.</td></tr> katex</code></td> bool</td> inherited</td> Default for pages in this section.</td></tr> social_media_image.path</code></td> path</td> unset</td> Fallback og:image</code> for pages in this section.</td></tr> social_media_image.alt_text</code></td> string</td> unset</td> og:image:alt</code> fallback.</td></tr> copy_button</code></td> bool</td> —</td> Inert (terminus leftover).</td></tr> </tbody></table> Standard Zola front matter#</a> </h2> Keys like title</code>, description</code>, sort_by</code>, paginate_by</code>, paginate_reversed</code>, template</code>, page_template</code>, redirect_to</code>, transparent</code>, insert_anchor_links</code>, and [taxonomies]</code> are standard Zola section front matter, not Tapestry-specific — see Zola's own section content documentation</a> for the full reference. Site-level Configuration Reference 2026-07-16T00:00:00+00:00 This page documents every setting Tapestry reads from the [extra]</code> table of your site's config.toml</code>, as defined in the theme's own theme.toml</code>. For Zola's own built-in configuration keys (base_url</code>, title</code>, [markdown]</code>, taxonomies, and so on), see Standard Zola configuration</a> at the bottom of this page. Identity & branding#</a> </h2> header_logo</code>, header_title</code>, and the brand-mark fallback#</a> </h3> [extra] header_title = "My Research Site" # header_logo = "images/logo/logo.svg"</code></pre> The header renders exactly one of the following, in this priority order: header_logo</code> — an image (including SVG), if set.</li> header_title</code> — plain text, if header_logo</code> is unset.</li> Tapestry's own brand mark — an inlined SVG, used only when neither of the above is set. config.title</code> is still included as screen-reader-only text alongside the mark.</li> </ol> Setting header_logo</code> always takes priority — header_title</code> is ignored entirely once a logo image is present. favicon</code> and favicon_emoji</code>#</a> </h3> [extra] favicon = "images/logo/logo-01-woven-monogram-square.svg" # favicon_emoji = "🔬"</code></pre> These are mutually exclusive: if favicon</code> is set, it is used and favicon_emoji</code> is ignored outright, regardless of whether favicon_emoji</code> is also set. SVG favicons are linked directly (rel="icon" type="image/svg+xml"</code>).</li> Raster favicons additionally get a 180×180 apple-touch-icon</code> generated automatically when the source is a PNG.</li> favicon_emoji</code> is embedded as an inline SVG data:</code> URI containing the emoji as text — no image file needed. Stick to plain emoji characters here; the value is interpolated into the data URI without escaping, so characters like "</code> or #</code> will break it.</li> </ul> copyright</code>#</a> </h3> [extra] copyright = "© $YEAR $AUTHOR :: Powered by [Zola](https://www.getzola.org) :: [Tapestry](https://github.com/anirbanbasu/tapestry) theme."</code></pre> $YEAR</code> is replaced with the current year (wrapped in a <time></code> element).</li> $AUTHOR</code> is replaced with config.author</code> (empty string if unset).</li> The string is split on the literal delimiter ::</code>; each segment becomes its own </code> (so they can wrap/stack independently on narrow screens), and each segment is rendered as inline Markdown — links, emphasis, etc. all work.</li> If copyright</code> is left unset entirely, Tapestry falls back to a built-in three-segment default equivalent to the example above.</li> </ul> Presentation style#</a> </h2> presentation_style</code> and presentation_variant</code>#</a> </h3> [extra] presentation_style = "scholarly" presentation_variant = "contemporary-research-lab"</code></pre> Tapestry ships 5 preset style groups, each with 5 fully-specified variants (25 combinations total). If presentation_style</code> is unset or names a group that doesn't exist, Tapestry falls back to scholarly</code>. If presentation_variant</code> is unset or names a variant that doesn't exist within the selected group, Tapestry falls back to that group's own default variant. </div> Migrating from terminus If you're migrating a site from terminus, any extra.color_scheme</code> or extra.color_scheme_switcher</code> left over in your config is inert under Tapestry — it is never read, mapped, or migrated into an equivalent style/variant. Set presentation_style</code>/presentation_variant</code> explicitly, or accept the scholarly</code>/contemporary-research-lab</code> default. </div> </section> Group</th> Default variant</th> All variants</th></tr></thead> scholarly</code></td> contemporary-research-lab</code> (also the theme-wide default)</td> classic-ivy</code>, nordic-minimalist</code>, dark-academia</code>, scientific-journal</code>, contemporary-research-lab</code></td></tr> creative</code></td> editorial-zine</code></td> bauhaus-studio</code>, editorial-zine</code>, watercolor-atelier</code>, neon-studio</code>, collage-mixed-media</code></td></tr> natural</code></td> periodic-table-chemistry</code></td> celestial-observatory</code>, periodic-table-chemistry</code>, field-notebook</code>, chalkboard-proof</code>, quantum-circuit</code></td></tr> precision</code></td> swiss-precision-instrument</code></td> blueprint-drafting</code>, surgical-precision</code>, aerospace-materials-lab</code>, biomedical-diagnostics</code>, swiss-precision-instrument</code></td></tr> collective</code></td> cartographers-atlas</code></td> cartographers-atlas</code>, ledger-index</code>, social-network-diagram</code>, agora-classical-philosophy</code>, strata-geology</code></td></tr> </tbody></table> Every group and variant independently meets WCAG AA contrast, ships its own self-hosted font pairing, and is built on the same 12-column responsive grid and no-JS navigation collapse. presentation_style_switcher</code>#</a> </h3> [extra] presentation_style_switcher = true</code></pre> Opt-in (default false</code>). Adds a disclosure menu next to the theme switcher that lets a visitor preview any group/variant combination live, without a page reload — a two-level accordion (one entry per group, expandable to reveal that group's variants), not a flat list of all 25 combinations. This is one of Tapestry's three sanctioned JavaScript exceptions; with JS disabled, the control simply doesn't appear and the site stays on its build-time presentation_style</code>/presentation_variant</code>. Navigation & social links#</a> </h2> main_menu</code>#</a> </h3> [extra] main_menu = [ { name = "docs", url = "docs", trailing_slash = true }, { name = "about", url = "about", trailing_slash = false }, { name = "repo github", url = "https://github.com/anirbanbasu/tapestry", new_tab = true }, ]</code></pre> Each entry supports: Field</th> Required</th> Default</th> Notes</th></tr></thead> name</code></td> yes</td> —</td> Link text.</td></tr> url</code></td> yes</td> —</td> Internal content path, or a full external URL.</td></tr> trailing_slash</code></td> no</td> false</code></td> Only applies to internal paths (see below).</td></tr> new_tab</code></td> no</td> false</code></td> Adds target="_blank"</code>.</td></tr> </tbody></table> A url</code> is treated as external whenever it starts with the literal characters http</code> — otherwise it's resolved internally with Zola's get_url()</code>, honouring trailing_slash</code>. new_tab</code> only adds target="_blank"</code>; it does not add rel="noopener"</code> (modern browsers apply that protection to target="_blank"</code> links automatically, but it's worth knowing this isn't set explicitly). socials</code>#</a> </h3> [extra] socials = [ { name = "email", url = "mailto:hello@example.com" }, { name = "github", url = "https://github.com/anirbanbasu" }, { name = "orcid", url = "https://orcid.org/0000-0000-0000-0000" }, ]</code></pre> Each entry is just name</code> and url</code> — there is no separate icon override key. name</code> must exactly match an SVG filename (without extension) under themes/tapestry/static/images/social_icons/</code>, since it's used directly to build the icon path. A name with no matching file doesn't fail the build — it silently renders a broken icon link, so double-check the spelling against the list below. Icons currently shipped: bitcoin</code>, bluesky</code>, codeberg</code>, codepen</code>, discord</code>, discourse</code>, email</code>, ethereum</code>, facebook</code>, fediverse</code>, flickr</code>, forgejo</code>, gitea</code>, github</code>, gitlab</code>, google-maps</code>, google-scholar</code>, instagram</code>, keybase</code>, keyoxide</code>, ko-fi</code>, linkedin</code>, mastodon</code>, matrix</code>, monero</code>, orcid</code>, patreon</code>, phone</code>, pixelfed</code>, reddit</code>, researchgate</code>, signal</code>, slack</code>, spotify</code>, stackexchange</code>, stackoverflow</code>, steam</code>, telegram</code>, twitch</code>, venmo</code>, vimeo</code>, whatsapp</code>, x</code>, youtube</code>, zulip</code> (plus atom</code>/rss</code>, normally reserved for feed_icon</code> below). feed_icon</code>#</a> </h3> [extra] feed_icon = true # feed_icon = "atom"</code></pre> Shown in the footer alongside socials</code>, only when config.generate_feeds</code> is also true</code>. true</code> uses the default icon, rss</code>.</li> A string uses that name instead, looked up the same way as socials</code>.</li> If your site's feed_filenames</code> produces more than one feed and one of those filenames contains "atom"</code>, that specific feed link is forced to the atom</code> icon regardless of what feed_icon</code> is set to. With a single default feed (the common case — just generate_feeds = true</code>, no feed_filenames</code> override), this distinction never triggers.</li> </ul> Content features#</a> </h2> katex</code>#</a> </h3> [extra] katex = false</code></pre># per-page front matter override [extra] katex = true</code></pre> Site-wide default for client-side KaTeX math rendering (one of Tapestry's three sanctioned JS exceptions). Resolved with page-level precedence: a page's own extra.katex</code>, then its section's, then walking up any ancestor sections' extra.katex</code>, then the site-wide config.extra.katex</code>, defaulting to false</code>. An explicit false</code> at a more specific level always wins over a true</code> set higher up — so a section can enable KaTeX globally while an individual page opts back out. With JS disabled, KaTeX-enabled pages show raw, unrendered $...$</code>/$$...$$</code> source instead of typeset math. show_default_author</code>#</a> </h3> [extra] show_default_author = true</code></pre> When true</code>, pages without their own authors = [...]</code> front matter show config.author</code> instead. Set false</code> to only show authorship where a page explicitly declares one. fediverse_creator</code>#</a> </h3> [extra] fediverse_creator = "@user@mastodon.social"</code></pre> Emits a <meta name="fediverse:creator"></code> tag for Mastodon's article attribution feature. Leave unset to omit the tag. Layout#</a> </h2> layout</code>#</a> </h3> [extra] layout = "center"</code></pre> One of "center"</code>, "left"</code>, or "full-width"</code>, applied as a layout-*</code> body class and used to vary the sizes</code> attribute the responsive_image</code> shortcode generates. </div> Current visual difference "center"</code> and "left"</code> currently produce identical CSS and layout — the distinction exists in the config surface but isn't yet visually differentiated. "full-width"</code> is the one value that visibly changes both the page's max-width behaviour and the responsive_image</code> sizes</code> output. </div> </section> Styling extensibility#</a> </h2> stylesheets</code>#</a> </h3> [extra] stylesheets = ["css/custom.css"]</code></pre> Site-, section-, and page-level stylesheets</code> are all additive — every stylesheet declared at any of the three levels is linked on the resulting page, not just the most specific one. Use this to layer small overrides on top of your chosen presentation style rather than to replace it. Images#</a> </h2> [extra.responsive_images]</code>#</a> </h3> [extra.responsive_images] widths = [640, 784, 1280, 1920, 2560] fallback_width = 1280</code></pre> widths</code> is the set of candidate image widths generated for the responsive_image</code> shortcode's srcset</code>; fallback_width</code> is the size used for browsers that ignore srcset</code>. This setting is scoped only to images inserted via that shortcode in your Markdown content — it does not affect og:image</code> (always generated at a fixed 1200×675), the favicon's apple-touch-icon (always 180×180), or header_logo</code> (used at its native size, unresized). Security#</a> </h2> [extra.content_security_policy]</code>#</a> </h3> [extra.content_security_policy] enable = true allowed_domains = [ { directive = "base-uri", domains = ["'self'"] }, { directive = "form-action", domains = ["'self'"] }, { directive = "img-src", domains = ["'self'", "https://images.example.com"] }, ]</code></pre> enable</code> gates the entire Content-Security-Policy</code> <meta></code> tag — when false</code>, no CSP tag is emitted at all.</li> allowed_domains</code> is a generic list of { directive, domains }</code> entries. Any CSP directive name works here (script-src</code>, img-src</code>, connect-src</code>, style-src</code>, font-src</code>, etc.) — it isn't limited to a fixed set.</li> Even with allowed_domains = []</code>, the theme always emits a baseline policy: default-src 'self'; img-src 'self' data:; style-src-attr 'unsafe-inline'</code> (the data:</code> and inline-style allowances are needed by the theme's own mask-icons and inline styles).</li> </ul> Under zola serve</code>, the policy is additionally relaxed with connect-src 'self' ws:</code> and script-src-elem 'self' 'unsafe-inline'</code>, to allow the dev-mode live-reload WebSocket. This relaxation never applies to production builds. Multi-site deployments#</a> </h2> site_id</code>#</a> </h3> [extra] site_id = "my-site-slug"</code></pre> Both the theme switcher and the presentation-style switcher persist a visitor's choice to localStorage</code>, scoped by the browser to the page's origin (scheme+host+port) but not by path. Two Tapestry sites sharing an origin but deployed under different paths — e.g. two GitHub Pages project sites both under username.github.io/</code> — would otherwise silently share and overwrite each other's saved preferences. site_id</code> namespaces both storage keys to prevent that. If unset, it falls back to config.base_url</code>, which is enough to distinguish sites in a plain zola build</code>, but not during zola serve</code> (which rewrites base_url</code> to http://127.0.0.1:<port>/</code>, discarding any path) or a zola build --base-url <url></code> override that strips or normalises the path. Set site_id</code> explicitly if your site is deployed to a shared-origin subdirectory, or regularly tested locally alongside other Tapestry sites on the same port. Quick reference#</a> </h2> Key</th> Type</th> Default</th> Purpose</th></tr></thead> site_id</code></td> string</td> config.base_url</code></td> Namespaces the theme-switcher and style-switcher localStorage</code> keys.</td></tr> presentation_style</code></td> string</td> "scholarly"</code></td> Top-level style group.</td></tr> presentation_variant</code></td> string</td> group's own default</td> Variant within the chosen group.</td></tr> presentation_style_switcher</code></td> bool</td> false</code></td> Opt-in live style/variant preview menu. Requires JS.</td></tr> main_menu</code></td> array of tables</td> []</code></td> Header navigation entries.</td></tr> socials</code></td> array of tables</td> []</code></td> Footer social/contact links.</td></tr> feed_icon</code></td> bool | string</td> unset</td> Show a feed icon in the footer alongside socials</code>.</td></tr> copyright</code></td> string (Markdown)</td> built-in fallback text</td> Footer copyright line.</td></tr> favicon</code></td> path</td> unset</td> Favicon image (SVG or raster). Wins over favicon_emoji</code> if both set.</td></tr> favicon_emoji</code></td> string (emoji)</td> unset</td> Emoji favicon, ignored if favicon</code> is also set.</td></tr> header_title</code></td> string</td> config.title</code></td> Header text, if no header_logo</code> is set.</td></tr> header_logo</code></td> path</td> unset</td> Header logo image. Takes priority over header_title</code>.</td></tr> katex</code></td> bool</td> false</code></td> Site-wide KaTeX math rendering. Overridable per section/page. Requires JS.</td></tr> layout</code></td> "center"</code> | "left"</code> | "full-width"</code></td> "center"</code></td> Overall content-width treatment.</td></tr> show_default_author</code></td> bool</td> true</code></td> Show config.author</code> on pages without their own authors</code>.</td></tr> fediverse_creator</code></td> string</td> unset</td> Emits a fediverse:creator</code> meta tag.</td></tr> stylesheets</code></td> array of paths</td> []</code></td> Extra stylesheets, additive with section/page-level stylesheets</code>.</td></tr> [extra.content_security_policy]</code></td> table</td> —</td> Site CSP <meta></code> tag configuration.</td></tr> [extra.responsive_images]</code></td> table</td> —</td> Width candidates for the responsive_image</code> shortcode.</td></tr> </tbody></table> Standard Zola configuration#</a> </h2> Root-level keys like base_url</code>, title</code>, description</code>, theme</code>, compile_sass</code>, generate_feeds</code>, author</code>, taxonomies</code>, build_search_index</code>, and the [markdown]</code>/[markdown.highlighting]</code> tables are standard Zola configuration, not Tapestry-specific — see Zola's own configuration documentation</a> for the full reference. One Tapestry-relevant note: [markdown.highlighting] style = "class"</code> requires some built-in Zola highlighting theme to be configured (e.g. theme = "monokai"</code>), but every presentation style/variant fully overrides the resulting .z-*</code> token colours itself — the configured theme name only acts as a placeholder to satisfy Zola, not as the actual code-block palette you'll see rendered. Markdown Syntax Guide 2026-07-05T00:00:00+00:00 This article offers a sample of basic Markdown syntax that can be used in Zola content files, also it shows whether basic HTML elements are decorated with CSS in a Zola theme. Headings#</a> </h2> The following HTML <h1></code>—<h6></code> elements represent six levels of section headings. <h1></code> is the highest section level while <h6></code> is the lowest. H1#</a> </h1> H2#</a> </h2> H3#</a> </h3> H4#</a> </h4> H5#</a> </h5> H6#</a> </h6> Paragraph#</a> </h2> Xerum, quo qui aut unt expliquam qui dolut labo. Aque venitatiusda cum, voluptionse latur sitiae dolessi aut parist aut dollo enim qui voluptate ma dolestendit peritin re plis aut quas inctum laceat est volestemque commosa as cus endigna tectur, offic to cor sequas etum rerum idem sintibus eiur? Quianimin porecus evelectur, cum que nis nust voloribus ratem aut omnimi, sitatur? Quiatem. Nam, omnis sum am facea corem alique molestrunt et eos evelece arcillit ut aut eos eos nus, sin conecerem erum fuga. Ri oditatquam, ad quibus unda veliamenimin cusam et facea ipsamus es exerum sitate dolores editium rerore eost, temped molorro ratiae volorro te reribus dolorer sperchicium faceata tiustia prat. Itatur? Quiatae cullecum rem ent aut odis in re eossequodi nonsequ idebis ne sapicia is sinveli squiatum, core et que aut hariosam ex eat. Blockquotes#</a> </h2> The blockquote element represents content that is quoted from another source, optionally with a citation which must be within a footer</code> or cite</code> element, and optionally with in-line changes such as annotations and abbreviations. Blockquote without attribution#</a> </h3> Tiam, ad mint andaepu dandae nostion secatur sequo quae. Note that you can use Markdown syntax within a blockquote</del>. </blockquote> Blockquote with attribution#</a> </h3> Don't communicate by sharing memory, share memory by communicating. — Rob Pike1</a></cite> </blockquote> GitHub-style alerts#</a> </h3> Alerts, also sometimes known as callouts or admonitions, are a Markdown extension based on the blockquote syntax that you can use to emphasize critical information. Requires Zola 0.21.0 or newer. Some content with Markdown syntax</code>. Here is a link</code></a>. </blockquote> Some content with Markdown syntax</code>. Here is a link</code></a>. </blockquote> Some content with Markdown syntax</code>. Here is a link</code></a>. </blockquote> Some content with Markdown syntax</code>. Here is a link</code></a>. </blockquote> Some content with Markdown syntax</code>. Here is a link</code></a>. </blockquote> Buttons and links#</a> </h2>

Section-level Configuration Reference

Site-level Configuration Reference

Markdown Syntax Guide

`Buttons and links#</span></a> </h2>`

Mathematical Typesetting

Shortcodes

Tapestry - docs

Page-level Configuration Reference

Tapestry - docs

Page-level Configuration Reference

Markdown Syntax Guide

Nested Ordered List#</span></a> </h3> Fruit Apple</li> Orange</li> Banana</li> </ul> </li>

Task List#</span></a> </h3> Completed item</li>

Mathematical Typesetting