refactor(landing): consume design-system from npm; drop local copies#35
Merged
Conversation
…al copies
The design system now lives in its own repo (agentage/design-system) and is
published to npm. Remove the duplicated local packages/design-system copy and
packages/showcase (which only rendered the DS's dev playground - that now lives
in the DS repo), and depend on @agentage/design-system@^0.3.0 instead.
- landing: dep '*' -> '^0.3.0'; the site imports @agentage/design-system/theme.css
from node_modules (JS barrel is still never imported).
- Root scripts, Dockerfile, eslint, vitest, CI: drop design-system + showcase.
- CLAUDE.md: 4 packages -> 2 (shared + landing).
Visible change: the npm DS's base.css wraps the '*{border-color}' reset in
@layer base (Tailwind v4 fix), so 'border-<color>' utilities now win. On the
homepage the 'Agentage Memory' box gets its intended primary/30 border instead
of the default dark one (utility was previously suppressed).
verify + full landing e2e (33) green.
|
✅ CI - Verify PASSED Commit:
|
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
1 participant
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
The design system now lives in its own repo (
agentage/design-system, published to npm). This removes landing's duplicated local copy and consumes the package instead.packages/design-system(duplicate) andpackages/showcase(a Next wrapper that only rendered the DS's dev playground via a relative path — that playground now lives in the DS repo and deploys tods.agentage.io).packages/landing:@agentage/design-system*→^0.3.0(npm). The site imports only@agentage/design-system/theme.css; the JS barrel is still never imported.shared+landing.The npm DS's
base.csswraps the*{border-color}reset in@layer base(the Tailwind v4 fix that was in web's copy but not landing's). Soborder-<color>utilities now win instead of being suppressed by the reset. I verified via computed styles:.border-primary/30box ("Agentage Memory")--color-border) — utility suppressedIt's a latent design-intent fix. On the homepage it affects exactly one box; site-wide it affects any colored-border utility. Since it changes the live site's appearance, I'd like your OK before merging.
Verify
npm run verify+ full landing e2e (33 passed) green locally; DS resolves from the npm tarball (@agentage/design-system@0.3.0). −10k LOC (the two deleted packages).