libref

The libref shortcode is the canonical way to link to a Library deep-link from inside prose. It is the inline counterpart to the library blockquote shortcode — use libref when you want a small reference tucked into a sentence, use library when you want to display the quoted text as a pulled blockquote with a “Read in Book” CTA.

Source: themes/bifrost/templates/shortcodes/libref.html

Syntax#

{%/* raw */%}

The transition signal is preserved in {% libref(book="zephaniah", chapter=1, verse=10) %}Zephaniah 1:10{% end %}:

… preserved in {% libref(book="genesis-woh", chapter=1, verse=1) %}Genesis 1:1{% end %}.

… most importantly the {% libref(book="book-of-enoch") %}Book of Enoch{% end %}.

{%/* endraw */%}

Parameters#

The body is rendered with markdown(inline=true) so light inline markup (*emphasis*, **bold**) inside the label still works.

Output#

<a class="libref" href="/library/zephaniah/#c1p10">Zephaniah 1:10</a>

.libref is style-light (no visual rules of its own) — the cascade in content-area templates already applies the underline + accent colour. The class exists so future code can target libref-only behaviour (analytics, alternate visual modes) without re-grepping templates.

Why use this instead of a markdown link#

Two reasons:

1. Language-awareness. The shortcode resolves the path via get_url(..., lang=lang), so the same source line renders /library/zephaniah/#c1p10 in English and /de/library/zephaniah/#c1p10 in German automatically. A raw markdown link hard-codes the English path forever.
2. Path centralisation. If /library/ ever moves or gets renamed, every reference still resolves.

When to use libref vs library#

Both auto-resolve language-aware paths; they differ only in visual weight.

Related#

• library — the blockquote sibling for displayed quotations.
• wiki — the same pattern for wiki entries (/wiki/<slug>/).
• Content → wiki-shortcodes — the visual surface around inline canon-internal links.