Skip to content

chore: tail-end Starlight->Nimbus migration cleanup#32250

Merged
mvvmm merged 2 commits into
productionfrom
chore/post-migration-cleanup-followups
Jul 22, 2026
Merged

chore: tail-end Starlight->Nimbus migration cleanup#32250
mvvmm merged 2 commits into
productionfrom
chore/post-migration-cleanup-followups

Conversation

@mvvmm

@mvvmm mvvmm commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Summary

Tail-end cleanup pass identified after the Starlight→Nimbus migration (#32229) and the src/nimbussrc promotion (#32249). Scoped to dead paths and stale style-guide content that still describes the site's old architecture. (The astro-config.ts I/O optimization and .git-blame-ignore-revs removal that were originally bundled here have been split into their own PRs: #32252 and #32253.)

Dead paths

  • .github/CODEOWNERS/src/nimbus/pages/agent-setup no longer exists post-promotion; that team currently has zero CODEOWNERS coverage on the real /src/pages/agent-setup directory. Fixed.
  • style-guide/how-we-docs/metadata.mdx — dead GitHub link to src/nimbus/schemas (now src/schemas).

Style-guide content batch (11 pages)

These pages describe our own component library and framework to authors — several still claimed the site runs on Starlight, or referenced removed community packages (starlight-package-managers, starlight-links-validator) instead of their Nimbus/local equivalents. Two are genuine functional breaks, not just wording:

  • icons.mdx had a copy-pasteable example importing StarlightIcon from ~/components — that export doesn't exist. Replaced with the real Card/LinkCard icon string-prop API.
  • badges.mdx instructed readers to apply an sl-badge CSS class to restyle a span — that class doesn't exist on the ported Badge component anymore (styling is computed inline via Tailwind). Removed the now-broken instruction.
  • ai-consumability.mdx claimed Cloudflare's Markdown-for-Agents network layer transforms a starlight-tabs custom element — Nimbus's Tabs component doesn't render that element at all anymore (verified: it's a plain <div data-nb-tabs>). Generalized the wording rather than asserting something about an external system I can't verify from this repo — worth a cross-team check on whether that transform pipeline still handles Nimbus's actual Tabs markup for AI-agent consumption.
  • The rest (cards.mdx, file-tree.mdx, package-managers.mdx, rss-button.mdx, frontmatter/index.mdx, frontmatter/custom-properties.mdx, directory-listing.mdx, content-types/overview.mdx, our-site.mdx, links.mdx) — swapped stale Starlight attributions/links for the real Nimbus equivalents (nimbus-docs.com has its own public docs site).

Verification

  • pnpm run check / lint / format:check / test all clean
  • Full pnpm run build succeeds locally (8709 pages)
  • pnpm run test:postbuild passes

Documentation checklist

@github-actions

github-actions Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/.github/CODEOWNERS @cloudflare/product-owners, @cloudflare/content-engineering, @kodster28
/src/content/docs/style-guide/ @dcpena, @caley-b, @cloudflare/product-owners

@github-actions

github-actions Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Preview URL: https://487ca8f1.preview.developers.cloudflare.com
Preview Branch URL: https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link Updated Link
https://developers.cloudflare.com/style-guide/components/icons/ https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com/style-guide/components/icons/
https://developers.cloudflare.com/style-guide/how-we-docs/links/ https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com/style-guide/how-we-docs/links/
https://developers.cloudflare.com/style-guide/components/badges/ https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com/style-guide/components/badges/
https://developers.cloudflare.com/style-guide/components/rss-button/ https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com/style-guide/components/rss-button/
https://developers.cloudflare.com/style-guide/frontmatter/ https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com/style-guide/frontmatter/
https://developers.cloudflare.com/style-guide/how-we-docs/our-site/ https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com/style-guide/how-we-docs/our-site/
https://developers.cloudflare.com/style-guide/components/cards/ https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com/style-guide/components/cards/
https://developers.cloudflare.com/style-guide/components/directory-listing/ https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com/style-guide/components/directory-listing/
https://developers.cloudflare.com/style-guide/components/file-tree/ https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com/style-guide/components/file-tree/
https://developers.cloudflare.com/style-guide/components/package-managers/ https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com/style-guide/components/package-managers/
https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/overview/ https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/overview/
https://developers.cloudflare.com/style-guide/frontmatter/custom-properties/ https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com/style-guide/frontmatter/custom-properties/
https://developers.cloudflare.com/style-guide/how-we-docs/ai-consumability/ https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com/style-guide/how-we-docs/ai-consumability/
https://developers.cloudflare.com/style-guide/how-we-docs/metadata/ https://chore-post-migration-cleanup-followups.preview.developers.cloudflare.com/style-guide/how-we-docs/metadata/

Small cleanup pass identified after the Starlight->Nimbus migration
and the src/nimbus->src promotion:

- .github/CODEOWNERS: fix dead /src/nimbus/pages/agent-setup path (no
  longer exists post-promotion) to /src/pages/agent-setup. That team
  had zero CODEOWNERS coverage on the real directory.
- style-guide/how-we-docs/metadata.mdx: fix dead GitHub link to
  src/nimbus/schemas (now src/schemas).
- Batch content fix across 11 style-guide pages that still described
  the site as running on Starlight, or referenced now-removed
  Starlight/community packages (starlight-package-managers,
  starlight-links-validator) instead of their Nimbus/local
  equivalents:
  - our-site.mdx: framework description now points to nimbus-docs.com
    instead of starlight.astro.build (and no longer misattributes a
    Hugo->Starlight blog post to a "choosing Nimbus" claim it doesn't
    make).
  - links.mdx: replaces the removed starlight-links-validator
    reference and a dead <GitHubCode> snippet (pinned to an ancient
    commit's now-nonexistent line numbers) and a phantom CI env var
    link with an accurate description of Nimbus's nimbus/internal-link
    rule.
  - icons.mdx: replaces a genuinely broken example (`import {
    StarlightIcon } from "~/components"` — this export doesn't exist)
    with the real Card/LinkCard `icon` string-prop API, and notes the
    legacy seti:/bare-name compat mapping for existing content.
  - badges.mdx: removes an instruction to apply a `sl-badge` CSS class
    that no longer exists on the ported Badge component (styling is
    now computed inline via Tailwind, not exposed as a class).
  - cards.mdx, file-tree.mdx, package-managers.mdx, rss-button.mdx,
    frontmatter/index.mdx, frontmatter/custom-properties.mdx,
    directory-listing.mdx, content-types/overview.mdx: swap Starlight
    framework/package attributions and dead starlight.astro.build
    links for the real Nimbus component/docs equivalents.
  - ai-consumability.mdx: the claim that Cloudflare's Markdown-for-
    Agents network layer transforms a `starlight-tabs` custom element
    is no longer accurate — Nimbus's Tabs component doesn't render
    that custom element at all (confirmed: it's a plain `<div
    data-nb-tabs>`). Generalized the wording since verifying/fixing
    that external transform pipeline is out of scope here; flagging
    this as worth a cross-team follow-up separately.

Verified: pnpm run check/lint/format:check/test all clean, full build
succeeds (8709 pages), test:postbuild passes.
@mvvmm
mvvmm force-pushed the chore/post-migration-cleanup-followups branch from 5767466 to 30dd3e6 Compare July 22, 2026 19:59
@mvvmm mvvmm changed the title chore: post-migration follow-ups — dead paths, stale style-guide docs, I/O fix chore: tail-end Starlight->Nimbus migration cleanup Jul 22, 2026
@mvvmm
mvvmm marked this pull request as ready for review July 22, 2026 20:06
@mvvmm
mvvmm requested review from a team and kodster28 as code owners July 22, 2026 20:06
@cloudflare-docs-bot

cloudflare-docs-bot Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Review

💡 2 suggestions found in commit 487ca8f.

👉 Fix in your agent 👈
Fix the following review findings in PR #32250 (https://github.com/cloudflare/cloudflare-docs/pull/32250).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
  or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.

The comment must come before the commit — the bot reads PR comments when a new
push triggers a review, so skip comments posted after the push will be missed.

---

## Code Review

### Suggestions (1)

#### CR-d80037644640 · Redundant external link
- **File:** `src/content/docs/style-guide/frontmatter/index.mdx` line 75
- **Issue:** The added line repeats the same Nimbus frontmatter documentation link that already appears on line 26 of the same page.
- **Fix:** Remove the duplicate link at line 75 so the page references Nimbus's frontmatter documentation only once.

---

## Style Guide Review

### Suggestions (1)

#### SG-dae8ed72eb0f · Active voice
- **File:** `src/content/docs/style-guide/components/icons.mdx` line 35
- **Issue:** Added sentence uses passive voice: "These are automatically mapped to an equivalent iconify icon at build time."
- **Fix:** Rewrite in active voice, for example: "The build automatically maps these to an equivalent iconify icon."

Code Review

This code review is in beta and may not always be helpful — use your judgment.

Suggestions (1)
File Issue
style-guide/frontmatter/index.mdx line 75 Redundant external link — The added line repeats the same Nimbus frontmatter documentation link that already appears on line 26 of the same page. Fix: Remove the duplicate link at line 75 so the page references Nimbus's frontmatter documentation only once.

Conventions

No convention issues found.

Style Guide Review

Suggestions (1)
File Issue
style-guide/components/icons.mdx line 35 Active voice — Added sentence uses passive voice: "These are automatically mapped to an equivalent iconify icon at build time." Fix: Rewrite in active voice, for example: "The build automatically maps these to an equivalent iconify icon."

Acknowledged by author (2)
Review File Issue Note
Code style-guide/frontmatter/index.mdx line 26 Unverified external documentation link The author says they verified the link is a live, public Nimbus documentation page and is correct as-is.
Code style-guide/frontmatter/index.mdx line 75 Unverified external documentation link The author says they verified the link is a live, public Nimbus documentation page and is correct as-is.
Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command Description
/review Runs a review now. Incremental if a prior review exists, full if not.
/full-review Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.
/rebase Rebases the PR branch against production. On conflict, attempts to resolve automatically using AI. Stops with an explanation if confidence is not high enough.

@mvvmm

mvvmm commented Jul 22, 2026

Copy link
Copy Markdown
Contributor Author

Skipping 2 findings from the code-review bot pass:

CR-4ebcc63c55df and CR-57734aec1a56 (unverified https://nimbus-docs.com/writing/frontmatter/ link, lines 26 and 75 of frontmatter/index.mdx) — I verified this link directly while researching the original fix (fetched nimbus-docs.com and its nav during the migration audit): it's a real, live, public documentation site for the Nimbus framework (marked "WIP" but structured and reachable), and /writing/frontmatter/ is a listed page in its nav. The bot's heuristic (no other repo reference + Nimbus being described elsewhere as an internal Cloudflare package) is reasonable on its face, but doesn't hold here — the link is correct. Not fixing.

Fixing the 2 style-guide findings (SG-1494a493ee02, SG-56958ba6eade) in the next commit.

…on sentence)

- frontmatter/index.mdx: remove 'please' per style guide (avoid please)
- components/icons.mdx: split a semicolon-joined sentence into two

Skipped 2 code-review findings about the nimbus-docs.com link possibly
being dead/unverified — confirmed live and correct, posted reasoning
as a PR comment.
@mvvmm
mvvmm merged commit b650262 into production Jul 22, 2026
13 checks passed
@mvvmm
mvvmm deleted the chore/post-migration-cleanup-followups branch July 22, 2026 20:56
@eeryngloriani-sudo

eeryngloriani-sudo commented Jul 22, 2026 via email

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants