Documentation Systems

This portal explains the delivered SaaS foundation and how to turn it into a customer-owned product, while the accompanying technical guide provides deeper implementation and operations detail.

On this page

Two documentation systems

SystemAudienceBuilder referencePublishing model
Customer help centerPeople who use your finished product.
Implementation referencesrc/features/docs/shared/content.ts and src/features/docs/ui.
Ships at /docs inside your application; replace the starter content with workflows and support information for your own users.
Builder and maintainer guidePeople who customize, deploy, and operate the delivered product.The accompanying docs directory plus README, AGENTS.md, SECURITY.md, SUPPORT.md, and LICENSE.Use it when building or operating the product; implementation references in this portal remain optional and collapsed where possible.
Implementation reference3 areas

These Product code locations explain how the documented behavior is implemented. Expand them when you are ready to customize or maintain this area.

Content contract

Stable section identifiers and typed blocks define the replaceable starter content.

  • src/features/docs/shared/content.ts
  • src/features/docs/shared/types.ts

Explorer UI

Navigation, filtering, rendering, and block presentation form the in-product documentation experience.

  • src/features/docs/ui/explorer.tsx
  • src/features/docs/ui/navigation.tsx
  • src/features/docs/ui/blocks.tsx

Route entrypoint

The public /docs route delegates rendering to the feature UI.

  • src/app/docs/page.tsx
  • src/features/docs/ui/page.tsx

Reference paths are relative to the delivered product checkout.

Maintainer guide map

FileUse
docs/getting-started/launch.mdProduction launch checklist.
docs/deploy/deployment.mdDeployment guide and host capability notes.
docs/extend/customization.mdBranding, UI, and copy customization guide.
docs/extend/development.mdFeature development workflow rules.
docs/extend/architecture.mdPlatform architecture boundary guidelines.
docs/extend/module-removal.mdSafe module removal checklist.
docs/extend/testing.mdTesting guidelines and layers.
docs/operate/operations.mdProduction operations, incident response, recovery, retention, and scheduled jobs.
docs/getting-started/buyer-quickstart.mdShortest path from a delivered checkout to a running product.
docs/product/billing/setup.mdProvider-edition billing setup and links to Stripe, Lemon Squeezy, Dodo Payments, Polar, and Creem guides.
docs/product/notifications/email/setup.mdSupabase Auth and Resend transactional email configuration.

Update documentation in the same change when you

  • Add, rename, or remove an environment variable, route, role, table, RPC, storage bucket, job, webhook, event, or command.
  • Change a provider setup step, capability, payload, dashboard setting, or test-mode procedure.
  • Change a customer workflow, module boundary, failure mode, support process, or removal path.
  • Add a migration, backfill, repair, retention rule, backup requirement, or recovery step that operators must understand.
  • Change the product behavior represented in your published customer help center.