twig-component

Symfony UX TwigComponent lets you build reusable UI components by creating class-based PHP components or anonymous Twig-only blocks, defining props and blocks, then rendering them across templates to eliminate duplication.

Class-based Twig components use PHP backing and the AsTwigComponent attribute for logic-heavy widgets, while anonymous Twig components are purely presentational blocks defined in Twig templates without any PHP class required.

Yes, you need the Symfony UX TwigComponent integration installed and configured in your Symfony project, along with the AsTwigComponent attribute, to enable class-based component functionality, props, blocks, and lifecycle hooks.

Yes, Twig components support props, computed properties, blocks or slots, and dynamic attributes, allowing you to build flexible design-system components like cards, buttons, modals, forms, and dashboards with customizable inputs.

The best way to structure a design system with Twig components is to create reusable class-based or anonymous components for UI elements like cards and modals, using props and blocks to manage presentation variations and reduce maintenance.

You should avoid using Twig components when a template block requires no reuse or composition, as the overhead of defining props and PHP backing for simple, one-off presentational markup outweighs the benefits of componentization.