uniweb 0.8.11 → 0.8.13

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.8.11",
+  "version": "0.8.13",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,11 +41,11 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/build": "0.8.10",
+    "@uniweb/build": "0.8.12",
     "@uniweb/content-reader": "1.1.4",
-    "@uniweb/core": "0.5.7",
-    "@uniweb/runtime": "0.6.7",
-    "@uniweb/kit": "0.7.7",
-    "@uniweb/semantic-parser": "1.1.5"
+    "@uniweb/core": "0.5.9",
+    "@uniweb/kit": "0.7.9",
+    "@uniweb/runtime": "0.6.9",
+    "@uniweb/semantic-parser": "1.1.6"
   }
 }

package/partials/agents.md

@@ -172,7 +172,6 @@ content = {
   title: '',        // Main heading (string or string[] for multi-line)
   pretitle: '',     // Heading before main title (auto-detected)
   subtitle: '',     // Heading after title (string or string[] for multi-line)
-  subtitle2: '',    // Third-level heading
   paragraphs: [],   // Text blocks
   links: [],        // { href, label, role } — standalone links become buttons
   images: [],       // { src, alt, role, href }
@@ -183,7 +182,7 @@ content = {
   quotes: [],       // Blockquotes
   snippets: [],     // Fenced code — [{ language, code }]
   data: {},         // From tagged data blocks (```yaml:tagname, ```json:tagname)
-  headings: [],     // Overflow headings after subtitle2
+  headings: [],     // Headings after subtitle, in document order
   items: [],        // Each has the same flat structure — from headings after body content
   sequence: [],     // All elements in document order
 }
@@ -431,6 +430,13 @@ Does the content author write content *inside* the nested element? **Yes** → c
 
 Inset components declare `inset: true` in meta.js. Don't use `hidden: true` on insets — `hidden` means "don't export this component at all" (for internal helpers), while `inset: true` means "available for `@Component` references in markdown."
 
+**What inset components receive:** Insets are full section types — they get `{ content, params, block }` like any other section. The alt text becomes `content.title`, and attributes become `params`:
+
+```markdown
+![npm create uniweb](@CommandBlock){note="Ready to go"}
+```
+→ CommandBlock receives `content.title = "npm create uniweb"` and `params.note = "Ready to go"`.
+
 **SSG:** Insets, `<ChildBlocks>`, and `<Visual>` all render correctly during prerender. Inset components that use React hooks internally (useState, useEffect) will trigger prerender warnings — this is expected and harmless; the page renders correctly client-side.
 
 ### Section Nesting Details
@@ -475,14 +481,12 @@ export default function Grid({ block, params }) {
 
 Set `background` in frontmatter — the runtime renders it automatically:
 
-> **FIXME:** var(--primary-900) should be primary-900, right?
-
 ```yaml
 background: /images/hero.jpg                             # Image
 background: /videos/hero.mp4                             # Video
 background: linear-gradient(135deg, #667eea, #764ba2)    # Gradient
 background: '#1a1a2e'                                    # Color (hex — quote in YAML)
-background: var(--primary-900)                            # CSS variable
+background: primary-900                                   # Palette token (bare name or var())
 ```
 
 Object form for more control:
@@ -603,21 +607,27 @@ Components use **semantic CSS tokens** instead of hardcoded colors. The runtime
 <h2 className="text-heading">...</h2>
 ```
 
-**Core tokens** (available as Tailwind classes):
+**Semantic tokens** (available as Tailwind classes — `text-*`, `bg-*`, `border-*`):
 
 | Token | Purpose |
 |-------|---------|
-| `text-heading` | Headings |
-| `text-body` | Body text |
-| `text-subtle` | Secondary/de-emphasized text |
-| `bg-section` | Section background |
-| `bg-card` | Card/panel background |
-| `bg-muted` | Hover states, zebra rows |
-| `border-border` | Borders |
-| `text-link` | Link color |
-| `bg-primary` / `text-primary-foreground` / `hover:bg-primary-hover` | Primary actions |
-| `bg-secondary` / `text-secondary-foreground` / `hover:bg-secondary-hover` | Secondary actions |
-| `text-success` / `text-error` / `text-warning` / `text-info` | Status colors |
+| `heading` | Heading text |
+| `body` | Body text |
+| `subtle` | Secondary/de-emphasized text |
+| `section` | Section background |
+| `card` | Card/panel/well background |
+| `muted` | Hover states, zebra rows |
+| `border` | Lines, dividers |
+| `ring` | Focus indicators |
+| `link` / `link-hover` | Link colors |
+| `primary` / `primary-foreground` / `primary-hover` / `primary-border` | Primary actions |
+| `secondary` / `secondary-foreground` / `secondary-hover` / `secondary-border` | Secondary actions |
+| `success` / `warning` / `error` / `info` | Status colors |
+| `success-subtle` / `warning-subtle` / `error-subtle` / `info-subtle` | Status backgrounds (alerts) |
+
+Use with any Tailwind prefix: `text-heading`, `bg-section`, `border-border`, `bg-primary`, `text-primary-foreground`, `hover:bg-primary-hover`, `bg-error-subtle`, etc.
+
+**Palette shades** are also available: `text-primary-600`, `bg-neutral-100`, `border-accent-300` — 11 shades (50–950) for each palette color (primary, secondary, accent, neutral). See `theme-tokens.css` for the complete mapping.
 
 **Content authors control context** in frontmatter:
 
@@ -789,14 +799,16 @@ Content fields are **HTML strings** — they contain `<strong>`, `<em>`, `<a>` f
 **Extracted fields** (most common — custom layout with content from markdown):
 
 ```jsx
-import { H1, H2, P, Span } from '@uniweb/kit'
+import { H1, H2, H3, P, Span } from '@uniweb/kit'
 
 <H1 text={content.title} className="text-heading text-5xl font-bold" />
+<H2 text={content.subtitle} className="text-heading text-2xl" />
+<H3 text={item.title} className="text-heading text-lg font-semibold" />
 <P text={content.paragraphs} className="text-body" />
 <Span text={listItem.paragraphs[0]} className="text-subtle" />
 ```
 
-These render their own HTML tag — don't wrap: `<H2 text={...} />` not `<h2><H2 text={...} /></h2>`.
+Kit provides `H1` through `H6` — use the appropriate level for semantic hierarchy. These render their own HTML tag — don't wrap: `<H2 text={...} />` not `<h2><H2 text={...} /></h2>`.
 
 **Full content rendering** (article/docs sections where the author controls the flow):
 
@@ -825,18 +837,46 @@ import { Visual } from '@uniweb/kit'
 
 **Navigation and routing:** `Link` (`to`/`href`, `to="page:about"` for page ID resolution, auto `target="_blank"` for external, `reload` for full page reload), `useActiveRoute()`, `useWebsite()`, `useRouting()`
 
-**Header and layout:** `useScrolled(threshold)`, `useMobileMenu()`, `useAppearance()` (light/dark mode)
+**Header and layout:** `useScrolled(threshold)`, `useMobileMenu()`, `useAppearance()`
 
 **Layout helpers:** `useGridLayout(columns, { gap })`, `useAccordion({ multiple, defaultOpen })`, `useTheme(name)`
 
 **Data and theming:** `useThemeData()` (programmatic color access), `useColorContext(block)`
 
-**Utilities:** `cn()` (Tailwind class merge), `Link`, `Image`, `Asset`, `SafeHtml`, `SocialIcon`, `filterSocialLinks(links)`, `getSocialPlatform(url)`
+**Utilities:** `cn()` (Tailwind class merge — `cn('px-4', condition && 'bg-primary')` resolves conflicts), `Link`, `Image`, `Asset`, `SafeHtml`, `SocialIcon`, `filterSocialLinks(links)`, `getSocialPlatform(url)`
 
 **Other styled:** `SidebarLayout`, `Prose`, `Article`, `Code`, `Alert`, `Table`, `Details`, `Divider`, `Disclaimer`
 
+### Hook Signatures
+
+```js
+useActiveRoute()    → { route, rootSegment, isActive(pageOrRoute), isActiveOrAncestor(pageOrRoute) }
+useMobileMenu()     → { isOpen, open, close, toggle }  // auto-closes on route change
+useScrolled(threshold?) → boolean                       // true when scrolled past threshold (px)
+useAppearance()     → { scheme, setScheme, toggle, canToggle, schemes }
+useWebsite()        → { website }                       // the Website object
+useThemeData()      → Theme                             // programmatic color access
+useColorContext(block) → 'light' | 'medium' | 'dark'   // current section context
+```
+
+`isActive` and `isActiveOrAncestor` accept a Page object or a route string. `useAppearance` reads `appearance:` from `theme.yml` — `scheme` is `'light'`|`'dark'`, `canToggle` reflects `allowToggle` config. Stores preference in localStorage, respects system preference.
+
+### Icon Component
+
+The `<Icon>` renders icons from content or explicit props. The simplest usage — spread an icon object from content:
+
+```jsx
+{content.icons.map((icon, i) => <Icon key={i} {...icon} />)}
+```
+
+Props: `library` + `name` (from content), `svg` (direct SVG string), `url` (fetch from URL), `size` (default `'24'`), `className`. The legacy `icon` prop accepts shorthand strings (`"lu-house"`) or objects.
+
+Built-in icons (no library needed): `check`, `close`, `menu`, `chevronDown`, `chevronRight`, `externalLink`, `download`, `play`, and a few others.
+
 ### Content Patterns for Header and Footer
 
+Layout sections (`header.md`, `footer.md`) are regular section types — they support the full content shape including tagged data blocks, lists, links, icons, and items. The only difference is they render on every page instead of one.
+
 Header and Footer combine several content categories. Use different parts of the content shape for each role:
 
 **Header** — title for logo, list for nav, standalone link for CTA:

package/src/commands/inspect.js

@@ -174,7 +174,6 @@ function guaranteeContentStructure(parsedContent) {
     title: content.title || '',
     pretitle: content.pretitle || '',
     subtitle: content.subtitle || '',
-    subtitle2: content.subtitle2 || '',
     alignment: content.alignment || null,
     paragraphs: content.paragraphs || [],
     links: content.links || [],