pub const CSS_LAYER: &str = "makeover";Expand description
The cascade layer every stylesheet the make-family generates is wrapped in.
One name shared by every emitter in the family, so an app writes it once and the design system’s output lands in one place it can order against:
@layer makeover, base, components, responsive;§Why a layer at all
The cascade resolves origin and importance, then layer, then specificity, then source order, and unlayered normal declarations outrank every named layer. So the moment an app declares any layer of its own, every rule it owns loses to unlayered generated CSS regardless of specificity or of loading last. Emitting into a layer is what stops that, and putting the name here rather than in each app is what stops three apps picking three names.
§Why this constant lives in the geometry crate
Not because spacing owns it. This crate is the only one every CSS-emitting
crate in the family already depends on, and it is already the crate that
spells CSS for the family (media_condition, Step::token, Ratio::css).
A second copy in makeover-webview is exactly the drift
Density::media_condition exists to prevent, one layer up.