Skip to content

Releases

v2.0.1 Release

v2.0.1 Release Latest
Latest

Choose a tag to compare

View all tags
@dayyanj dayyanj released this 15 Mar 06:39
v2.0.1
7cfa0a9

Changelog

All notable changes to the Spwig Theme SDK will be documented in this file.

v2.0.1 — Audit & Compatibility Release (2026-03-15)

What's New

Cross-Platform Compatibility Fixes
This release resolves 12 bugs discovered during a comprehensive audit against the live platform and update server. Themes built with the SDK now validate cleanly against the platform's ThemePackager with zero errors.

Expanded Documentation

  • CSS Overrides Guide (docs/CSS_OVERRIDES_GUIDE.md) — Step-by-step guide to customizing theme appearance with overrides.css, including component class targeting examples
  • Component Classes Reference (docs/COMPONENT_CLASSES.md) — Complete list of platform component CSS classes available for styling
  • CSS Load Order (docs/CSS_LOAD_ORDER.md) — Explains the token > component > override cascade so developers know where their styles land
  • Design Tokens (docs/DESIGN_TOKENS.md) — Expanded with element tokens, widget tokens, and responsive scaling sections

6 Header Presets
The starter theme now ships with 6 ready-to-use header configurations: classic, boutique, mega, minimal, promotional, and split. Drop any of these into your presets/headers/ directory as a starting point.

Improved spwig init

  • Template tiers renamed to blank, minimal, and full for clarity
  • Generates slug and component_type automatically
  • Creates presets/headers/ and presets/footers/ directory structure
  • Includes a starter overrides.css with annotated examples

Bug Fixes

# Fix Impact
1 Fixed 96 broken header zone variable references (--theme-header-zones-{zone}-*) Tokens referencing main-header, bottom-bar, and mega-menu-bar zones now resolve correctly
2 Fixed border radius variable naming in docs (--theme-radius-* not --theme-border-radius-*) Documentation now matches actual platform CSS output
3 Added missing slug and component_type to starter manifest Starter theme passes platform validation without manual edits
4 Fixed same header zone references in CLI template New themes created with spwig init generate correct token references
5 Rewrote typography validator for flat CSS strings Tokens like "font-size-lg": "1.125rem" validate correctly instead of expecting nested objects
6 Fixed screenshots validator for mixed entry formats Both "screenshot.png" and {"file": "screenshot.png", "title": "Home"} are accepted
7 Added slug, component_type to TypeScript manifest type IDE autocompletion and type-checking cover all required fields
8 Updated spwig init to output slug and component_type Generated manifests are platform-ready out of the box
9 Synced manifest schemas across CLI, validator, and VS Code extension 16 marketplace fields added (niche, style, assets, videos, etc.)
10 Changed bundled component type "utility" to "widget" Matches platform terminology
11 Increased max screenshots from 10 to 12 Matches marketplace listing limits
12 Allowed additionalProperties in manifest schema Future manifest fields won't cause validation failures

Upgrade Notes

  • No breaking changes. Existing themes continue to work as-is.
  • If your tokens.json references header zone variables without zones- in the path (e.g. var(--theme-header-main-header-background)), update them to include zones- (e.g. var(--theme-header-zones-main-header-background)).
  • Add "slug" and "component_type": "theme" to your manifest.json if not already present — these are now expected by the platform packager.

v2.0.0 — Token-First Architecture (2025-02-23)

  • Complete rewrite from component-based to token-focused system
  • Themes now provide visual identity through design tokens; the platform handles all rendering
  • New CLI tooling (spwig init, spwig validate, spwig package)
  • VS Code extension with schema validation and snippets
  • Menu tokens and header/footer zone support
  • Responsive scaling tokens
Assets 2
Loading