/* * Tailwind utility classes that need to be available even when the * SSR-rendered DOM doesn't contain them (e.g. pages/community/blog.vue * which SSRs a skeleton-loading state before async data arrives, so * Tailwind's content scan doesn't pick up bg-pink-13 / text-alert-error * from the active-filter button and prunes them from the inline * critical CSS — leaving the pill unstyled on first visit until the * JS-loaded chunk lands). * * Served from /public/ → Nuxt does NOT process this through its * per-page CSS extractor, and we link it directly from via * nuxt.config.ts's `app.head.link` config so it loads in parallel * with the HTML on every page. * * Values mirror tailwind.config.js theme.colors: * pink.13 = #FFCCD3 * alert.error = #D97481 * secondary = #F7F7F9 */ .bg-pink-13 { background-color: #FFCCD3; } .hover\:bg-pink-13:hover { background-color: #FFCCD3; } .text-alert-error { color: #D97481; } .hover\:text-alert-error:hover { color: #D97481; } .bg-secondary { background-color: #F7F7F9; }