Andreas Reinhold / reiniandClaude Sonnet 5
a967cfcc2b
Plan step 37: an application on 1.x-style imports now imports foundation.css before @import 'tailwindcss' and tailwind.css after it, the way foundation.css's own header has described since Phase F started — material.css only ever saved writing those two lines. Updates every place that named it: tailwind.css's and foundation/hidden.css's and tokens/utilities.css's header comments, the development skill's install snippet and Tokens section, README.md's install snippet, and a new line in UPGRADE.md's migration notes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9
21 lines
1.0 KiB
CSS
21 lines
1.0 KiB
CSS
/*
|
|
* Livewire Material's Tailwind half: the theme that turns the tokens into utilities and the token
|
|
* utilities themselves (`state-layer`, `focus-ring`, `touch-target`, `link`, `type-*`), for a view
|
|
* that still writes Tailwind classes — the showcase until step 38, and an application's own views
|
|
* until it drops Tailwind. Every component stylesheet is plain CSS (plan step 36) and needs
|
|
* nothing from here. This file goes when the last Tailwind class leaves (step 39).
|
|
*
|
|
* It carries no tokens, so it can sit behind the foundation without declaring them twice — the
|
|
* Workbench imports it that way, after Tailwind:
|
|
*
|
|
* @import '../../../resources/css/foundation.css';
|
|
* @import 'tailwindcss' source(none);
|
|
* @import '../../../resources/css/tailwind.css';
|
|
*
|
|
* An application still building Tailwind imports the same way, `foundation.css` then `tailwindcss`
|
|
* then this file, in place of the 1.x `material.css` shortcut, which is gone.
|
|
*/
|
|
|
|
@import './tokens/theme.css';
|
|
@import './tokens/utilities.css';
|