uniweb 0.6.20 → 0.6.21

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.6.20",
+  "version": "0.6.21",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -40,9 +40,9 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
+    "@uniweb/build": "0.6.18",
     "@uniweb/core": "0.4.7",
     "@uniweb/kit": "0.5.10",
-    "@uniweb/build": "0.6.17",
     "@uniweb/runtime": "0.5.21"
   }
 }

package/partials/agents-md.hbs

@@ -167,16 +167,19 @@ Decimals insert between: `2.5-testimonials.md` goes between `2-` and `3-`.
 ```yaml
 title: About Us
 description: Learn about our company
-order: 2                    # Navigation sort order
+order: 2                    # Navigation sort position
+pages: [team, history, ...] # Child page order (... = rest). Without ... = strict (hides unlisted)
 index: getting-started      # Which child page is the index
 ```
 
 **site.yml:**
 ```yaml
-index: home                 # Which page folder is the homepage
+index: home                         # Just set the homepage
+pages: [home, about, ...]           # Order pages (... = rest, first = homepage)
+pages: [home, about]                # Strict: only listed pages in nav
 ```
 
-Use `index:` rather than `pages: [...]` — listing pages explicitly hides auto-discovered ones.
+Use `pages:` with `...` for ordering, without `...` for strict visibility control. Use `index:` for simple homepage selection.
 
 ## Semantic Theming
 

package/src/commands/i18n.js

@@ -237,24 +237,20 @@ async function runExtract(siteRoot, config, args) {
   if (!collectionsOnly) {
     log(`\n${colors.cyan}Extracting translatable content${dryRun ? ' (dry run)' : ''}...${colors.reset}\n`)
 
-    // Check if site has been built
-    const siteContentPath = join(siteRoot, 'dist', 'site-content.json')
-    if (!existsSync(siteContentPath)) {
-      error('Site content not found. Run "uniweb build" first.')
-      process.exit(1)
-    }
-
     try {
-      // Dynamic import to avoid loading at CLI startup
+      // Collect site content directly from source files (no build required)
+      const { collectSiteContent } = await import('@uniweb/build/site')
       const { extractManifest, formatSyncReport } = await import('@uniweb/build/i18n')
 
+      log(`${colors.dim}Collecting site content...${colors.reset}`)
+      const siteContent = await collectSiteContent(siteRoot)
+
       // Check if this is a first-time extract (no previous manifest)
       const manifestPath = join(siteRoot, config.localesDir, 'manifest.json')
       const isUpdate = existsSync(manifestPath)
 
-      const { manifest, report } = await extractManifest(siteRoot, {
+      const { manifest, report } = await extractManifest(siteRoot, siteContent, {
         localesDir: config.localesDir,
-        siteContentPath,
         verbose,
         dryRun,
       })
@@ -1466,11 +1462,10 @@ ${colors.bright}Configuration:${colors.reset}
   By default, all *.json files in locales/ are treated as translation targets.
 
 ${colors.bright}Workflow:${colors.reset}
-  1. Build your site:           uniweb build
-  2. Extract strings:           uniweb i18n extract
-  3. Generate locale files:     uniweb i18n generate es fr
-  4. Translate locale files:    Edit locales/es.json, locales/fr.json, etc.
-  5. Build with translations:   uniweb build (generates locale-specific output)
+  1. Extract strings:           uniweb i18n extract
+  2. Generate locale files:     uniweb i18n generate es fr
+  3. Translate locale files:    Edit locales/es.json, locales/fr.json, etc.
+  4. Build with translations:   uniweb build (generates locale-specific output)
 
 ${colors.bright}File Structure:${colors.reset}
   locales/