Contao Component Style Manager Laravel Package

Product Decisions This Supports

• Theming & Customization Roadmap: Continues to enable a scalable, maintainable approach to CSS class management in Contao CMS, now with improved backend label handling (label_callback replacement). Supports evolving design systems by reducing technical debt in class assignment workflows.
• Build vs. Buy: Buy—this package remains a cost-effective alternative to custom development, with minor API refinements that align with Contao’s backend patterns (e.g., label_callback for better UX in dropdowns).
• Use Cases:
  • Editor Workflow Improvements: The label_callback change simplifies how custom style options are displayed in backend dropdowns, reducing confusion for non-technical users.
  • Third-Party Extension Compatibility: The deprecation of child_record_callback ensures consistency with Contao’s core API, making it easier to integrate with plugins like RockSolid or custom DCA fields.
  • Migration Path: Reinforces the shift from legacy XML to YAML configs, now with cleaner backend label management for style groups.

When to Consider This Package

Adopt if:

• Your team uses Contao CMS (v5.6+) and needs a scalable, backend-driven CSS class manager with improved label handling for dropdowns (e.g., custom style groups with descriptive names).
• You’re migrating from manual class management or legacy XML solutions and want a modern YAML/config-driven approach.
• Your project involves multi-role editing (e.g., editors assigning styles via intuitive backend labels).
• You need third-party extension support (e.g., custom modules, forms) with cleaner API integration (post-child_record_callback deprecation).
• You’re building a design system and want to centralize reusable classes (e.g., btn--primary) with user-friendly backend labels.

Look elsewhere if:

• You’re not using Contao CMS (this is Contao-specific).
• Your team prefers inline CSS or CSS preprocessors (Sass/Less) over class-based styling.
• You require real-time style previews (this is backend-focused; consider frontend tools like Storybook).
• Your project has strict performance constraints (minimal overhead, but evaluate trade-offs).
• You rely on deprecated child_record_callback functionality (this release removes it; update custom integrations).

How to Pitch It (Stakeholders)

For Executives: "This updated package streamlines theming in Contao with a cleaner backend experience. The latest change (label_callback) makes it even easier for editors to assign styles—like picking a ‘Primary Button’ from a dropdown—without technical friction. It’s a low-risk upgrade that cuts dev time by eliminating scattered class definitions, while future-proofing our design system. Ideal for multi-site projects or teams with non-technical editors."

For Engineers: *"The 3.12.1 release replaces child_record_callback with label_callback, aligning with Contao’s modern API for better dropdown UX (e.g., custom style groups with readable labels). Key updates:

• Simpler backend labels: Use label_callback to customize how style options appear in dropdowns (e.g., ‘Dark Mode’ instead of theme--dark).
• Third-party friendly: Deprecates child_record_callback to match Contao’s core patterns, easing integration with plugins.
• No breaking changes: Existing configs using child_record_callback will need updates, but the trade-off is cleaner, more maintainable code. Use case: Perfect for projects with 5+ Contao sites or complex theming—reduces dev overhead while improving editor workflows."*

For Editors/Designers: "Now you’ll see clearer, more descriptive style names in the backend dropdowns (e.g., ‘Large Text’ instead of text--xl). No more guessing what a class does—just pick what you need and apply it to pages, buttons, or layouts. Even easier than before!"