g-comments 0.2.0 → 0.2.1

package/CHANGELOG.md

@@ -6,6 +6,16 @@ All notable changes to `g-comments` are listed here. The format follows
 
 ## [Unreleased]
 
+## [0.2.1] - 2026-10-20
+
+### Changed
+
+- The default stylesheet lives in the `gc-defaults` cascade layer and a forum
+  theme's CSS is imported into `gc-forum`, so site CSS beats the forum's and the
+  forum's beats the defaults regardless of load order or specificity. The forum
+  stylesheet is no longer a `<link>`: it is an `@import … layer(gc-forum)` in
+  the installed `<style>`.
+
 ## [0.2.0] - 2026-10-20
 
 ### Added

package/README.md

@@ -134,9 +134,9 @@ depth, and `Item` keeps the inline reply, edit, report and delete panels.
 (`.gc-root.gc-root--styled`); nothing outside it is touched. Class names follow
 BEM (`gc-comment`, `gc-comment__body`, `gc-composer--replying`,
 `gc-button--primary`, …) and stay in place with `unstyled`, which only drops
-`gc-root--styled`. Selectors carry one class of specificity, so your own class
-rules win when loaded after the stylesheet. Cooked comment HTML is wrapped in
-`.gc-prose`.
+`gc-root--styled`. The rules live in the `gc-defaults` cascade layer, so your
+own (unlayered) CSS wins whatever its order or specificity. Cooked comment HTML
+is wrapped in `.gc-prose`.
 
 `appearance.elements` adds class names: `root`, `header`, `count`, `sort`,
 `signIn`, `composer`, `textarea`, `toolbar`, `list`, `comment`, `avatar`,
@@ -191,14 +191,15 @@ element's shadow root. Three things arrive:
   `--gc-forum-font-monospace` carry the stacks, and `@font-face` rules are
   added to the page for fonts the forum serves.
 - **Theme CSS.** The default theme's "Embedded CSS" (Admin → Customize →
-  Themes → Edit CSS/HTML → Embedded) is loaded as a stylesheet, so forum
-  admins can style the `gc-*` classes without touching the site.
-
-Precedence: tokens you set (`appearance.variables`, or `--gc-*` on the root
-or an ancestor) win over the forum's, which win over the defaults. The forum's
-stylesheet is appended after the page's, so plain CSS rules tie-break in the
-forum's favour; out-specify them (`.blog .gc-comment`) where the site must
-win. `useForumTheme()` returns the same data for sites that style their own
+  Themes → Edit CSS/HTML → Embedded) is imported into the `gc-forum` cascade
+  layer, so forum admins can style the `gc-*` classes without touching the
+  site.
+
+Precedence, for tokens and for plain CSS alike: what a component sets
+(`appearance`) beats the site's own CSS and `--gc-*` values, which beat the
+forum's, which beat the defaults. Site CSS is unlayered and the forum's sits in
+`gc-forum` above `gc-defaults`, so no ordering or specificity tricks are
+needed. `useForumTheme()` returns the same data for sites that style their own
 UI after the forum.
 
 ## Custom elements (no framework)