Tortusfor Designers
Snippet Library/Content

Post layout

What you control on a single published post — the /blog/:slug page inherits your blog appearance slice.

The single blog-post page (/blog/:slug) is a Dynamic Page — Tortus renders your authored post inside our chrome. There's no separate blog_detail setting: the post page reads the same blog appearance slice as the index ({{tortus:blog}}), stored once at design_tokens.blog. Style the index and every post updates with it.

Post content is never touched — your authored HTML is rendered verbatim (and sanitized). These controls only style the chrome around the article.

What carries onto the post page

The blog slice drives both surfaces; a few of its fields are index-only (layout, columns, the tag filter). These are the ones that shape the post page:

FieldValuesOn the post page
showExcerptstrue (default) / falseshows the post dek (subtitle) under the title
showAuthortrue (default) / falseshows the author name + avatar in the meta row
showReadTimetrue (default) / falseshows the "N min read" estimate
accentColorprimary (default) / secondary / accenttints prose links + the active category pill
cardRadius024 px (default 8)corner radius of the post's lead image
categoriesyour listthe category chip above the title reads from here

An org that hasn't customized renders byte-identically to the original editorial look (neutral tag pills, emerald prose links). The moment you customize, the post adopts your brand accent — an edited blog wears the brand, a legacy one stays neutral.

Referencing the accent from custom content

The resolved accent is a live CSS var (var(--color-primary) by default — it follows your accentColor role). Any Custom Code block you drop into a post can read the same brand tokens, so inline callouts stay on-brand and re-skin when the broker changes their palette.

A branded pull-quote inside a post

Custom HTML + CSS escape hatch

Like every page-builder block, a block you add to a post supports Convert to custom — the scoped Custom HTML and CSS fields are the escape hatch when a token knob doesn't reach far enough. Scoped CSS references the same --color-* / --font-* design tokens, so it stays on-brand.

The blog appearance slice is edited from the site's Blog appearance panel; the feed token that lists posts is documented on Blog.

Full param table: Designer Handbook.