/* The package's CSS for the Workbench, built the way an application without Tailwind builds it:
   all.css (the foundation, every layout and every component stylesheet) and the Workbench's
   scheme, in an entry Tailwind never touches. Vite's own CSS pipeline inlines the imports here and
   keeps a stylesheet several components import once, at its first position — the order an
   application gets. `@tailwindcss/vite` inlines the imports of an entry that uses Tailwind without
   that deduplication, so all.css imported beside `tailwindcss` would repeat every shared rule later
   in the cascade; app.css keeps Tailwind, for the showcase's classes, apart.

   Both entries open with the same layer statement, so the order holds whichever the page links
   first: the `material` layers above Tailwind's preflight (`base`), whose `* { padding: 0 }` would
   otherwise beat a component's padding, and below its `components` and `utilities`. `properties`
   is the layer Tailwind hoists to the top of its output (the `--tw-*` fallbacks for a browser
   without `@property`); named first, it stays lowest, as it was when both shared one entry. */
@layer properties, theme, base, material, components, utilities;
@import '../../../resources/css/all.css';
@import './material-scheme.css';