Why useful content compounds after you publish it
A focused editorial system connects what your audience asks, what your product knows and what search engines can understand.
A self-hosted foundation that turns editorial direction into searchable articles on your own domain—with Next.js, Supabase and optional AI.
The source is free. Hosting, databases and optional providers may have their own costs.
A focused editorial system connects what your audience asks, what your product knows and what search engines can understand.
The template brings the moving parts into one repository. You choose the editorial rules and integrations; the system handles the repeatable plumbing.
Set your brand, audience, tone, seed topics, internal links and CTA in one typed profile.
Use local topics or connect a text provider only after you define credentials and budget.
Supabase keeps articles and execution state. RLS exposes only published content.
Next.js renders article pages, metadata and structured data directly on your domain.
No closed dashboard sits between you and your publishing workflow. Every important setting lives in code you own.
Read the setup guideName, domain, narrative and conversion path.
Audience, tone, keywords and internal links.
Schedule, credentials and provider limits.
Keep review human-controlled where your context requires it.
The workflow can continue after reserving the date. A later call cannot claim the same schedule twice.
This browser model explains the published guardrail contract. It does not contact Supabase, a cron route or any AI provider.
Idempotent execution prevents the same schedule from publishing twice.
Public database reads are restricted to articles already marked as published.
The repository ships without provider keys or production data.
Cloning is free and triggers no provider. A complete installation still needs your own deployment, Supabase project and—only if enabled—AI or Search Console credentials.
THE REPOSITORY IS THE PRODUCT.