From f055fc7b94ed6d51402f247616af7fe755087fc3 Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 5 Jul 2026 09:15:42 +0000 Subject: [PATCH 1/2] docs(roadmap): record permanently-excluded, never-planned items Add 4 deliberate architectural exclusions under Out of scope, mirroring the framework stance, so they are not re-proposed or picked up by accident: a SCSS/preprocessor authoring field, prefix-based auto component styling, viewport-breakpoint utility/mixin generation, and full utility-class library generation. Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_01AR8LFdZpCqJj3AaYWM4hB4 --- docs/roadmap.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/docs/roadmap.md b/docs/roadmap.md index cdf29732..79d2147f 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -30,6 +30,25 @@ Bricks Builder and Gutenberg integrations. Framework-level items live in the - Per-page CSS bundle override — covered by the `slashed_bricks/css_bundle_url` filter. +The following are **permanently excluded** — deliberate architectural decisions +that mirror the framework's stance, not backlog. They should not be re-proposed +or picked up by accident: + +- **A SCSS / preprocessor authoring field** — the plugin will not ship a "custom + SCSS" input with mixins or functions. The framework is pure CSS with no compile + step; configuration is done through token overrides plus a plain custom-CSS field, + and native CSS features are the substitute. +- **Prefix-based automatic component styling** — the plugin will not auto-style + arbitrary classes by name pattern. Components are explicit BEM classes (`.sf-*`) + surfaced as builder presets; there is deliberately no "style anything matching this + prefix" mechanism. +- **Viewport-breakpoint utility / mixin generation** — layout adapts through container + queries and breakpoint-free techniques. Emitting a media-query breakpoint utility or + mixin system is out of scope. +- **Generating a full utility-class library** — the plugin stays token- and + primitive-first. Small, opt-in, token-backed helpers may be surfaced on demand, but + emitting a broad utility-class surface is out of scope. + --- ## Shipped (no longer tracked here) From 7c6751d1342f8a7316fa78036ecfa397cb0f4255 Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 5 Jul 2026 11:05:39 +0000 Subject: [PATCH 2/2] docs(roadmap): clarify .sf-* is the reserved framework namespace, not generic BEM Address review feedback: reword the prefix-based-styling exclusion so it no longer implies .sf-* is a user-facing generic BEM namespace; .sf-* is the reserved SLASHED framework class namespace (authored BEM-style), surfaced as builder presets. Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_01AR8LFdZpCqJj3AaYWM4hB4 --- docs/roadmap.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/roadmap.md b/docs/roadmap.md index 79d2147f..d2cbbf43 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -39,9 +39,9 @@ or picked up by accident: step; configuration is done through token overrides plus a plain custom-CSS field, and native CSS features are the substitute. - **Prefix-based automatic component styling** — the plugin will not auto-style - arbitrary classes by name pattern. Components are explicit BEM classes (`.sf-*`) - surfaced as builder presets; there is deliberately no "style anything matching this - prefix" mechanism. + arbitrary classes by name pattern. Components are surfaced as builder presets that + apply explicit, named framework classes (the reserved `.sf-*` namespace, authored + BEM-style); there is deliberately no "style anything matching this prefix" mechanism. - **Viewport-breakpoint utility / mixin generation** — layout adapts through container queries and breakpoint-free techniques. Emitting a media-query breakpoint utility or mixin system is out of scope.