Skip to content

docs: naming a rendered document (fileName) - #40

Open
delchev wants to merge 1 commit into
mainfrom
docs/rendered-document-file-name-2
Open

docs: naming a rendered document (fileName)#40
delchev wants to merge 1 commit into
mainfrom
docs/rendered-document-file-name-2

Conversation

@delchev

@delchev delchev commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

Documents the fileName pattern proposed in #50.

A document is rendered to a file in two places - the versioned copy a function: Snapshot child mints and the copy a notify block attaches - and the intent could say nothing about what that file is called. The new section covers the token vocabulary ({field}, one-hop {relation.field}, {field:pattern}, {A|B} alternatives, {Version}), where each side's paths resolve, and the normative rules - value sanitization, non-ASCII preserved rather than transliterated, blank renders empty while unresolvable is an authoring error, and the same default on both sides.

Added to /spec/presentation under Printable documents, plus a reference-index row.

npx vitepress build docs clean, anchor verified in the built HTML. Left open pending the proposal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant