Skip to content

Clarify that site global.* files can hold your own opt-in patterns #75

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
minimaldesign merged 2 commits into from
Sep 19, 2026
Merged

Clarify that site global.* files can hold your own opt-in patterns #75

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7b1fb07
Clarify that site global.* files can hold your own opt-in patterns
minimaldesign Sep 19, 2026
ada169c
don't need example there
minimaldesign Sep 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/content/docs/start.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -182,7 +182,7 @@ Your own CSS is unlayered, which means:
Your `site/` CSS is required to be imported in this order:

- `theme.starter.css` overrides the default mCSS theme.
- `global.*.css` for site-wide additions to the framework's globals.
- `global.*.css` for site-wide patterns that are not components: your own opt-in classes and additions to the mCSS globals.
- `component.*.css` for your own components (most of your CSS should end up here)
- `page.*.css` for the rare page-specific styles
- `patch.*.css` for patching CSS you don't control, i.e. plugins
Expand Down
Loading