Configured Markdown

Sidebar text/profile text, article/site footer text, string content licenses, authored reference entries and final article_end_text share a small build-time interpolation mechanism. Native field resolution happens first; per-instance widget options remain local. Ordinary article/section bodies, shortcode labels, menu labels, image paths, titles, bylines and translations do not interpolate.

[params]
footer_text = '**{site.title}** — notes worth returning to.'
article_text = 'You have been reading **{page.title}**.'

Only two built-in values exist: {site.title} (current-language native Site.Title) and {page.title} (the Page displaying the component). There is no automatic theme version, author identity or release link. Unknown/empty text tokens stay visibly literal. Names are case-sensitive lowercase dotted identifiers, not property traversal. The pass is nonrecursive; values are escaped plain strings, never Markdown/templates.

#Add one real value through native lookup

Create site layouts/_partials/config-markdown/values.html:

{{- return (dict "site.home" .Page.Site.Home.Permalink) -}}

Then use [Home]({url:site.home}) in a participating setting. url: selects the same value as a whole Markdown link destination, with URL validation and delimiter escaping. Do not splice it into a path or prose. Missing/empty/unsafe URL tokens fail rather than emitting a broken link. Native Home.Permalink follows language and deployment prefix; literal [Home](/) still means host root.

The extension returns a flat string map; it cannot replace built-ins. Context has Page, Owner, Settings and normal component context. Select intended public values only; never return all Site.Params, private files or credentials. Do not render Content, mutate context or recurse into the helper. Templates are trusted code; configuration strings are not evaluated as templates.

#Literal braces and rendering

Use \{page.title} or {page.title} for a literal. Conventional fenced/ indented code, backtick spans and native dollar TeX spans in configured text stay opaque. For complex nested examples use explicit escapes; this is a conservative lexical guard, not a second Markdown parser. No-token text goes unchanged into native RenderString. Authored Markdown remains active under the same safe HTML policy and resource hooks. Relative source links use the actual displaying Page’s source directory, so one relative footer link is not portable to every page.