InkStoneNavigation
Contents
Auto-generated nav
Section listing pages automatically appear as top-level nav links. A vault with these folders:
vault/
├── blog/Blog.md (type: listing)
├── gallery/Gallery.md (type: listing)
└── projects/Projects.md (type: listing)
Produces nav links: Blog · Gallery · Projects (in filesystem order).
No configuration required. Add a type: listing file to a folder — it appears in the nav.
Hiding sections from the nav
A section appears in the nav by default. To hide it, add nav_hidden: true to the listing or homepage file for that section:
---
website: true
type: listing
title: Archive
nav_hidden: true
---
The section is still fully routable — visitors can reach it via direct links or wiki-links. It simply won't appear as a nav item.
Pinning pages with menu_order
Any note can be pinned to the nav by adding menu_order: to its frontmatter:
---
website: true
title: About
menu_order: 1
---
- Lower value = further left in the nav
- Pinned pages are appended after the auto-generated section links
- Multiple pages with
menu_order:are sorted by value
Example: an About page pinned after all section links:
---
website: true
title: About
menu_order: 10
---
This is the intended mechanism for root-level standalone pages that should be discoverable. See URL Mapping › Root-level standalone pages.
Breadcrumbs
Every post page shows a breadcrumb trail:
Home › Blog › My Post Title
Each segment is a clickable link. The breadcrumb reflects the URL structure — nesting matches folder depth.
Next / Previous navigation
Posts show previous/next links that let the reader continue through the section in listing order:
← Previous post title Next post title →
The reading sequence mirrors the listing page: featured posts first (sorted by priority: ascending, then date: descending), followed by regular posts (sorted by date: descending). The very first post in the sequence has no left arrow; the very last has no right arrow.
The nav block appears above the See also block at the bottom of each post.