uniweb 0.8.40 → 0.8.42

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.8.40",
+  "version": "0.8.42",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,14 +41,14 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/core": "0.5.20",
-    "@uniweb/runtime": "0.6.35",
-    "@uniweb/kit": "0.7.23"
+    "@uniweb/core": "0.5.22",
+    "@uniweb/kit": "0.7.24",
+    "@uniweb/runtime": "0.6.38"
   },
   "peerDependencies": {
+    "@uniweb/build": "0.8.41",
     "@uniweb/content-reader": "1.1.4",
-    "@uniweb/semantic-parser": "1.1.9",
-    "@uniweb/build": "0.8.39"
+    "@uniweb/semantic-parser": "1.1.9"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -1150,26 +1150,26 @@ This is the system-building pattern at its clearest: **section types are the pub
 
 ### Section components are composites
 
-A section component is rarely a single flat render. It imports helper components from `src/components/` to build a complex UI while presenting a single `type:` to the content author. The `src/components/` directory is the developer's workbench — ordinary React components with ordinary props, not selectable by authors, not auto-discovered.
+A section component is rarely a single flat render. It imports helper components from `src/components/` and utilities from `src/utils/` to build a complex UI while presenting a single `type:` to the content author. These directories are the developer's workbench — ordinary React and JS, not selectable by authors, not auto-discovered.
 
 ```jsx
-// src/sections/Lesson/index.jsx
-import LessonHeader from '../../components/LessonHeader'
-import LessonContent from '../../components/LessonContent'
-import LessonNav from '../../components/LessonNav'
+// src/sections/Pricing/index.jsx
+import PricingCard from '#components/PricingCard'
+import formatPrice from '#utils/formatPrice'
 
-export default function Lesson({ content, params, block }) {
+export default function Pricing({ content, params }) {
+  const currency = params.currency || 'USD'
   return (
-    <>
-      <LessonHeader block={block} />
-      <LessonContent content={content} params={params} />
-      <LessonNav block={block} />
-    </>
+    <div className="grid grid-cols-1 md:grid-cols-3 gap-8 max-w-6xl mx-auto">
+      {content.items.map((tier, i) => (
+        <PricingCard key={i} tier={tier} price={formatPrice(tier.data, currency)} />
+      ))}
+    </div>
   )
 }
 ```
 
-The content author writes `type: Lesson` in one markdown file. The section component handles the structural chrome — a header derived from the page hierarchy, the rendered content, a prev/next footer. The three helpers live in `src/components/` and receive whatever props make sense for their job.
+The content author writes `type: Pricing` and defines tiers as content items. The section component maps items to cards using a helper component from `src/components/` and a formatting utility from `src/utils/`. Neither is selectable by authors — they're implementation details behind the section type boundary.
 
 **When to reach for this pattern:** When a page type has consistent structural elements (header bars, navigation footers, contextual sidebars) that the content author shouldn't need to add as separate sections. If the author would have to add the same boilerplate sections to every page of a certain type, the section component should compose them internally.
 
@@ -1188,26 +1188,38 @@ foundation/src/
 │       └── Diagram/
 │           ├── index.jsx
 │           └── meta.js
+├── layouts/             # Custom layouts (optional, auto-discovered)
+│   └── DocsLayout/
+│       ├── index.jsx
+│       └── meta.js
 ├── components/          # Your React components (no meta.js, not selectable)
 │   ├── ui/
 │   │   └── button.jsx
 │   └── Card.jsx
+├── utils/               # Helper functions, non-React logic
+│   └── splitContent.js
 └── styles.css
 ```
 
 **Discovery:** PascalCase files/folders at root of `sections/` are auto-discovered. Nested levels require `meta.js`. Lowercase directories are organizational only. `hidden: true` excludes a component entirely. Everything outside `sections/` is ordinary React.
 
-**`#components` alias:** Foundations include a `#components/*` subpath import in `package.json` that maps to `src/components/`. Use it in section types instead of brittle relative paths:
+**Import aliases:** Foundations include subpath imports in `package.json` that map to `src/` subdirectories. Use them instead of brittle relative paths:
+
+| Alias | Maps to | Use for |
+|-------|---------|---------|
+| `#components/*` | `./src/components/*` | Shared React components |
+| `#utils/*` | `./src/utils/*` | Helper functions, non-React logic |
 
 ```jsx
-// ✅ Clean — use the alias
+// ✅ Clean — use aliases
 import LessonHeader from '#components/LessonHeader'
+import splitContent from '#utils/splitContent'
 
 // ❌ Fragile — breaks if you reorganize sections/
 import LessonHeader from '../../components/LessonHeader'
 ```
 
-Within `src/components/` itself, use normal relative imports (`./AIFeedbackCard`) since files are siblings.
+Within the same directory (e.g., one component importing a sibling), use normal relative imports (`./AIFeedbackCard`).
 
 ### Website and Page APIs
 

package/templates/foundation/package.json.hbs

@@ -11,7 +11,8 @@
     "./dist/styles": "./dist/assets/style.css"
   },
   "imports": {
-    "#components/*": "./src/components/*"
+    "#components/*": "./src/components/*",
+    "#utils/*": "./src/utils/*"
   },
   "files": ["dist", "src"],
   "scripts": {