Documentation wants files, versioning, and boring HTTPS

Static site hosting for documentation is the natural home for API references, product handbooks, and internal runbooks compiled to HTML. You run Docusaurus, MkDocs, VitePress, Hugo, Sphinx, or a hand-built tree on your machine or in CI, then upload the output. StaticHost serves those files. It does not run npm or Hugo for you. It does not include email, a built-in CDN product, or forever-free hosting after a short trial. Plans are Starter $9, Pro $30, Scale $65, and Business $130.

Deep links must exist as files. The web server rule is try_files $uri $uri/ =404—no SPA index.html fallback for missing doc paths. Most doc generators already emit real paths; keep them that way.

Who this is for

  • Engineering teams publishing public API docs.
  • Startups maintaining a help center as static HTML.
  • Open-source maintainers who want a paid, predictable home for a commercial docs portal.
  • Students learning doc tooling who still need a host for graded sites.

Pick other products for wiki software with server-side auth as the primary UX, PHP WordPress knowledge bases, or platforms that must run your doc build remotely.

Publish path for docs portals

  1. Build in CI on every main-branch merge (npm run build, mkdocs build, hugo, etc.—locally to CI, not on StaticHost).
  2. Publish only the output directory (build, site, public).
  3. Verify HTTPS preview: search page, version switcher, asset paths.
  4. Attach docs.example.com; create DNS; wait for verification; wait for certificate.
  5. Roll back via deploy history if a bad generation escapes review.
  6. Keep versioned outputs as real directories (/v1/, /v2/) if you promise versioned URLs.

Pair with cheap portfolio static hosting, static website hosting provider, and host HTML files.

Worked example: a student class project

A student builds a MkDocs site explaining a networking lab. They run mkdocs build on their laptop, zip the site/ contents with index.html at the root, and upload during class on a Starter plan or studio seat. HTTPS preview lets the instructor review without the student rushing DNS. After feedback, they fix a broken diagram path, redeploy, then optionally attach a personal domain and wait for the certificate.

The project never needed WordPress. It never needed StaticHost to install Python. It never assumed forever-free beyond a short trial. When the term ends, deleting the site frees quota. The same student later uses identical habits for an internship’s internal HTML runbook mirror.

Failure to avoid: changing WordPress URLs before HTTPS exists

Companies sometimes migrate a WordPress “knowledge base” toward static docs. Mid-migration, someone runs a global HTTPS URL replace in the database while the vanity docs hostname still lacks a working certificate on the new stack. Editors see warnings; staged content disagrees with public content; panic follows.

If WordPress remains in play, finish TLS on that hostname before forcing https:// siteurl changes. If you have left WordPress for StaticHost, stop carrying database habits: generate HTML, prove it on HTTPS preview, then point DNS, then rely on certificate issuance after verification. Old WP pretty permalinks that were never exported as files will 404 under =404—export deliberately. Do not expect StaticHost to execute PHP leftovers.

When to pick a different product

Use a hosted wiki when non-technical editors need in-browser structured editing with permissions as the core product. Use PHP hosts for WordPress. Use forever-free Pages for public OSS docs if $0 forever and forge policies fit. Use platforms with remote build plugins if your org refuses to own CI.

Stay on StaticHost when CI already emits HTML and you want preview-before-DNS plus rollback. Pro ($30) staging helps when docs and marketing share review rituals. Scale/Business raise caps for many doc properties or large asset sets. No plan adds mailboxes or a CDN product.

Search, versions, and 404 honesty

Client-side doc search is fine as static JS plus a generated index file. Version dropdowns must point at directories you actually uploaded. A missing /v3/api/auth/ should 404 unless you shipped that page—do not wish for SPA fallbacks to hide incomplete releases. Branded 404.html can explain “this version was removed” while still being a file.

CI notes that prevent surprise

  • Cache dependencies in CI; upload artifacts only.
  • Fail the pipeline if index.html is missing at output root.
  • Block deploys that include node_modules.
  • Store the docs domain runbook beside the repo: preview first, DNS second, cert third.

FAQ

Will StaticHost run npm run build for Docusaurus?

No. Build in CI or locally; upload the build folder.

Can docs send email from “Contact maintainers”?

Not via StaticHost mailboxes. Link to a form provider or mailto carefully.

Why do some client-routed doc themes 404?

They expected index fallback. Prefer generators that emit real paths.

Is there a free forever docs tier?

No. Short trial, then $9/$30/$65/$130. OSS maintainers may prefer free forge Pages for public commons.