Default platform site

Launch governed marketing sites without rebuilding your stack.

CMS Platform gives business teams a fast path from campaign idea to searchable, AI-assisted, multi-site publishing while developers keep control of data, plugins, SEO, and deployment.

Seed content describes the platform capability and onboarding path; live production readiness still depends on your configured backend, providers, and deployment proof.

For business owners

Marketing momentum with operational control

A practical CMS landing story for teams that need campaigns, sites, and content operations to move together.

Campaigns move faster

Create landing pages, event pages, forms, and content sections from reusable DB-driven page data instead of waiting for a bespoke code release.

One platform, many sites

Run brand, campaign, partner, and nonprofit sites from the same platform model while preserving site-specific navigation, theme, content, and forms.

AI-assisted publishing

Use AI-assisted workflows for drafts and content operations while keeping review, publishing, and runtime proof boundaries explicit.

Governance by design

Enterprise RBAC, JWT session controls, rate-limit posture, and evidence-driven review docs help teams keep marketing speed aligned with operational risk.

Search and agent visibility

SEO, sitemap, robots, JSON-LD, and llms.txt surfaces are part of the platform story, not an afterthought for the last launch week.

Lower rewrite pressure

Business changes are modeled as site data, page sections, components, and plugin enablement wherever possible instead of parallel one-off site code.

Application path

How to apply for onboarding

The first conversation should clarify business goals, operating constraints, and the site model before implementation begins.

1. Tell us the business goal

Share the campaign, organization, audience, launch timing, and required site flows such as contact, event signup, content publishing, or donations.

2. Confirm the operating model

Map who edits, reviews, approves, publishes, and measures content so the CMS setup matches the way the business actually works.

3. Start with a governed pilot

Use the default platform seed as the first site baseline, then replace seed content with approved brand, page, form, and integration data.

For developers

Built for engineers who need real extension points

The public site is marketing-friendly, but the platform shape stays technical: Go services, Next.js rendering, DB-backed pages, plugins, and source-backed proof gates.

DB-driven pages and sections

Page sections are stored as structured JSON and rendered through a component registry, so default content, tenant sites, and future page builder flows share a contract.

View seed contract

Plugin-rich architecture

Backend and web plugin boundaries support storage, auth, dashboard, content, AI, and external extension paths with fail-closed behavior where live executors are not wired.

Inspect plugin system

Go + Next.js runtime split

Go owns backend services, Ent, GraphQL, auth, and migrations; Next.js owns the public CMS runtime, SEO surfaces, and site-specific rendering.

Explore source

AI and SEO surfaces

The platform includes AI content/runtime hooks, JSON-LD, sitemap, robots, and llms.txt routes while keeping static review output separate from runtime proof.

Review web libs

Docs

Move from pitch to proof

Use the repo-owned documentation to inspect the operating model, review posture, and source-backed evidence behind this platform.

User manual

Bilingual operating manual outputs and source workflow for CMS admin and public-site flows.

Manual docs

Project review

Executive review artifact and guidelines that distinguish current source evidence from runtime proof.

Review artifact

Generation guides

Manual and review generation guides for keeping stakeholder documents aligned with specs and proof artifacts.

Docs source

Repository

Inspect the Go backend, Next.js public web, CMS admin, seeds, specs, and plugin surfaces directly.

Source code

Platform Metrics

15+

DB-driven page section components

Plugin extension types (core, storage, auth, custom)

AI crawler rules in robots.txt

Agent/SEO surfaces (llms.txt, sitemap, JSON-LD, MCP)

Call to action

Register your pilot site and turn the default seed into your launch plan.

Send the business context, required pages, integrations, and review needs. The first deliverable is a governed pilot that can be verified before broader rollout.