SaaS Documentation and Help Center Site

This package builds a documentation and help center site for a SaaS product, usually at docs.yourdomain.com or help.yourdomain.com, and moves your existing articles into it from Notion, Google Docs, Zendesk, Intercom or loose files. It is for companies whose support team answers the same question every day because the answer is hard to find.

Two kinds of reader

Customers want short how-to articles grouped by task, with screenshots and a clear next step. Developers want guides, code samples and a complete API reference. On Business and Premium the site has both: a help center organized by category, and developer docs with language tabs on code samples (cURL, JavaScript, Python, PHP) and an API reference generated from your OpenAPI file with Scalar or Redoc, so the reference changes when the spec changes.

How your team writes and publishes

• Developers write MDX files in Git, so docs change in the same pull request as the feature they describe.
• Support staff who do not use Git can edit in a headless CMS or a Laravel admin panel instead; I set up whichever fits who writes.
• A "Was this helpful?" vote sends results to your analytics, so you see which articles fail readers.
• Old help URLs redirect to the new pages, keeping links in emails, tickets and search results working.

Search, versions and in-app help

Starter and Business use Pagefind, a static search index with no monthly fee. Premium switches to Algolia for typo tolerance and search analytics, adds a version switcher for products with v1 and v2 APIs, and gives your app links that open the right article from any screen. A CI job checks for broken links and flags articles not touched in a set period.

Writing new articles is not part of the plans; the writing extra covers that. Algolia, CMS and support tool fees are paid to those providers.