Skip to content

Rewrite reference page descriptions (next trees)#2711

Open
ctauchen wants to merge 1 commit intotigera:mainfrom
ctauchen:descriptions-reference
Open

Rewrite reference page descriptions (next trees)#2711
ctauchen wants to merge 1 commit intotigera:mainfrom
ctauchen:descriptions-reference

Conversation

@ctauchen
Copy link
Copy Markdown
Collaborator

@ctauchen ctauchen commented May 8, 2026

Summary

Rewrites the description frontmatter on every page in the reference book across the three unversioned (next-release) source trees — 333 files, 1-line replacement each. Same rule set as #2696, #2697, and #2710.

Tree Files
calico/reference/ 113
calico-enterprise/reference/ 139
calico-cloud/reference/ 81
Total 333

This PR is next-only on purpose — landing on the unversioned source first so the descriptions can get review without being pre-mirrored to versioned snapshots that would all need amending if anything changes. After review, I will mirror to the published latest-version snapshots in a follow-up.

Intentionally skipped

Five files in */reference/installation/ are not touched:

  • calico/reference/installation/_api.mdx
  • calico-enterprise/reference/installation/_api.mdx
  • calico-cloud/reference/installation/_api.mdx
  • calico-cloud/reference/installation/_ia-api.mdx — the four auto-generated CRD reference files, regenerated from the operator schema (already excluded by .vale.ini).
  • calico-cloud/reference/installation/_README.mdx — developer-only README with no frontmatter; underscore-prefixed so Docusaurus excludes it from the build.

What every new description follows

  1. Names exactly one canonical product (Calico Open Source, Calico Enterprise, Calico Cloud).
  2. ≤ 200 characters.
  3. Reference content is mostly noun-led per the docs-frontmatter-description skill — "reference" is worked into the sentence rather than used as a label prefix.
  4. No enable, disable, or teaching.
  5. Unique across products. Many CRDs (FelixConfiguration, BGPConfiguration, HostEndpoint, etc.) and many calicoctl commands exist identically in all three products; those are disambiguated by canonical product name and product-specific context.
  6. Vale-clean on line 2 (frontmatter description line) — no data plane/dataplane, IPAM/ipam, BGP/bgp term-rule violations.

Cross-product disambiguation

Reference is dominated by CRD docs and command-line reference. Disambiguation strategy:

  • Calico Open Source — bare-resource framing: ... resource in Calico Open Source ..., calicoctl ..., upstream-project context.
  • Calico Enterprise — enterprise-feature framing: ... resource in Calico Enterprise ..., references to tiers, recommendations, observability, the management UI.
  • Calico Cloud — connected-cluster / SaaS framing: ... resource in Calico Cloud connected clusters ..., Calico Cloud web console, "across connected clusters."

For functionally identical CRDs the canonical product name in the resource phrasing is the primary disambiguator.

What was wrong before

Pre-fix snapshot of the same files:

  • 0 forbidden-word hits — none in this bucket pre-fix.
  • 0 descriptions over 200 chars — none in this bucket pre-fix.
  • 2 missing description fields — both filled in.
  • 73 cross-product literal duplicates covering 257 files — any CRD or command shared across two or three products had identical descriptions. Most-duplicated phrases were short generic stubs like Configure Resource requests and limits., Command to apply a policy., Command to delete a policy., REST API reference, plus the entire calicoctl command surface. All disambiguated by the rules above.

Verification

Run from repo root on this branch:

grep -nEri "^description:.*\b(enable|disable|teaching)\b" \
  calico/reference calico-enterprise/reference calico-cloud/reference

Length, canonical-name presence, and cross-product-uniqueness checks are equivalent one-liners over the same three directories. All four return empty post-fix.

Test plan

  • Run the forbidden-word grep above and confirm empty.
  • Spot-check a cross-product CRD trio (e.g., resources/felixconfiguration.mdx, resources/bgpconfiguration.mdx, resources/hostendpoint.mdx) for distinguishability.
  • Spot-check the calicoctl command surface across calico/ and calico-enterprise/.
  • Spot-check 5 random rewrites against page bodies for accuracy.
  • After review, mirror to latest-version snapshots (calico_versioned_docs/version-3.32/reference/, calico-enterprise_versioned_docs/version-3.23-1/reference/, calico-enterprise_versioned_docs/version-3.22-2/reference/, calico-cloud_versioned_docs/version-22-2/reference/).

Replaces the description frontmatter on every reference page across the
three unversioned source trees with descriptions that name one canonical
product, fit in 200 chars, and disambiguate identically-named CRDs and
calicoctl commands across products. No body changes; one line per file.

The four auto-generated _api.mdx / _ia-api.mdx files are intentionally
skipped (regenerated from the operator schema, already excluded by Vale).
The unversioned _README.mdx in calico-cloud/reference/installation/ is
also skipped because it has no frontmatter (developer-only file).
@ctauchen ctauchen requested a review from a team as a code owner May 8, 2026 16:26
Copilot AI review requested due to automatic review settings May 8, 2026 16:26
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

@netlify
Copy link
Copy Markdown

netlify Bot commented May 8, 2026

Deploy Preview for calico-docs-preview-next ready!

Name Link
🔨 Latest commit 3897fc7
🔍 Latest deploy log https://app.netlify.com/projects/calico-docs-preview-next/deploys/69fe0ea37f6d78000839ab59
😎 Deploy Preview https://deploy-preview-2711--calico-docs-preview-next.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link
Copy Markdown

netlify Bot commented May 8, 2026

Deploy Preview succeeded!

Built without sensitive environment variables

Name Link
🔨 Latest commit 3897fc7
🔍 Latest deploy log https://app.netlify.com/projects/tigera/deploys/69fe0ea37f6d78000839ab54
😎 Deploy Preview https://deploy-preview-2711--tigera.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 64 (🔴 down 23 from production)
Accessibility: 98 (no change from production)
Best Practices: 83 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

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.

2 participants