Frontmatter Reference
Complete reference for all InkStone frontmatter fields.
Your notes. Your structure. Live on the web.
A lightweight Python/Flask engine that turns a folder of Markdown files into a fully-featured website. Write, push to GitHub, see it live — no export step, no build pipeline, no CMS.
Your folder structure maps directly to URL paths — no configuration needed:
| Vault path | URL |
|---|---|
blog/My Post.md |
/blog/my-post |
gallery/Photo.md |
/gallery/photo |
About.md |
/about |
Add website: true to a note's frontmatter and it's live. A note with type: listing auto-generates a paginated post index. A note with type: homepage serves its content at the section root.
A production-ready site out of the box:
.canvas files published as read-only visual diagrams![[img|inline]] places images in text without a lightboxdefault_theme: sets the default for new visitorsSee Features for the complete list.
InkStone reads plain .md files with YAML frontmatter — it works with any editor that produces them. A plain text editor and git push is all you technically need.
That said, Obsidian is the recommended editor. It's the reference implementation for the syntax InkStone understands: [[wiki-links]], [[wiki-links | display text]], ![[embeds]], > [!callouts], Dataview queries, inline tags, block references, and transclusions. Writing in Obsidian means every feature works as intended, with live preview as you compose.
If you prefer a different environment, the closest alternatives are:
[[wiki-links]], backlinks, and graph view; same file format as Obsidian; most syntax compatible[[wiki-link]] support and YAML frontmatterBasic publishing works everywhere. The richer Obsidian-native syntax (Dataview, transclusions, callouts, block references) is only as good as your editor supports it.
Complete reference for all InkStone frontmatter fields.
Requirements: Python 3.11+ InkStone works with any Markdown editor — even a plain text editor. For the full experience (wiki-links, Dataview, callouts, transclusions), use Obsidian. Foam (VS Code) is…
The recommended production setup: your Obsidian vault lives in its own private GitHub repo. Pushing to it triggers an instant content update — no container rebuild required. How it works The vault is…