@uniweb/theming 0.1.12 → 0.1.14

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/theming",
-  "version": "0.1.12",
+  "version": "0.1.14",
   "description": "Theming utilities for the Uniweb platform — shade generation, CSS generation, theme processing",
   "type": "module",
   "exports": {

package/src/css-generator.js

@@ -597,10 +597,21 @@ export function generateThemeCSS(config = {}, options = {}) {
     sections.push(generateDarkSchemeCSS(appearance, contexts.dark, colorVars))
   }
 
-  // 7. Site background (if specified in theme.yml)
-  if (config.background) {
-    sections.push(`/* Site Background */\nbody {\n  background: ${config.background};\n}`)
-  }
+  // 7. Site background — the page behind the sections.
+  //
+  // Sections paint themselves (rule 3), and on a page whose sections run the
+  // full width that covers the viewport. It does not cover a layout with
+  // columns: a sidebar shell paints its rails and its article and leaves the
+  // space between them unpainted, which falls through to the browser's white —
+  // in both schemes, so dark mode shows a white page around dark panels.
+  //
+  // Defaulting to var(--section) means the page matches the sections sitting on
+  // it and flips with the visitor's choice, because that token already does. A
+  // site wanting a different canvas — a wash behind cards, an image — sets
+  // `background:` in theme.yml and replaces this.
+  sections.push(
+    `/* Site Background */\nbody {\n  background: ${config.background || 'var(--section)'};\n}`
+  )
 
   // 8. Inline text styles (if specified in theme.yml)
   if (config.inline && typeof config.inline === 'object') {

package/src/processor.js

@@ -115,36 +115,6 @@ function normalizeApplyTo(applyTo) {
   return cleaned.length ? cleaned : null
 }
 
-/**
- * Default code block theme configuration
- * Uses Shiki CSS variable names for compatibility
- * These values are NOT converted to CSS here - the kit's Code component
- * injects them at runtime only when code blocks are used (tree-shaking)
- */
-const DEFAULT_CODE_THEME = {
-  // Background and foreground
-  background: '#1e1e2e',      // Dark editor background
-  foreground: '#cdd6f4',      // Default text color
-
-  // Syntax highlighting colors (Shiki token variables)
-  keyword: '#cba6f7',         // Purple - keywords (if, else, function)
-  string: '#a6e3a1',          // Green - strings
-  number: '#fab387',          // Orange - numbers
-  comment: '#6c7086',         // Gray - comments
-  function: '#89b4fa',        // Blue - function names
-  variable: '#f5e0dc',        // Light pink - variables
-  operator: '#89dceb',        // Cyan - operators
-  punctuation: '#9399b2',     // Gray - punctuation
-  type: '#f9e2af',            // Yellow - types
-  constant: '#f38ba8',        // Red - constants
-  property: '#94e2d5',        // Teal - properties
-  tag: '#89b4fa',             // Blue - HTML/JSX tags
-  attribute: '#f9e2af',       // Yellow - attributes
-
-  // UI elements
-  lineNumber: '#6c7086',      // Line number color
-  selection: '#45475a',       // Selection background
-}
 
 /**
  * Validate color configuration
@@ -693,10 +663,14 @@ export function processTheme(rawConfig = {}, options = {}) {
   // Process code block theme
   // These values are stored for runtime injection by kit's Code component
   // (not converted to CSS here - enables tree-shaking when code blocks aren't used)
-  const code = {
-    ...DEFAULT_CODE_THEME,
-    ...(rawConfig.code || {}),
-  }
+  // Passed through exactly as declared — no defaults filled in.
+  //
+  // A default palette here would defeat the point of the setting downstream: a
+  // site naming a bundled theme and overriding one colour would arrive carrying
+  // fifteen, and the theme it named would be overridden in full by values it
+  // never asked for. Whoever renders code owns the default; this only carries
+  // what the site said.
+  const code = rawConfig.code ?? null
 
   // Site background (pass through as CSS value)
   const background = rawConfig.background || null