For end users
content-insights
The bundled public-facing site. Static Astro build that renders your published articles and pages with brand-aware design.
Type: outbound. Bundled with Pectus.
What it does
When you Publish from the CMS, content-insights builds an Astro site from your articles + pages rows, applies your brand tokens, commits the result to your configured GitHub repo, and lets your deploy target (Vercel, Netlify, Pages) take it from there.
Phase 1 ships content-insights as an explicit per-workspace activation rather than always-on. A fresh install activates content-insights on first publish and gets a live site within minutes.
CMS surfaces it contributes
- Workspace tabs: Pages, Articles
- Workspace settings: Site URL, Redirects
These surfaces only appear in the workspace nav once content-insights is active. If you don’t want a public site, leave content-insights deactivated and the nav stays clean.
Configuration
- Site shape — Brand new site (Pectus owns
/) or Existing site (Pectus mounts under a sub-path like/insights/). - Mount slug —
/for brand-new,/insights/or/blog/for existing sites. - GitHub repo —
owner/nameof the repo content-insights commits to. The repo your deploy target watches reads from this.
Activation lives at /apps/content-insights/activate in the CMS.
Where it lives
pectusai/apps/content-insights/APP.md