Read this first
This site is for staff developers of WPCloudCMS. It is behind Cloudflare Access with the staff
group. Everyone else, customers on any plan included, reads docs.wpcloudcms.com.
The rule for what goes where
Section titled “The rule for what goes where”| Site | Audience | May contain |
|---|---|---|
docs.wpcloudcms.com |
every customer, on every plan | how to use the product, including self-hosted installs. No stack names, no internal hosts, no key names |
admin-docs.wpcloudcms.com (here) |
staff developers only | architecture, agent internals, node inventory, ops runbooks |
There is no third site and no per-plan site: plans (starter, business, agency, enterprise) change at any time, so documentation never depends on one. A customer upgrading or downgrading must never lose a bookmark. The only split is staff versus everyone else, enforced by a Cloudflare Access group on this hostname alone.
Anything that names a server, a port, a key reference or a credential path belongs here, never in the public site and never in the repository we hand to an enterprise customer.
Where the real documentation lives
Section titled “Where the real documentation lives”The repository is the source of truth, and it is versioned with the code:
CLAUDE.md— how to work in the repo, hard rules, gotchasWPCLOUDCMS-OVERVIEW.md— the product and its architectureROADMAP.md— phases and what is nextCHANGELOG.md— what was actually done, with measured evidencedocs/environment.md— every environment fact: nodes, ports, paths, credentials by namedocs/wpcloudcms-control-plane-spec.md— the contract: endpoints, tools, tables
These pages exist so a new staff developer can find their way in without a tour. They do not duplicate the repo; when the two disagree, the repo wins.
Non-negotiables
Section titled “Non-negotiables”- Secrets never appear in documentation. Credentials are referenced by name, stored in the credential manager, and never written into a page, a commit or a chat.
- Every claim about behaviour is measured, not remembered. If a page says an endpoint returns
422, someone ran it.