The Public Docs, App Pages, and Updates

What Is Published

The guides you are reading, a page for each app, and the Updates feed are public. They are at mountdev.app:

• Docs at /docs/: a guide for the workspace and one for each app, such as /docs/crm/. Every page has a menu of its app's pages, Previous and Next links, and a search box that finds pages by title and headings.
• Apps at /apps/: every app and where it stands (Planned, In Development, Early Access, or Available). An app that is being built or is available has its own page at /apps/<app>/ with its features, the number of automated tests that cover it, and its latest updates.
• Updates at /updates/: what is new, newest first, with a feed at /updates/feed.xml for any feed reader.

The guides for the machine-readable parts are served as they are: /docs/core/openapi.json, /docs/core/openapi-billing.json, /docs/core/openapi-reporting.json, /docs/core/mcp-tools.json, /docs/core/permissions-index.json, and /docs/core/llms.txt. A list of every page for search engines is at /docs/sitemap.xml.

Published with Every Release

These pages are made from the same files as the product, in the same release. When an update to MountDev Ops is released, its docs, its statuses, its test counts, and its Updates are published at the same moment, so nothing is out of date. Nobody has to rebuild or publish a second site.

What Is Never Published

Only the guides in the app and workspace folders are public. Internal plans, build rules, feature proposals, and legal drafts are never part of it. The pages hold no company data, show no keys, and use no analytics or tracking.

For Developers

The pages are built by bin/build-docs-site.mjs into site-data/docs-pages.generated.js and served by the workspace (src/docs-site/site.js). npm run check fails when the generated file is out of date, so a change to a guide, apps.json, tests.json, or docs/updates.json is not released until it is rebuilt. After a merge conflict in the generated file, run node bin/build-docs-site.mjs again.