Skip to content

docs: render provider name as "PCD" in generated doc titles - #41

Merged
PF9-pushkar merged 1 commit into
mainfrom
pushkar/docs-provider-title
Aug 12, 2026
Merged

docs: render provider name as "PCD" in generated doc titles#41
PF9-pushkar merged 1 commit into
mainfrom
pushkar/docs-provider-title

Conversation

@PF9-pushkar

Copy link
Copy Markdown
Collaborator

What

Capitalizes the provider name in generated documentation so the Registry shows "PCD Provider" instead of "pcd Provider", and resource page titles read "… - PCD" instead of "… - pcd".

Implemented by passing --rendered-provider-name PCD to tfplugindocs, wired into both make generate and the CI docs job so they stay in sync. Docs regenerated accordingly (78 pages).

Why

tfplugindocs defaults the rendered provider name to the lowercase registry short name (pcd), which reads as unpolished in the overview heading and page <title>s.

Scope / what does NOT change

  • Resource & data-source type names (pcd_networking_network, …) stay lowercase — verified 0 type names were altered.
  • The provider's registry address platform9/pcd is unchanged (immutable; that's the published source).
  • The large provider title, breadcrumb, and left-nav "pcd provider" label come from the registry name itself and remain lowercase — this is conventional for every provider (aws, google, azurerm) and not controllable from the repo.

Rollout

Docs-only. Appears on the Registry once a release tag containing it is published (proposed v0.1.2).

The overview heading rendered as "pcd Provider" and each resource/data-source
page title as "... - pcd", using the lowercase registry short name. Pass
--rendered-provider-name PCD to tfplugindocs (in `make generate` and the CI docs
job) so the human-facing provider name renders as PCD.

Resource/data-source type names (pcd_*) and the registry address platform9/pcd
are unchanged. Docs-only.
@PF9-pushkar
PF9-pushkar merged commit ca54203 into main Aug 12, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant