docs(docsite): replace stale XDS references with Astryx#3425
Merged
Conversation
Continues the XDS->Astryx cleanup, scoped to the docsite and the core README.
Fixes several user-facing correctness issues alongside brand/comment cleanup:
- InteractivePreview generated example code as <XDS${Name}> (e.g. <XDSButton />),
but the real exports are bare (<Button />); users copy-pasted invalid code.
- ThemeEditor showed theme-override selectors as .xds-<component>; the real
stable class prefix is astryx- (.astryx-<component>).
- core/README.md documented non-existent component names (XDSLayout, XDSAppShell,
XDSTopNav, XDSSideNav) and an "XDS CLI" section; corrected to bare names
(Layout/AppShell/TopNav/SideNav) and "Astryx CLI". Updated the docsite's
coupled CORE_STRIP_SECTIONS array to match the renamed heading.
- blog authors.ts JSDoc referenced a non-existent 'xds-team' author key; the
real key is 'team'.
- Renamed internal codegen vars (xdsTokens/xdsTypes/xdsFiles/xdsListStyle) and
updated the one coupled test assertion.
- Scrubbed Meta-internal references that had leaked into this public repo: an
internal 'nest/apps/xds' path and several internal Phabricator IDs in comments.
Legacy XDS-prefix resolution fallbacks (and the tests that pin them), the
"Astryx (XDS)" MCP tool descriptions kept for discoverability, and the
__xds_preview_* runtime window globals are intentionally left for a later pass.
ejhammond
requested review from
cixzhang,
imdreamrunner,
josephfarina,
marie-lucas,
nynexman4464 and
thedjpetersen
as code owners
meta-cla
Bot
added
the
CLA Signed
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
PR Analysis Report📚 Storybook PreviewView Storybook for this PR 🧪 Sandbox PreviewView Sandbox for this PR No new or modified components detected. Bundle Size Summary
Accessibility AuditStatus: No accessibility violations detected. Generated by PR Enrichment workflow | Storybook | Sandbox | View full report |
thedjpetersen
approved these changes
Jul 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Second pass of the XDS → Astryx cleanup, scoped to the docsite and the core README. Like the first pass, this is more than cosmetics — several stale references were producing wrong user-facing output.
Stacks conceptually on #3422 (the three files already touched there — docsite
README.md,blog/README.md,analytics.ts— are excluded here to avoid conflicts).Correctness fixes (user-facing)
generateCodeemitted<XDS${Name} ... />(e.g.<XDSButton />), but the real exports are bare (<Button />). Users were copy-pasting code that doesn't compile. Now emits the bare name..xds-<component>, but the real stable class prefix isastryx-. Now shows.astryx-<component>.packages/core/README.md— documented component names that don't exist (XDSLayout,XDSAppShell,XDSTopNav,XDSSideNav) and an## XDS CLIsection. Corrected to the real bare exports (Layout/AppShell/TopNav/SideNav) and## Astryx CLI. The docsite's coupledCORE_STRIP_SECTIONSarray (which strips that heading from the rendered package page) was updated in lockstep.authors.ts— JSDoc referenced a non-existentxds-teamauthor key; the real registry key isteam.Cleanup
XDS→Astryxin docsite comments, JSDoc, landing-page/playground/theme prose.xdsTokens,xdsTypes,xdsFiles,xdsListStyle) and updated the one coupled test assertion (playground-scope.test.ts).Meta-internal leaks scrubbed (public repo)
Ported from the internal docsite (nest/apps/xds)comment.P…) from four comments describing the un-prefix migration.Deliberately out of scope
Left for a later, more careful pass (per the "keep it safe" directive):
/^XDS/-stripping and?? readExport(\XDS${name}`)**fallback resolution logic** (generate-data.mjs,mcp/route.ts,componentInstances.ts,parsePropType.ts,resolveElements.ts,changelogLinkify.ts`) and the tests that pin that behavior. These are harmless today (doc names are already bare) but interconnected."Astryx (XDS)"MCP tool descriptions — intentionally keep "XDS" for search discoverability (there's a test asserting this).__xds_preview_*runtime window globals (an observable contract).Testing
pnpm -F @astryxdesign/docsite generate && test— pass (210 tests), including the coupledplayground-scopeandmcp-serversuites.check:changesets,sync-exports --check,check-sync— pass.