Framework-Agnostic Components

Framework-Agnostic Components Overview

At its core, framework-agnostic components is about doing one thing well inside your design systems project. Once you understand the pattern, you can apply it consistently across features and teams.

Good framework-agnostic components pays off across the whole codebase: fewer surprises, easier testing, and smoother onboarding. The snippet below is a solid starting point.

import { LitElement, html, css } from 'lit';

export class DsButton extends LitElement {
  static styles = css`
    button { padding: var(--space-2) var(--space-4); }
  `;
  render() {
    return html`<button part="button"><slot></slot></button>`;
  }
}
customElements.define('ds-button', DsButton);

Web components built with Lit work in any framework and expose CSS parts for controlled styling.

Framework-Agnostic Components Example

/* Tokens flow into components, which flow into products */
:root { --color-brand-500: #2563eb; }
.button { background: var(--color-brand-500); }

• Start from a minimal Framework-Agnostic Components example and grow it only as needed.
• Keep configuration explicit so Framework-Agnostic Components behaves the same in every environment.
• Name things clearly so teammates understand your Framework-Agnostic Components at a glance.
• Add tests around Framework-Agnostic Components early to lock in expected behaviour.

Design System Cheatsheet

Quick reference for framework-agnostic components within a modern design system.

How Framework-Agnostic Components Fits into a Design System

Framework-Agnostic Components connects the design decisions in your system to the code teams actually ship. When it is defined once and reused, products stay consistent and updates roll out everywhere.

Web components built with Lit work in any framework and expose CSS parts for controlled styling.

• Define it once as a token or shared component.
• Document intended usage with clear examples.
• Make it themeable and accessible by default.
• Version and release changes so consumers can upgrade safely.

Getting Teams to Adopt Framework-Agnostic Components

Adoption is where design systems succeed or stall. Make framework-agnostic components the easiest option: great docs, sensible defaults, and clear migration paths beat mandates every time.

Common Mistakes

• Skipping error handling and edge cases when wiring up framework-agnostic components.
• Leaving framework-agnostic components untested, so regressions slip into production.
• Over-engineering framework-agnostic components before you actually need the extra flexibility.
• Ignoring documentation, which makes framework-agnostic components hard for the next developer to change.

Key Takeaways

• Framework-Agnostic Components is a core part of working effectively with design systems.
• Start small and keep framework-agnostic components focused on a single responsibility.
• Apply consistent patterns so framework-agnostic components scales across your project.
• Test and document framework-agnostic components to keep it maintainable over time.