cf-docs-rfc-proposal

Research areas

Status: draft Docs WG position, incomplete — covers what is known as of 2026-10-10.

Questions the requirements depend on that nobody has answered yet. For each: why it matters, what is known, and what would answer it. Requirement IDs refer to the requirement list. The RFC is cloudfoundry/community#1642, the draft request for comments that proposes the new docs stack; quotes from it link to their line, as in L112 (glossary).

Scope

Which repositories feed the docs, and who owns each?

Is bosh.io in scope?

How do the UAA and CredHub API references fit?

What do downstream consumers reuse?

Content

Are partial names in variables still needed?

What should undefined variables show?

Which table styles beyond the standard one?

What do the concepts not yet worked require?

Site and services

Does “open source only” cover services?

What does search do today?

How should versions work?

Should the site publish an llms.txt file?

Who controls hosting and the domain today?

Which old redirects carry over?

Governance

Who maintains shared extensions, and how does a working group ask for one?

Who staffs the central migration team?