Andreas Reinhold / reiniandClaude Opus 5
d7653aa6d0
Plan step 36. A component rewritten without Tailwind keeps its padding,
margins and borders in material.components, and Tailwind's preflight
(* { padding: 0; margin: 0; border: 0 solid }) in its base layer, named
after material, undid every one of them. The Workbench now names theme and
base before importing the foundation, so the preflight — the same reset
foundation/reset.css carries — sits below the package, while Tailwind's
components and utilities stay above it and a caller's utility still wins.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9
21 lines
1.0 KiB
CSS
21 lines
1.0 KiB
CSS
/* The Workbench builds the package as an application would, with explicit sources so the plans
|
|
in docs/ are not scanned for class names.
|
|
|
|
Tailwind's theme and base layers are named first, then the foundation's `material` layers, then
|
|
Tailwind's components and utilities: a caller's utility still outranks every package rule, and
|
|
Tailwind's preflight sits below the package. Its preflight is the reset the foundation already
|
|
carries rule for rule (foundation/reset.css), and above `material` its `* { padding: 0 }` would
|
|
undo the padding and margins of every component rewritten without Tailwind. tailwind.css brings
|
|
the components still written for Tailwind, without declaring the tokens a second time. */
|
|
@layer theme, base;
|
|
|
|
@import '../../../resources/css/foundation.css';
|
|
@import '../../../resources/css/layout.css';
|
|
@import '../../../resources/css/components.css';
|
|
@import 'tailwindcss' source(none);
|
|
@import '../../../resources/css/tailwind.css';
|
|
@import './material-scheme.css';
|
|
|
|
@source '../../../resources/views';
|
|
@source '../../../src';
|