Andreas Reinhold / reiniandClaude Opus 5
1075305a9c
Plan step 33. The Workbench imports foundation.css ahead of @import 'tailwindcss', so the material layers are declared first and sit below Tailwind's, then tailwind.css: the theme, the token utilities and the component stylesheets still written for Tailwind, with no tokens, so nothing is declared twice. material.css keeps working for 1.x-style imports after Tailwind by bringing the tokens, the hiding rules and tailwind.css, and never the reset, which would outrank Tailwind's utilities from there. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9
12 lines
591 B
CSS
12 lines
591 B
CSS
/* The Workbench builds the package as an application would, with explicit sources so the plans
|
|
in docs/ are not scanned for class names. The foundation comes before Tailwind, so the
|
|
`material` layers are declared first and sit below Tailwind's; tailwind.css brings the
|
|
components still written for Tailwind, without declaring the tokens a second time. */
|
|
@import '../../../resources/css/foundation.css';
|
|
@import 'tailwindcss' source(none);
|
|
@import '../../../resources/css/tailwind.css';
|
|
@import './material-scheme.css';
|
|
|
|
@source '../../../resources/views';
|
|
@source '../../../src';
|