@uniweb/build 0.14.20 → 0.14.22

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "0.14.20",
+  "version": "0.14.22",
   "description": "Build tooling for the Uniweb Component Web Platform",
   "type": "module",
   "exports": {
@@ -59,13 +59,13 @@
     "js-yaml": "^4.1.0",
     "sharp": "^0.33.2",
     "yaml": "^2.5.0",
-    "@uniweb/content-writer": "0.2.6",
-    "@uniweb/theming": "0.1.4"
+    "@uniweb/theming": "0.1.4",
+    "@uniweb/content-writer": "0.2.6"
   },
   "optionalDependencies": {
     "@uniweb/content-reader": "1.1.12",
-    "@uniweb/runtime": "0.8.20",
-    "@uniweb/schemas": "0.2.4"
+    "@uniweb/schemas": "0.2.4",
+    "@uniweb/runtime": "0.8.21"
   },
   "peerDependencies": {
     "vite": "^5.0.0 || ^6.0.0 || ^7.0.0",
@@ -74,7 +74,7 @@
     "@tailwindcss/vite": "^4.0.0",
     "@vitejs/plugin-react": "^4.0.0 || ^5.0.0",
     "vite-plugin-svgr": "^4.0.0",
-    "@uniweb/core": "0.7.14"
+    "@uniweb/core": "0.7.15"
   },
   "peerDependenciesMeta": {
     "vite": {

package/src/site/content-collector.js

@@ -295,6 +295,16 @@ const CONTENT_PROFILES = {
   'document.yml': { contentDir: 'content', defaultMode: 'pages',    orderField: 'content' }
 }
 
+// Short profile aliases, so a caller that knows its own context can select
+// the profile explicitly (collectSiteContent's `profile` option) instead of
+// inferring it from the config filename. unipress — always a document tool —
+// uses this so an author can name a variant config anything (book.yml,
+// print.yml) without it being misread as a site.
+const PROFILE_ALIASES = {
+  document: CONTENT_PROFILES['document.yml'],
+  site: CONTENT_PROFILES['site.yml']
+}
+
 function getContentProfile(configFile) {
   return CONTENT_PROFILES[configFile] || CONTENT_PROFILES['site.yml']
 }
@@ -1813,29 +1823,49 @@ async function collectPagesRecursive(dirPath, parentRoute, siteRoot, orderConfig
  * @param {string} foundationPath - Path to foundation directory
  * @returns {Promise<{ vars: Object, layoutNames: Set<string> }>}
  */
-async function loadFoundationInfo(foundationPath) {
+export async function loadFoundationInfo(foundationPath) {
   if (!foundationPath) return { vars: {}, layoutNames: new Set() }
 
   // Try dist/meta/schema.json first (built foundation), then root schema.json
   const distSchemaPath = join(foundationPath, 'dist', 'meta', 'schema.json')
   const rootSchemaPath = join(foundationPath, 'schema.json')
 
-  const schemaPath = existsSync(distSchemaPath) ? distSchemaPath : rootSchemaPath
-
-  if (!existsSync(schemaPath)) {
-    return { vars: {}, layoutNames: new Set() }
+  const schemaPath = existsSync(distSchemaPath)
+    ? distSchemaPath
+    : existsSync(rootSchemaPath)
+      ? rootSchemaPath
+      : null
+
+  if (schemaPath) {
+    try {
+      const schemaContent = await readFile(schemaPath, 'utf8')
+      const schema = JSON.parse(schemaContent)
+      // Foundation config is in _self, support both 'vars' (new) and 'themeVars' (legacy)
+      const vars = schema._self?.vars || schema._self?.themeVars || schema.themeVars || {}
+      // Layout names from _layouts (keys are layout component names)
+      const layoutNames = new Set(schema._layouts ? Object.keys(schema._layouts) : [])
+      return { vars, layoutNames }
+    } catch (err) {
+      console.warn('[content-collector] Failed to load foundation schema:', err.message)
+      // Fall through to the source-config fallback below.
+    }
   }
 
+  // No built schema.json — the normal state for `uniweb dev` on a bundled-mode
+  // site that was never built (dev doesn't build the foundation to dist/). Read
+  // the foundation's declared vars straight from its source config
+  // (main.js / foundation.js) so theme tokens like --section-padding-y are
+  // defined; without them, components using py-[var(--section-padding-y)] render
+  // with collapsed section spacing. Layouts aren't resolved from source (they
+  // need component discovery), but they aren't needed to build the theme CSS.
   try {
-    const schemaContent = await readFile(schemaPath, 'utf8')
-    const schema = JSON.parse(schemaContent)
-    // Foundation config is in _self, support both 'vars' (new) and 'themeVars' (legacy)
-    const vars = schema._self?.vars || schema._self?.themeVars || schema.themeVars || {}
-    // Layout names from _layouts (keys are layout component names)
-    const layoutNames = new Set(schema._layouts ? Object.keys(schema._layouts) : [])
-    return { vars, layoutNames }
+    const { resolveFoundationSrcPath } = await import('../utils/foundation-source-root.js')
+    const { loadFoundationConfig } = await import('../schema.js')
+    const srcDir = resolveFoundationSrcPath(foundationPath)
+    const config = await loadFoundationConfig(srcDir)
+    return { vars: config?.vars || {}, layoutNames: new Set() }
   } catch (err) {
-    console.warn('[content-collector] Failed to load foundation schema:', err.message)
+    console.warn('[content-collector] Failed to load foundation source config:', err.message)
     return { vars: {}, layoutNames: new Set() }
   }
 }
@@ -1974,17 +2004,18 @@ async function collectLayouts(layoutDir, siteRoot, layoutNames = new Set()) {
  * @param {Object} options - Collection options
  * @param {string} options.foundationPath - Path to foundation directory (for theme vars)
  * @param {string} [options.configFile='site.yml'] - Name of the top-level config file inside sitePath. Defaults to 'site.yml'. Document tools (unipress) pass 'document.yml'.
+ * @param {'document'|'site'} [options.profile] - Explicit content profile, authoritative over the filename. Lets a tool that knows its context (unipress → 'document') read an arbitrarily named config with the right directory/mode/ordering. Falls back to the configFile-derived profile when omitted.
  * @returns {Promise<Object>} Site content object with assets manifest
  */
 export async function collectSiteContent(sitePath, options = {}) {
-  const { foundationPath, configFile = 'site.yml' } = options
+  const { foundationPath, configFile = 'site.yml', profile: profileName } = options
 
   // Read site config and raw theme config
   const siteConfig = await readYamlFile(join(sitePath, configFile))
 
   // Profile selects workspace-root defaults: site.yml → pages/ + page mode +
   // pages: ordering; document.yml → content/ + folder mode + content: ordering.
-  const profile = getContentProfile(configFile)
+  const profile = (profileName && PROFILE_ALIASES[profileName]) || getContentProfile(configFile)
 
   // Resolve content paths from <config>.paths: group, defaulting per profile.
   // Backward compatibility: when the document profile's `content/` is missing