Most sites built with this theme only need a small set of layouts. This guide helps you pick the right one quickly.
Choose this when
page
Use page when you want a simple standalone content page.
- Good for about pages, contact pages, and general markdown content
- Minimal structure beyond the theme shell
Demo
post
Use post when you are writing article-style content.
- Good for blog posts, announcements, and long-form writing
- Supports hero media, tags, related posts, and an optional table of contents
Demo
profile
Use profile when the site centers on a person, project, or organization identity.
- Good default homepage for most theme users
- Combines masthead, links, posts, and repositories
Demo
landing
Use landing when you want a homepage that emphasizes navigation and repository context.
- Good for project homepages
- Best when your top-level navigation is an important part of the experience
Demo
linktree
Use linktree when the page is mainly a curated list of links.
- Good for creator pages, bio links, resource hubs, and simple launch pages
- Works well with custom background styling and social links
Demo
repositories
Use repositories when the repository list should be the primary content.
- Good for portfolio-style project indexes
- Best when the GitHub repo list is more important than posts
Demo
docs
Use docs when you are publishing a structured documentation collection.
- Good for guides, references, and multi-page documentation
- Best when you want categories, sidebar navigation, and article-level organization
Demo
paginate
Use paginate when you want a card-based blog index.
- Good for blog homepages with featured cards
- Best when visual post previews matter
Demo
paginate_timeline
Use paginate_timeline when you want chronological browsing in a simpler timeline format.
- Good for update logs, journals, and post archives
- Best when recency matters more than card-style presentation
Demo
A simple starting point
If you are not sure where to begin:
- Start with
profile for your homepage.
- Use
page for standalone content.
- Use
post for writing.
- Add
docs only if you need a real documentation section.
