@soloworks/smking-next 0.12.2 → 0.14.0

package/CHANGELOG.md

@@ -1,5 +1,45 @@
 # @soloworks/smking-next
 
+## 0.14.0 — 2026-05-23
+
+**Single-source CSS distribution + theme mode toggle.** `<SmkingCms>` now ships its own polished default styles by default — no customer CSS work needed. Customers who already use Tailwind + `@tailwindcss/typography` can flip to a prose-utility markup variant via the `mode` prop or `SMKING_CMS_THEME` env var.
+
+### Added
+
+- **Mode A (`css`, default)** — `<SmkingCms>` emits a `<style data-smking="cms-styles">` block once per render carrying the canonical SDK stylesheet. Class hooks `.smk-cms` / `.smk-block--*` / `.smk-hero` / `.smk-nav` / `.smk-carousel`. Customer themes via CSS variables on `:root` (`--smk-accent`, `--smk-font-serif`, etc).
+- **Mode B (`tailwind-prose`)** — opt-in via `<SmkingCms mode="tailwind-prose" ... />` or `SMKING_CMS_THEME=tailwind-prose` env var. Wraps the article in `<article class="prose dark:prose-invert">` and emits Tailwind utility classes on every block (`not-prose` resets around hero/nav/carousel/search). Requires the customer's `@tailwindcss/typography` plugin and a tailwind safelist (the `@soloworks/smking-wizard` 0.4+ installs both automatically).
+- **`CmsThemeMode` type export** — discriminated string literal `'css' | 'tailwind-prose'` for typed prop usage.
+- **`SMKING_CMS_STYLES` constant** at `@soloworks/smking-next/lib/smking-cms-styles` — auto-generated from `packages/shared/src/styles/cms-styles.css` via the monorepo `pnpm sync:cms-styles` script. Customers who want to ship the SDK stylesheet as a standalone CSS file (CDN / static asset) can copy this constant verbatim.
+
+### Changed
+
+- `SmkingCms` props now accept `mode?: CmsThemeMode` alongside the existing `CmsParams`. No breaking change — omitted prop defaults to `'css'` (legacy behavior plus the new inline style block).
+
+### Pairs with
+
+- `smking/laravel` v0.15.0 — identical theme-mode toggle on the Laravel side. Both SDKs ship byte-identical canonical CSS in Mode A; Mode B markup also mirrors across both runtimes.
+- `@soloworks/smking-wizard` v0.4.0 — install-time Tailwind detect + theme-mode-select TUI step. When Tailwind is detected the wizard offers Mode B and installs `@tailwindcss/typography` + safelist patches automatically.
+
+## 0.13.0 — 2026-05-22
+
+**Dynamic CMS blocks — `nav-recent-posts`, `nav-taxonomy-list`, `nav-search` now render with real publish-time data.**
+
+Customer pages that include any nav-* block on the smking dashboard editor now receive the resolved snapshot baked into `block.props.snapshot` (or `block.props.index` for search). The SDK echoes it directly — zero round-trips back to smking at request time. If smking is down, the customer's page still renders the last published snapshot.
+
+### Added
+
+- **Server-side render of `nav-recent-posts` / `nav-taxonomy-list`** — `<SmkingCms>` now emits a real `<ul>` of cards (slug-linked title + excerpt + featured image + published date) instead of the prior `smk-nav-pending` placeholder. The wrapper carries `data-layout="list|grid|carousel"` so customer CSS can theme each variant.
+- **Server-side render of `nav-search`** — emits an `<input type="search">` plus a results `<ul>`, wired by an inline IIFE that does case-insensitive substring filter against the publish-time index (top 20 matches). Zero React client-component dependency on the customer side; the IIFE is `</`-escaped against `</script>` smuggling.
+- **`NavSnapshotEntry` + `NavSearchIndexEntry` types** added to the package's public type surface. Each nav block's `props` now exposes `snapshot?` (list/taxonomy) or `index?` (search) so customer code that introspects blocks gets full TS support.
+
+### Why this is a minor (0.13.0) not a patch
+
+Customer pages that previously rendered the empty `smk-nav-pending` placeholder will now show real content. If a customer's stylesheet relied on the placeholder being invisible / empty, this is a visible behavioural change — bumped to minor per semver hygiene. No API surface removals.
+
+### Pairs with
+
+- smking SaaS atomic publish — `publish-handler.ts` now resolves nav-* snapshots via `materializeBlocks` and cascade-refreshes sibling pages so a freshly published article appears in every other page's `nav-recent-posts` feed within the same webhook tick.
+
 ## 0.12.2 — 2026-05-21
 
 **Fix: `doctor` now auto-loads `.env.local` + `.env` matching Next.js convention.**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@soloworks/smking-next",
-  "version": "0.12.2",
+  "version": "0.14.0",
   "description": "AI-native SEO (AEO) for Next.js — auto-inject JSON-LD, FAQ, AI summary, and SEO metadata so AI crawlers (ChatGPT, Perplexity, Google AI) can cite your pages.",
   "license": "MIT",
   "homepage": "https://github.com/sillyleo/smking/tree/main/packages/smking-next",