An application lists named schemes in livewire-material.profiles, and material:scheme without a seed generates them all into one stylesheet: the default profile as the plain blocks, every profile under <html data-scheme>, with descendant selectors so a nested data-theme panel keeps the page's profile. The JSON keeps the 1.0 top level. Scheme::resolveProfileUsing() lets the application name the active profile; it is asked on every use and falls back to the default for an unknown name or a resolver that throws. The head script writes it before the first paint and keeps it through wire:navigate, and the mail theme and the error pages' fallback draw it. <x-scheme-picker> chooses one and previews it through $store.theme.previewScheme(); the showcase previews the Workbench's profiles. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V9NnLxnPp8vaaurb3Z1MFy
9 lines
329 B
CSS
9 lines
329 B
CSS
/* The Workbench builds the package exactly as an application would, with explicit
|
|
sources so the plans in docs/ are not scanned for class names. */
|
|
@import 'tailwindcss' source(none);
|
|
@import '../../../resources/css/material.css';
|
|
@import './material-scheme.css';
|
|
|
|
@source '../../../resources/views';
|
|
@source '../../../src';
|