Tailwind is compiled per resource
Every page, layout and component carries its own compiled CSS. Pages with a responsive layout can ask for a single compilation, which preserves the order of the rules.
Until now, the Tailwind CSS was one stylesheet for the whole system. From this delivery on, each resource carries the CSS for the classes it uses, compiled at build time and delivered with the HTML.
The problem found along the way
Joining the stylesheets of several resources on the same page loses the global order of the rules. In a real case, the hidden class of a component loaded later cancelled the layout's lg:flex, and the desktop menu showed up as the mobile one.
The answer was the page bundle: a page that declares this option is compiled together with its layout and dependencies, in a single stylesheet, with the theme and base layers in the right order. Pages that do not need it keep the per-resource stylesheet.
What else landed
- The build is incremental: a resource with no changes stays cached.
- Updates preserve the compiled CSS even when the content was edited in the panel.
- The editing bar menu left the PHP code and became a component, with texts in Portuguese and English.
Source: Core · req-115 · BATCH-115