Ship documentation
as a real site
Deploy VitePress, Docusaurus, Nextra, VuePress, MkDocs, and other static documentation builds with search-friendly HTML, custom domains, HTTPS, and predictable release paths.
Documentation formats we see every day
Where documentation hosting gets messy
The site outgrows the tool
Hosted docs tools are convenient, but teams often hit limits around branding, custom pages, and how much control they have over the final site.
Basic wikis are too limited
A wiki is fine for notes. Public product docs usually need search, readable navigation, custom domains, metadata, and a cleaner first impression.
Self-hosting eats engineering time
Managing servers, SSL, deploy hooks, and release hygiene should not compete with writing the docs.
Check the build before you publish
Upload the generated folder
Docusaurus usually outputs build, VitePress uses .vitepress/dist, and MkDocs writes to site. Upload the generated files, not the source markdown.
Confirm base paths
If the docs live under a subpath or project route, make sure the framework base URL matches the final URL.
Test search and navigation
Open a production build locally and check search indexes, sidebar links, version paths, and deep links before sharing the public URL.
Keep assets cacheable
Docs sites often ship many small images, fonts, and JavaScript files. A static deploy keeps those assets easy to cache at the edge.
Built for more than one kind of documentation
Open-source project docs
Publish guides, changelogs, and migration docs on a branded domain without turning the docs site into a separate ops project.
API references
Ship clean reference sites with search, navigation, and code-friendly layouts that are easier to scan than a generated blob.
Internal knowledge bases
Host engineering handbooks, runbooks, and process documentation with a clean site structure.
Product documentation
Publish onboarding docs, setup guides, and feature references that stay fast for customers in every region.
Design systems
Expose component usage, tokens, and patterns in a navigable site that can grow with the product.
Works with the major static docs stacks
Documentation hosting FAQ
Can I deploy VitePress or Docusaurus output here?
Yes. Run the framework build first, then upload the generated static output directory. DeployPages serves the final HTML, CSS, JavaScript, and assets.
How do custom domains work for docs sites?
Add the domain after deployment, point the DNS record to the provided target, and DeployPages provisions HTTPS automatically.
Can I host private documentation too?
The strongest fit today is public documentation and open product docs. Access control is expanding, but the core workflow today is static publishing.
Does this help with SEO?
It can. Static HTML, clean URLs, useful metadata, and fast delivery give documentation a stronger technical base for search visibility.
Publish the docs build as a site
Upload the generated documentation folder and give readers a fast, branded place to find answers.
Supports HTML, CSS, JS, and typical static documentation assets.