Introduction
In version 2 of our design system, Block was a straightforward component whose primary purpose was to apply specific CSS properties through attributes. It inherited the same styling logic as Base, allowing developers to add layout or display-related properties without manually writing repeated class names.
Why It’s Discontinued
Like Base, Block became unnecessary with our shift to Tailwind CSS in version 3. Tailwind’s utility-first approach lets developers apply equivalent (or more precise) styling directly in their markup. This eliminates the need for an extra component wrapper and simplifies the development process.
For a deeper explanation of how to migrate from attribute-based styling to Tailwind utilities, refer to the Base page. You’ll find more details on the underlying reasons for the change, along with best practices for transitioning your existing components to a utility-first approach.