Layouts, pages, components, and templates have authored CSS (css) and two derived forms: css_precompiled, generated for the resource HTML, and css_compiled, generated as a delta by the visual editor. css_source_hash records compilation provenance. The resources pipeline writes authored data to the database; css:rebuild regenerates derived CSS against the HTML in the database.
gestor_css_incluir() inserts styles marked by role (authored, compiled, and data-tailwind-role values), deduplicating them by hash. gestor_pagina_css() combines default, project, precompiled, editor, and authored CSS in a defined order. A dependency selected only at runtime, such as a template by target, must be listed in tailwind_dependencies so its classes are compiled.
Tailwind resources have per-resource precompiled CSS; an isolated global stylesheet does not replace the page CSS. The editor must accumulate the baseline for inserted sections so its delta retains the rules visitors see.
Dashboard widget compilation
In a widget iframe, partial precompiled sheets must precede the browser compiler. Its complete sheet comes last within utilities; otherwise an unresponsive utility in a later partial sheet can override a responsive one. The theme contract supplies tokens to the isolated document. Authored unlayered CSS keeps precedence. Public presentations omit the template partial sheet after the page sheet; they retain authored template CSS and extra head. This prevents responsive slides from becoming a single column. See Dashboard.