Contents
Getting Started
Welcome to Your Template Project
Use this sample post to validate markdown rendering, sticky TOC, and SEO metadata.
Quick Hits
- •This post validates markdown frontmatter and article rendering end-to-end.
- •H2/H3 headings drive the sticky table of contents.
- •You can author posts directly in `apps/web/content/posts`.
Why This Template Exists
This project gives you a repeatable, production-ready baseline for fast product execution.
What You Get
- Monorepo structure
- Blog pipeline with typed frontmatter
- SEO route handlers
- Auth and billing scaffolding
How The Blog Structure Works
The article page uses a one-third sticky table of contents and two-thirds reading column.
Heading Strategy
Use ## and ### headings in posts.
Authoring Rules
Keep each section concise and semantic so search engines and readers can scan quickly.
What To Customize First
You should replace branding and conversion copy first, then wire your actual app features.
Priority Order
- Landing page messaging
- Auth callback and app routes
- Stripe product setup
- Content publishing cadence
References
- Internal template design notes
FAQ
Where do blog posts live?
All posts are markdown files in `apps/web/content/posts` with typed frontmatter.
How do I add a hero image?
Add your image under `apps/web/public/blog` and reference it with `/blog/your-image.webp`.
How does TOC grouping work?
The TOC groups H3 items under each H2 heading and follows scroll position.
Key Takeaway
Start by replacing this file, keep the frontmatter schema, and maintain H2/H3 structure for best blog UX.