01
The content layer is missing
Docs, changelogs, case studies, landing pages, newsletters, and a blog need somewhere coherent to live. Many teams end up building each surface separately.
Open source. The Next.js publishing layer.Next.js powers the product.
Next.js powers the product.
We’re building what it doesn’t ship.
An open-source, plug-and-play blog and CMS. Integrates in just 10 seconds.
Editorial workflow, SEO guidance, and content ownership in one system.
Early-stage MIT licensed Built for Next.js teams
Engineering6 MIN READ
Why Your Database Index Is Not Being Used
A working guide to the reasons Postgres ignores an index you were sure it would use, and how to read the plan instead of guessing at it.
THE SHORT VERSION
Postgres skips an index when it estimates that reading the table directly will cost less, when the query shape does not match the index's leading columns, or when a function or type cast on the indexed column makes the index inapplicable. Read EXPLAIN ANALYZE and compare estimated rows against actual rows before changing anything.
The four reasons an index goes unused
Good writing begins with a clear idea. Give readers the context they need, then make every paragraph earn its place.
Right at home in your stack.
Next.jsTypeScriptGitMarkdownshadcn/ui
THE GAP
Next.js gives you the app.
Not the publishing system.
Next.js gives teams powerful application and delivery primitives. Content-driven products still have to assemble the layer that turns ideas into durable, discoverable pages.
02
SEO is a collection of primitives
Titles, descriptions, canonicals, social cards, structured data, sitemaps, robots, feeds, and internal links need shared defaults and checks. The framework does not provide that editorial contract for you.
03
The stack drifts apart
WordPress offers a familiar publishing workflow. Yoast adds inline guidance. Headless CMS tools add remote content. In a Next.js app, those layers can become a second system to sync, host, and maintain.
THE PRODUCT
WordPress-like publishing.
Next.js-native delivery.
A familiar place for writers and marketers to work, with content, code, and generated output kept in sync.
01
A place to publish.
Draft, edit, review, schedule, and publish from a visual Studio or your favorite editor. The source stays portable.
Familiar workflow. Developer-owned content.02
SEO by default.
Consistent metadata, canonical URLs, social cards, structured data, feeds, and factual checks are part of the publishing path.
Fewer omissions. No score theater.03
One source. Every surface.
Article pages, search, social cards, structured data, RSS, and AI-readable output stay connected to the same content model.
Write once. Let the system do the rest.MADE FOR THE READER
Good ideas deserve
a great place to land.
Help readers find the answer, follow the details, and discover what comes next. This is the blog your project ships with.
01
Get to the point
Answer-first summaries and key takeaways.
02
Keep your place
Contents, reading progress, and clear hierarchy.
03
Follow your curiosity
Search, topic archives, and related reading.
The journal.Explore the live blog
Engineering
Why Your Database Index Is Not Being Used
A working guide to the reasons Postgres ignores an index you were sure it would use, and how to read the plan instead of guessing at it.
Ketan6 min
Design
The Typography Decisions That Actually Change Reading
Five typographic choices measurably change how much of a page people read. Most redesigns spend their effort on the other forty that do not.
Ketan4 min
Artificial Intelligence
RAG Is Not a Database Problem
Teams reach for a vector database on day one and spend the next month discovering that retrieval quality was never about the store they picked.
Ketan5 min
YOUR REPOSITORY IS THE CMS
Fits your stack.
Stays out of your way.
Content lives beside your components. Review it in a pull request. Deploy it with your app. Keep the entire system when your needs change.
- App Router and Server Components
- Static pages with incremental regeneration
- Typed content and configuration
- Visual editing that saves plain Markdown
content/posts/hello-world.mdMarkdown
---
title: "Your next great idea"
category: Engineering
publishedAt: "2026-09-05"
tldr: "Start with the useful part."
---
## A little context
Your words go here. The rest
is already taken care of.ONE SOURCE. CONNECTED OUTPUTS.
CONTENT THAT WORKS FOR YOUR BUSINESS
Turn "FREE" search traffic
into your next "customer".
Illustrative examples: 1,000 visitors at 1% conversion means 10 paying customers; 10,000 visitors at 0.5% means 50 paying customers.
- 01Get discovered
SEO
Search-ready pages. Built-in SEO guidance.
- Target questions your buyers search for
- Fine-tune titles and descriptions
- Publish with structured data included
- 02Bring people in
Traffic
Useful answers attract interested visitors.
- Bring readers in through helpful guides
- Link related posts to keep them exploring
- Refresh useful posts to stay relevant
- 03Grow your business
Revenue
Turn reader interest into signups and sales.
- Connect each post to a relevant offer
- Give readers a clear next step
- Measure signups and sales from content
Metadata, sitemaps & structured data included.
START PUBLISHING
Build the publishing layer
your Next.js project deserves.
Your next post has the potential. Start with a blog. Build with SEO in place.
Free to use. Free to change. MIT licensed.