All bites
The whole library, newest first. Filter by what you are here for, or pick a topic if you already know.
8668 bites
Page 40
Governance model for specialized contributions
Define a governance model, RFC and shared-need gate, tiered intake (core vs community), CI and CODEOWNERS review, then versioned release.
Essential docs for onboarding a new team
Getting-started guide, per-component API and usage docs, design guidelines and tokens, plus changelog and migration notes.
Bug report to deployed fix workflow
Triage and reproduce, write a failing test, fix it, pass CI gates and review, then patch-release and notify.
Designing a component deprecation process
Announce with a replacement and timeline, mark deprecated with runtime and lint warnings, provide codemods, then remove only in a major release.
Classifying a visually breaking padding change
A layout-shifting padding change is effectively breaking, so major; release with visual diffs, a migration note, and a token or opt-in path.
Purpose and key sections of CONTRIBUTING.md
It documents how to contribute; key sections are setup and dev workflow, contribution process and standards, and review and release expectations.
Deciding whether a one-off variant belongs in core
Weigh reuse and consistency against maintenance cost, then decide with a shared-need bar and escape hatches for local cases.
Contributor workflow from proposal to merge
Proposal or RFC, design and core alignment, branch and build with tests and docs, review, then merge and release.
Reversing stagnating design system adoption
Find friction via interviews, reduce it with DX, codemods, and docs, then prove value with adoption and velocity metrics.
Building a design system quarterly roadmap
Combine usage and adoption data, support tickets, stakeholder interviews, and a debt ledger into a scored backlog with a deliberate debt allocation.
Designing a contribution model with quality gates
Define a federated model, branch-and-PR flow, required reviews, and automated gates for tests, a11y, and visual regression.
Process for adding a new component
Triage need, design and spec, build with a11y and tests, document, version, and release.
Core roles on a design system team
Name design, engineering, product/PM, and accessibility/docs roles with clear ownership.
Shadow DOM accessibility: focus and cross-boundary ARIA
IDREF ARIA can't cross the shadow boundary, so aria-labelledby and aria-activedescendant break; delegatesFocus and ElementInternals/ARIAMixin help.
Adapting CSS for Forced Colors Mode
Use semantic HTML and system color keywords, the forced-colors media query, forced-color-adjust sparingly.
Accessible toasts with ARIA live regions
A persistent live region, polite vs assertive by urgency, role status or alert, content injected after mount.
Enforcing an accessible name on icon-only buttons
Require aria-label via the type system for icon-only variants, warn at runtime, decorate the icon as aria-hidden.
ARIA roles and keyboard nav for a Tabs component
Tablist, tab, tabpanel roles with aria-selected and aria-controls; arrow keys move tabs, Tab moves to the panel via roving tabindex.
Enforcing WCAG color contrast programmatically
Pre-validate token pairs, expose only safe semantic combos, lint and test contrast in CI.
Managing keyboard focus in an accessible Modal
Move focus in on open, trap Tab inside, close on Escape, restore focus to the trigger on close.