uniweb 0.2.38 → 0.2.40

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.2.38",
+  "version": "0.2.40",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -37,9 +37,9 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/build": "0.1.19",
-    "@uniweb/runtime": "0.2.11",
+    "@uniweb/build": "0.1.21",
+    "@uniweb/core": "0.1.9",
     "@uniweb/kit": "0.1.5",
-    "@uniweb/core": "0.1.8"
+    "@uniweb/runtime": "0.2.11"
   }
 }

package/partials/adding-pages.hbs

@@ -9,9 +9,11 @@
 
 ### Section Ordering
 
-By default, sections are discovered from `.md` files and sorted by numeric prefix (`1-`, `2-`, `2.5-`).
+By default, sections are discovered from `.md` files and sorted by numeric prefix (`1-`, `2-`, `3-`).
 
-For more control, use the `sections` property in `page.yml`:
+**Decimal prefixes** allow inserting sections without renumbering: `2.5-` sorts between `2-` and `3-`.
+
+For explicit control, use the `sections` property in `page.yml`:
 
 ```yaml
 title: My Page
@@ -21,9 +23,55 @@ sections:
   - pricing
 ```
 
-This approach makes reordering easy (just move lines) and allows temporarily removing sections by commenting them out.
+This makes reordering easy (move lines) and allows commenting out sections temporarily.
 
 **Options:**
-- `sections: *` or omit — auto-discover and sort `.md` files (default)
-- `sections: [hero, features]` — explicit ordering, no numeric prefixes needed
-- `sections: []` or no `.md` files — pure route with no content sections
+- `sections: *` or omit — auto-discover and sort `.md` files by prefix (default)
+- `sections: [hero, features]` — explicit ordering, no prefixes needed
+- `sections: []` — pure route with no content sections
+
+### Section Hierarchy (Subsections)
+
+For parent-child relationships, use the explicit array with nesting:
+
+```yaml
+sections:
+  - hero
+  - features:
+      - logocloud
+      - stats
+  - pricing
+```
+
+This is clearer than prefix notation and easier to restructure.
+
+**Advanced:** Comma prefixes (`1,1-`, `1,2-`) also denote hierarchy, but explicit arrays are recommended for readability.
+
+### Page Ordering and Index Pages
+
+Parent controls which page is the "index" for its route. The index page gets the parent's route.
+
+**In `site.yml`** (for top-level pages):
+```yaml
+name: My Site
+pages: [home, about, features]  # First (home) is homepage at /
+# Or just name the homepage:
+index: home
+```
+
+**In `page.yml`** (for child pages):
+```yaml
+title: Documentation
+pages: [getting-started, installation, config]  # First is index for /docs
+# Or just name the index:
+index: getting-started
+```
+
+**How it works:**
+- `pages: [a, b, c]` — Explicit order, first item gets parent route
+- `index: name` — Just set the index, auto-discover the rest
+- Omit both — Sort by `order` prop, lowest becomes index
+
+**Example:** If `getting-started` is the index for `/docs`:
+- `pages/docs/getting-started/` → route `/docs`
+- `pages/docs/installation/` → route `/docs/installation`

package/partials/claude-md.hbs

@@ -122,11 +122,36 @@ sections:
 ```
 
 **Section ordering:**
-- Default: `.md` files discovered and sorted by numeric prefix (`1-`, `2-`, `2.5-`)
+- Default: `.md` files discovered and sorted by numeric prefix (`1-`, `2-`, `3-`)
+- Decimals to insert: `2.5-` sorts between `2-` and `3-` (no renumbering needed)
 - Explicit: Use `sections: [hero, features]` — no prefixes needed, easy reordering
-- Empty: `sections: []` or no `.md` files — pure route with no content
+- Empty: `sections: []` — pure route with no content
 - Wildcard: `sections: *` — explicitly use default behavior
 
+**Section hierarchy:** For subsections, use explicit nesting in `page.yml`:
+```yaml
+sections:
+  - hero
+  - features:
+      - logocloud
+      - stats
+```
+This is clearer than prefix notation (`1,1-`, `1,2-`) and easier to restructure.
+
+**Page ordering:** Parent controls which page is the index for its route:
+```yaml
+# In site.yml (top-level pages)
+pages: [home, about, docs]  # First is homepage at /
+index: home                  # Or just name the homepage
+
+# In page.yml (child pages)
+pages: [getting-started, installation]  # First is index for this route
+index: getting-started                   # Or just name the index
+```
+- `pages: [a, b, c]` — First gets parent route (becomes index)
+- `index: name` — Just set index, auto-discover rest
+- Omit both — Sort by `order` prop, lowest becomes index
+
 ## Component Development
 
 ### Props Interface