Tasty is a styling engine for design systems that turns component state into deterministic CSS by compiling state maps into mutually exclusive selectors. Use this hub to choose the right guide once you know whether you are evaluating the model, adopting it in a design system, or implementing reusable, stateful components day to day.
- New to Tasty: Getting Started for installation, the first component, optional shared
configure(), ESLint, editor tooling, and rendering mode selection. - Learning the component model: Methodology for root + sub-elements,
styleProps, tokens, extension, and recommended boundaries betweenstyles,style, and wrappers. - Evaluating the selector model: Style rendering pipeline for how mutually exclusive selectors make stateful styling deterministic.
- Evaluating fit: Comparison for tool-selection context, then Adoption Guide for audience fit and rollout strategy inside a design system.
- Application developer using an existing design system: Getting Started, then Runtime API.
- Design-system author: Methodology, Building a Design System, Configuration, and Adoption Guide.
- Platform or tooling engineer: Configuration, Zero Runtime (tastyStatic), Server-Side Rendering, and Debug Utilities.
- Runtime React components: Runtime API
- Zero-runtime / build-time extraction: Zero Runtime (tastyStatic)
- Runtime
tasty()with server collection and hydration: Server-Side Rendering
- Learn the style language: Style DSL
- Look up a property handler: Style Properties
- Define tokens, units, recipes, keyframes, or properties globally: Configuration
- Debug generated CSS or cache behavior: Debug Utilities
- Understand how selector generation works internally: Style rendering pipeline
- Understand runtime injection internals: Style Injector