/* * This is a manifest file that'll be compiled into application.css. * * With Propshaft, assets are served efficiently without preprocessing steps. You can still include * application-wide styles in this file, but keep in mind that CSS precedence will follow the standard * cascading order, meaning styles declared later in the document or manifest will override earlier ones, * depending on specificity. * * Consider organizing styles into separate files for maintainability. */ .alphabet-logo { position: relative; display: inline-block; } .alphabet-before { position: absolute; top: 0; right: 100%; white-space: nowrap; pointer-events: none; z-index: 1; } .alphabet-after { position: absolute; top: 0; left: 100%; white-space: nowrap; pointer-events: none; z-index: 1; } .alphabet-main { position: relative; z-index: 2; } .art-text { position: relative; right: 0.5em; z-index: 3; } /* * The mobile nav dropdown. * * Open/closed is the native `hidden` attribute, not a Tailwind `hidden` class, * and this rule is the one that has to be unbeatable — a menu that will not * hide is a menu permanently covering the page under it. * * `!important` rather than specificity, on purpose. The panel's colours come * from Themes::Css::APP_RULES, which the layout emits as an UNLAYERED inline *