Add developer section and reconcile wiki with theme implementation
Use the umdlib_umdds theme (DESIGN-SYSTEM.md, css/base.css, component
schemas) as the source of truth to update the wiki and document, for the
first time, how to build a component that matches the design system.
New "For Developers" section:
- For-Developers: two-layer token model, the golden rule, no-build note
- Design-Tokens-and-Utility-Classes: c-/t-/s-/ani- reference, the
.button.umd-lib base class, and the no-border-radius house rule
- Building-a-Component: SDC anatomy, spacing/color/type rules, Part D
house rules, error-chip fallback, card example, 60-second checklist
New Foundations token pages (real values from base.css):
- Design-Tokens, Color, Spacing; folded the t-* ramp into Typography
Reconcile component pages with their .component.yml:
- Card: document the card_url_optional prop
- CTA Button: document the .button.umd-lib / .secondary base class
- Navigation: search is now props (+ sub_site); drop the stale WYSIWYG
search slot
- Accordion: mark the Accordions wrapper deprecated; single-component model
- Icon: note Lucide is bundled and used via data-lucide
Wire up navigation: _Sidebar, Foundations, Components (add Component
Layout, fix Navigation description), and a developer pointer on Home.
Excludes the badge/stat/cta-banner teaching components and the button
(base class only) from editor-facing docs.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>