uniweb 0.2.32 → 0.2.36

package/README.md

@@ -324,7 +324,7 @@ my-project/
     └── src/
         ├── styles.css        # Tailwind CSS v4
         ├── meta.js           # Foundation metadata
-        ├── runtime.js        # (optional) Custom Layout, props
+        ├── exports.js        # (optional) Custom Layout, props
         └── components/
             └── Section/
                 ├── index.jsx

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.2.32",
+  "version": "0.2.36",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -8,7 +8,8 @@
   },
   "files": [
     "src",
-    "templates"
+    "templates",
+    "partials"
   ],
   "keywords": [
     "uniweb",
@@ -36,9 +37,9 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/build": "0.1.15",
-    "@uniweb/runtime": "0.2.8",
-    "@uniweb/core": "0.1.7",
+    "@uniweb/build": "0.1.19",
+    "@uniweb/runtime": "0.2.10",
+    "@uniweb/core": "0.1.8",
     "@uniweb/kit": "0.1.4"
   }
 }

package/partials/adding-pages.hbs

@@ -0,0 +1,29 @@
+### Adding a New Page
+
+1. Create a folder: `site/pages/my-page/`
+2. Add `page.yml`:
+   ```yaml
+   title: My Page
+   ```
+3. Add section files: `1-hero.md`, `2-content.md`, etc.
+
+### Section Ordering
+
+By default, sections are discovered from `.md` files and sorted by numeric prefix (`1-`, `2-`, `2.5-`).
+
+For more control, use the `sections` property in `page.yml`:
+
+```yaml
+title: My Page
+sections:
+  - hero
+  - features
+  - pricing
+```
+
+This approach makes reordering easy (just move lines) and allows temporarily removing sections by commenting them out.
+
+**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

package/partials/ai-assistance.hbs

@@ -0,0 +1,3 @@
+## AI Assistance
+
+See [CLAUDE.md](./CLAUDE.md) for detailed instructions that AI assistants can use.

package/partials/claude-md.hbs

@@ -0,0 +1,226 @@
+# CLAUDE.md
+
+This file provides guidance for AI assistants working with this Uniweb project.
+
+## Project Structure
+
+Uniweb projects have two structures. A single project can be converted to multi-site:
+
+**Single (one foundation, one site):**
+```
+project/
+├── foundation/     # Purpose-built component library (React)
+├── site/           # Content (markdown pages)
+└── pnpm-workspace.yaml
+```
+
+**Multi-site (multiple foundations and sites):**
+```
+project/
+├── foundations/        # Purpose-built component libraries
+│   └── marketing/
+├── sites/              # Content sites
+│   └── my-org/
+└── pnpm-workspace.yaml
+```
+
+- **Foundation**: React components. Components with `meta.js` are *exposed* to content authors.
+- **Site**: Markdown content. Each section references a component via `type:` in frontmatter.
+
+## Commands
+
+```bash
+pnpm install    # Install dependencies
+pnpm dev        # Start dev server (runs default/main site)
+pnpm build      # Build for production
+```
+
+Multi-site also supports:
+```bash
+pnpm dev:all    # Start all sites in parallel
+pnpm build:all  # Build all sites
+```
+
+## Discovering Components
+
+Exposed components live in `foundation/src/components/` (or `foundations/*/src/components/`).
+
+```bash
+# List exposed components (those with meta.js)
+ls foundation/src/components/*/meta.js
+```
+
+**Understanding a component:**
+
+1. **`meta.js`** - Defines the component's interface:
+   - `title`, `description` - What the component does
+   - `elements` - What content it expects (title, paragraphs, links, items, etc.)
+   - `properties` - Configurable parameters (theme, layout, etc.)
+   - `hidden: true` - Component exists but isn't selectable from frontmatter
+
+2. **`index.jsx`** - The React implementation
+
+3. **Existing content** - See how the component is used in `site/pages/`
+
+**Note:** Components without `meta.js` are internal helpers used by other components.
+
+## Content Authoring
+
+### Section Format
+
+Each section is a markdown file with YAML frontmatter:
+
+```markdown
+---
+type: ComponentName   # Must match an exposed component
+theme: dark           # Parameter from meta.js properties
+---
+
+### Eyebrow Text      # H3 before H1 → pretitle
+
+# Main Headline       # H1 → title
+
+## Subtitle           # H2 after H1 → subtitle
+
+Description paragraph.
+
+[Call to Action](#link)
+
+![Image](image.jpg)
+```
+
+### Content Structure
+
+The semantic parser extracts markdown into:
+
+- **`content.main.header`** - title, pretitle, subtitle
+- **`content.main.body`** - paragraphs, links, imgs, lists
+- **`content.items`** - Groups created by H3 headings (each with its own header/body)
+
+### Page Organization
+
+```
+site/pages/                    # or sites/*/pages/
+├── @header/                   # Rendered on all pages
+├── @footer/                   # Rendered on all pages
+└── [page-name]/
+    ├── page.yml               # title, description, order
+    └── 1-section.md           # Numbered for ordering
+```
+
+**page.yml options:**
+```yaml
+title: About Us
+description: Learn about our company
+order: 2                 # Sort order in navigation
+
+# Section ordering (optional)
+sections:
+  - hero
+  - features
+  - pricing
+```
+
+**Section ordering:**
+- Default: `.md` files discovered and sorted by numeric prefix (`1-`, `2-`, `2.5-`)
+- Explicit: Use `sections: [hero, features]` — no prefixes needed, easy reordering
+- Empty: `sections: []` or no `.md` files — pure route with no content
+- Wildcard: `sections: *` — explicitly use default behavior
+
+## Component Development
+
+### Props Interface
+
+```jsx
+function MyComponent({ content, params, block, website }) {
+  const { title, pretitle } = content.main?.header || {}
+  const { paragraphs = [], links = [] } = content.main?.body || {}
+  const items = content.items || []
+  // ...
+}
+```
+
+### Using @uniweb/kit
+
+```jsx
+import { H1, P, Link, Image, Section, cn } from '@uniweb/kit'
+```
+
+- `H1, H2, H3, P, Span` - Typography (handles arrays, filters empty)
+- `Link` - Smart routing
+- `Image` - Optimized images
+- `Section` - Layout wrapper
+- `cn()` - Tailwind class merging
+
+### Creating a New Component
+
+1. Create `foundation/src/components/NewComponent/index.jsx`
+2. Create `foundation/src/components/NewComponent/meta.js`
+3. Export from `foundation/src/index.js`
+4. Rebuild: `cd foundation && pnpm build`
+
+### meta.js Structure
+
+```javascript
+export default {
+  title: 'Component Name',
+  description: 'What it does',
+  // hidden: true,  // Uncomment to hide from content authors
+  elements: {
+    title: { label: 'Headline', required: true },
+    paragraphs: { label: 'Description' },
+    links: { label: 'Call to Action' },
+  },
+  properties: {
+    theme: {
+      type: 'select',
+      label: 'Theme',
+      options: [
+        { value: 'light', label: 'Light' },
+        { value: 'dark', label: 'Dark' },
+      ],
+      default: 'light',
+    },
+  },
+}
+```
+
+### Parameter Philosophy
+
+Design parameters that describe **intent**, not implementation:
+
+| Good | Bad |
+|------|-----|
+| `theme: "dark"` | `backgroundColor: "#1a1a1a"` |
+| `layout: "split"` | `gridTemplateColumns: "1fr 1fr"` |
+| `size: "large"` | `fontSize: "2rem"` |
+
+## Tailwind CSS v4
+
+Theme is defined in `foundation/src/styles.css`:
+
+```css
+@import "tailwindcss";
+@source "./components/**/*.{js,jsx}";
+
+@theme {
+  --color-primary: #3b82f6;
+}
+```
+
+Use with: `bg-primary`, `text-primary`, `bg-primary/10` (10% opacity)
+
+## Troubleshooting
+
+**"Could not load foundation"**
+- Single: Check `site/package.json` has `"foundation": "file:../foundation"`
+- Multi: Check `sites/*/package.json` has `"default": "file:../../foundations/default"`
+
+**Component not appearing**
+1. Verify `meta.js` exists and doesn't have `hidden: true`
+2. Check it's exported from `foundation/src/index.js`
+3. Rebuild: `cd foundation && pnpm build`
+
+**Styles not applying**
+1. Verify `@source` in styles.css includes your component path
+2. Check custom color names match `@theme` definitions

package/partials/components-docs.hbs

@@ -0,0 +1,15 @@
+## Component Documentation
+
+Generate up-to-date documentation for all foundation components:
+
+```bash
+# From within the foundation directory
+pnpm docs
+```
+
+This creates `COMPONENTS.md` with full details on each component's:
+- Content elements (title, paragraphs, links, images, items)
+- Parameters (theme, layout, columns, etc.)
+- Presets (pre-configured parameter combinations)
+
+The documentation is generated from component `meta.js` files, so it's always current.

package/partials/deployment.hbs

@@ -0,0 +1,13 @@
+## Deployment
+
+Build and deploy the `site/dist` folder:
+
+```bash
+pnpm build
+```
+
+**Supported platforms:**
+- **Vercel**: `cd site && vercel`
+- **Netlify**: Build command `pnpm build`, publish `site/dist`
+- **GitHub Pages**: Use GitHub Actions
+- **Cloudflare Pages**: Connect repo, set `pnpm build` and `site/dist`

package/partials/exports-js.hbs

@@ -0,0 +1,14 @@
+/**
+ * Foundation Exports
+ *
+ * Optional file to export foundation-level capabilities to the runtime:
+ * - Layout: Custom page layout component (receives header, body, footer, sidebars)
+ * - props: Foundation-wide props accessible via website.foundationProps
+ *
+ * The Layout component receives pre-rendered page areas as props:
+ * - page, website: Runtime context
+ * - header, body, footer: Core page regions (pre-rendered React elements)
+ * - left/leftPanel, right/rightPanel: Sidebar panels
+ *
+ * If this file is not provided, the runtime uses a default layout (header -> body -> footer).
+ */

package/partials/learn-more.hbs

@@ -0,0 +1,5 @@
+## Learn More
+
+- [Uniweb Documentation](https://github.com/uniweb/cli)
+- [@uniweb/kit Components](https://www.npmjs.com/package/@uniweb/kit)
+- [Tailwind CSS v4](https://tailwindcss.com)

package/partials/quick-start.hbs

@@ -0,0 +1,8 @@
+## Quick Start
+
+```bash
+pnpm install    # Install dependencies
+pnpm dev        # Start development server
+```
+
+Visit `http://localhost:5173` to see your site.

package/src/commands/build.js

@@ -279,6 +279,46 @@ async function generateLocalizedHtml(projectDir, i18nConfig) {
   }
 }
 
+/**
+ * Resolve foundation directory based on site config and project structure
+ *
+ * For single projects: ../foundation
+ * For multi projects: ../../foundations/{name}
+ */
+function resolveFoundationDir(projectDir, siteConfig) {
+  const foundationName = siteConfig?.foundation
+
+  // Check if we're in a multi-site structure (site is under sites/)
+  const parentDir = join(projectDir, '..')
+  const grandParentDir = join(projectDir, '..', '..')
+  const isMultiSite = parentDir.endsWith('/sites') || parentDir.endsWith('\\sites')
+
+  if (isMultiSite && foundationName) {
+    // Multi-site: look for foundations/{name}
+    const multiFoundationDir = join(grandParentDir, 'foundations', foundationName)
+    if (existsSync(multiFoundationDir)) {
+      return multiFoundationDir
+    }
+  }
+
+  // Single site: ../foundation
+  const singleFoundationDir = join(projectDir, '..', 'foundation')
+  if (existsSync(singleFoundationDir)) {
+    return singleFoundationDir
+  }
+
+  // Fallback: try to find by foundation name in parent
+  if (foundationName) {
+    const namedFoundationDir = join(parentDir, foundationName)
+    if (existsSync(namedFoundationDir)) {
+      return namedFoundationDir
+    }
+  }
+
+  // Ultimate fallback
+  return singleFoundationDir
+}
+
 /**
  * Build a site
  */
@@ -330,7 +370,7 @@ async function buildSite(projectDir, options = {}) {
       const { prerenderSite } = await import('@uniweb/build/prerender')
 
       const result = await prerenderSite(projectDir, {
-        foundationDir: foundationDir || join(projectDir, '..', 'foundation'),
+        foundationDir: foundationDir || resolveFoundationDir(projectDir, siteConfig),
         onProgress: (msg) => log(`  ${colors.dim}${msg}${colors.reset}`)
       })
 

package/src/templates/processor.js

@@ -58,7 +58,7 @@ export function clearMissingVersions() {
 function registerPartials() {
   if (partialsRegistered) return
 
-  const partialsDir = path.join(__dirname, '..', 'partials')
+  const partialsDir = path.join(__dirname, '..', '..', 'partials')
 
   if (!existsSync(partialsDir)) {
     partialsRegistered = true

package/templates/_shared/CLAUDE.md.hbs

@@ -1,148 +1 @@
-# CLAUDE.md - AI Assistant Instructions
-
-This file provides guidance for AI assistants working with this Uniweb project.
-
-## Project Overview
-
-This is a **Uniweb** project - a component web platform that separates content from code.
-
-```
-{{projectName}}/
-├── foundation/     # React component library (code)
-├── site/           # Content and pages (markdown)
-├── package.json    # Root workspace config
-└── pnpm-workspace.yaml
-```
-
-## Quick Commands
-
-```bash
-# Install dependencies
-pnpm install
-
-# Start development server (site with foundation)
-pnpm dev
-
-# Build foundation (generates dist/foundation.js and schema.json)
-cd foundation && pnpm build
-
-# Build site for production (outputs to site/dist/)
-cd site && pnpm build
-```
-
-## Key Files
-
-**Site:**
-- `site/vite.config.js` - 3-line config using `defineSiteConfig()` from `@uniweb/build/site`
-- `site/main.js` - Entry point using `start()` from `@uniweb/runtime`
-- `site/site.yml` - Site configuration (foundation path, title, i18n)
-- `site/pages/` - Content pages (file-based routing)
-
-**Foundation:**
-- `foundation/vite.config.js` - 3-line config using `defineFoundationConfig()` from `@uniweb/build`
-- `foundation/src/styles.css` - Tailwind CSS v4 theme
-- `foundation/src/components/*/meta.js` - Component metadata (makes component exposed)
-- `foundation/src/runtime.js` - (optional) Custom Layout and foundation props
-- `foundation/src/_entry.generated.js` - Auto-generated at build/dev time
-
-## Architecture
-
-### Foundation Package (`/foundation`)
-
-The **foundation** is a React component library. Components with a `meta.js` file are **exposed** (available to content creators via `type:` in frontmatter). Exposed components:
-
-1. Receive structured content parsed from markdown
-2. Have configurable parameters (theme, layout, etc.)
-3. Render content according to their design
-
-Internal components (no `meta.js`) are regular React components used within exposed components.
-
-**Key directories:**
-- `src/components/*/` - Component implementations
-- `src/components/*/meta.js` - Component metadata (makes component exposed)
-- `src/styles.css` - Global Tailwind styles
-
-### Site Package (`/site`)
-
-The **site** contains content written in markdown. The runtime loads the foundation and renders content based on component selections.
-
-**Key directories:**
-- `pages/` - Content pages organized in folders
-- `pages/[page-name]/page.yml` - Page metadata
-- `pages/[page-name]/*.md` - Content sections
-
-## Content Authoring
-
-### Section File Format
-
-```markdown
----
-type: ComponentName
-theme: dark
-layout: center
----
-
-# Main Headline
-
-Description paragraph.
-
-[Call to Action](#link)
-```
-
-### Content Structure
-
-The semantic parser extracts content into:
-
-- **`content.main.header`**: title, pretitle, subtitle
-- **`content.main.body`**: paragraphs, links, imgs, lists
-- **`content.items`**: Content groups from H3 headings
-
-## Component Development
-
-### Component Interface
-
-```jsx
-function MyComponent({ content, params, block, website }) {
-  const { title } = content.main?.header || {}
-  const { paragraphs = [] } = content.main?.body || {}
-  // ...
-}
-```
-
-### Using @uniweb/kit
-
-```jsx
-import { H1, P, Link, cn } from '@uniweb/kit'
-```
-
-### Component Metadata (`meta.js`)
-
-```javascript
-export default {
-  title: 'Component Name',
-  description: 'What the component does',
-  category: 'Content',
-  elements: { /* content elements */ },
-  properties: { /* configurable params */ },
-}
-```
-
-## Tailwind CSS v4
-
-This project uses Tailwind CSS v4 with the Vite plugin.
-
-**Theme customization** (`foundation/src/styles.css`):
-
-```css
-@import "tailwindcss";
-@source "./components/**/*.{js,jsx}";
-@theme {
-  --color-primary: #3b82f6;
-}
-```
-
-## Resources
-
-- [Uniweb Documentation](https://github.com/uniweb/uniweb)
-- [@uniweb/kit Documentation](https://www.npmjs.com/package/@uniweb/kit)
-- [Tailwind CSS v4](https://tailwindcss.com/docs)
+{{> claude-md}}

package/templates/multi/CLAUDE.md.hbs

@@ -1,100 +1 @@
-# CLAUDE.md - AI Assistant Instructions
-
-This file provides guidance for AI assistants working with this Uniweb multi-site workspace.
-
-## Project Overview
-
-This is a **Uniweb multi-site workspace** - supporting multiple sites and foundations.
-
-```
-{{projectName}}/
-├── foundations/        # Shared component libraries
-│   └── default/        # Default foundation
-├── sites/              # Content sites
-│   └── main/           # Main site
-├── package.json        # Root workspace config
-└── pnpm-workspace.yaml
-```
-
-## Quick Commands
-
-```bash
-# Install dependencies
-pnpm install
-
-# Start main site development
-pnpm dev
-
-# Start all sites in parallel
-pnpm dev:all
-
-# Build main site
-pnpm build
-
-# Build all sites
-pnpm build:all
-```
-
-## Adding New Sites
-
-1. Copy an existing site directory:
-   ```bash
-   cp -r sites/main sites/newsite
-   ```
-
-2. Update `sites/newsite/package.json` with a unique name
-
-3. Update `sites/newsite/site.yml` with site configuration
-
-4. Run `pnpm install` to link the new site
-
-## Adding New Foundations
-
-1. Copy an existing foundation:
-   ```bash
-   cp -r foundations/default foundations/newfoundation
-   ```
-
-2. Update `foundations/newfoundation/package.json` with a unique name
-
-3. In your site's `site.yml`, reference the foundation:
-   ```yaml
-   foundation: newfoundation
-   ```
-
-4. In your site's `package.json`, add the dependency:
-   ```json
-   "dependencies": {
-     "newfoundation": "file:../../foundations/newfoundation"
-   }
-   ```
-
-## Key Files
-
-**Sites:**
-- `sites/*/vite.config.js` - 3-line config using `defineSiteConfig()` from `@uniweb/build/site`
-- `sites/*/main.js` - Entry point using `start()` from `@uniweb/runtime`
-- `sites/*/site.yml` - Site configuration (foundation reference, title, i18n)
-- `sites/*/pages/` - Content pages (file-based routing)
-
-**Foundations:**
-- `foundations/*/vite.config.js` - 3-line config using `defineFoundationConfig()` from `@uniweb/build`
-- `foundations/*/src/styles.css` - Tailwind CSS v4 theme
-- `foundations/*/src/components/*/meta.js` - Component metadata (makes component exposed)
-- `foundations/*/src/runtime.js` - (optional) Custom Layout and foundation props
-
-## Architecture
-
-### Foundations (`/foundations/*`)
-
-Each foundation is a React component library. Sites can share foundations or have their own.
-
-### Sites (`/sites/*`)
-
-Each site contains content in markdown. A site references one foundation for its components.
-
-## Resources
-
-- [Uniweb Documentation](https://github.com/uniweb/uniweb)
-- [@uniweb/kit Documentation](https://www.npmjs.com/package/@uniweb/kit)
-- [Tailwind CSS v4](https://tailwindcss.com/docs)
+{{> claude-md}}

package/templates/multi/README.md.hbs

@@ -1,15 +1,8 @@
 # {{projectName}}
 
-A multi-site workspace built with [Uniweb](https://github.com/uniweb/uniweb) — a component web platform that separates content from code.
+A multi-site workspace built with [Uniweb](https://github.com/uniweb/cli) — a component web platform that separates content from code.
 
-## Quick Start
-
-```bash
-pnpm install    # Install dependencies
-pnpm dev        # Start main site development
-```
-
-Visit `http://localhost:5173` to see your site.
+{{> quick-start}}
 
 ## Project Structure
 
@@ -33,6 +26,8 @@ Visit `http://localhost:5173` to see your site.
 └── README.md            # This file
 ```
 
+{{> components-docs}}
+
 ## Commands
 
 ```bash
@@ -85,12 +80,6 @@ This allows:
 - Single source of truth for design
 - Foundation updates propagate to all sites
 
-## AI Assistance
-
-See [CLAUDE.md](./CLAUDE.md) for detailed instructions that AI assistants can use.
-
-## Learn More
+{{> ai-assistance}}
 
-- [Uniweb Documentation](https://github.com/uniweb/uniweb)
-- [@uniweb/kit Components](https://www.npmjs.com/package/@uniweb/kit)
-- [Tailwind CSS v4](https://tailwindcss.com)
+{{> learn-more}}

package/templates/multi/foundations/default/package.json.hbs

@@ -14,7 +14,8 @@
     "dev": "vite",
     "build": "uniweb build",
     "build:vite": "vite build",
-    "preview": "vite preview"
+    "preview": "vite preview",
+    "docs": "uniweb docs"
   },
   "peerDependencies": {
     "react": "^18.0.0 || ^19.0.0",

package/templates/multi/foundations/default/src/_entry.generated.js

@@ -0,0 +1,13 @@
+// Auto-generated foundation entry point
+// DO NOT EDIT - This file is regenerated during build
+
+import './styles.css'
+import Section from './components/Section/index.jsx'
+
+export const components = { Section }
+
+export { Section }
+
+export const capabilities = null
+
+export const meta = {}

package/templates/multi/foundations/default/src/exports.js.hbs

@@ -0,0 +1,11 @@
+{{> exports-js}}
+
+// import Layout from './components/Layout'
+
+export default {
+  // Uncomment to use a custom page layout:
+  // Layout,
+
+  // Foundation-wide props (accessible via website.foundationProps):
+  props: {},
+}

package/templates/single/README.md.hbs

@@ -1,15 +1,8 @@
 # {{projectName}}
 
-A website built with [Uniweb](https://github.com/uniweb/uniweb) — a component web platform that separates content from code.
+A website built with [Uniweb](https://github.com/uniweb/cli) — a component web platform that separates content from code.
 
-## Quick Start
-
-```bash
-pnpm install    # Install dependencies
-pnpm dev        # Start development server
-```
-
-Visit `http://localhost:5173` to see your site.
+{{> quick-start}}
 
 ## Project Structure
 
@@ -49,10 +42,7 @@ Your content here.
 [Call to Action](#)
 ```
 
-**Page structure:**
-- Create folder: `site/pages/about/`
-- Add `page.yml` with title and metadata
-- Add sections: `1-intro.md`, `2-team.md`, etc.
+{{> adding-pages}}
 
 ## Component Development
 
@@ -78,6 +68,8 @@ export default Hero
 
 Exposed components (selectable via `type:` in frontmatter) need a `meta.js` file.
 
+{{> components-docs}}
+
 ## Building
 
 ```bash
@@ -90,12 +82,6 @@ cd site && pnpm build
 
 Deploy `site/dist/` to any static host (Vercel, Netlify, Cloudflare Pages, etc.)
 
-## AI Assistance
-
-See [CLAUDE.md](./CLAUDE.md) for detailed instructions that AI assistants can use.
-
-## Learn More
+{{> ai-assistance}}
 
-- [Uniweb Documentation](https://github.com/uniweb/uniweb)
-- [@uniweb/kit Components](https://www.npmjs.com/package/@uniweb/kit)
-- [Tailwind CSS v4](https://tailwindcss.com)
+{{> learn-more}}

package/templates/single/foundation/package.json.hbs

@@ -11,11 +11,11 @@
   },
   "files": ["dist", "src"],
   "scripts": {
-    "postinstall": "node scripts/generate-entry.js",
     "dev": "vite",
     "build": "uniweb build",
     "build:vite": "vite build",
-    "preview": "vite preview"
+    "preview": "vite preview",
+    "docs": "uniweb docs"
   },
   "peerDependencies": {
     "react": "^18.0.0 || ^19.0.0",

package/templates/single/foundation/src/_entry.generated.js

@@ -0,0 +1,13 @@
+// Auto-generated foundation entry point
+// DO NOT EDIT - This file is regenerated during build
+
+import './styles.css'
+import Section from './components/Section/index.jsx'
+
+export const components = { Section }
+
+export { Section }
+
+export const capabilities = null
+
+export const meta = {}

package/templates/single/foundation/src/exports.js.hbs

@@ -0,0 +1,11 @@
+{{> exports-js}}
+
+// import Layout from './components/Layout'
+
+export default {
+  // Uncomment to use a custom page layout:
+  // Layout,
+
+  // Foundation-wide props (accessible via website.foundationProps):
+  props: {},
+}

package/templates/template/template/CLAUDE.md.hbs

@@ -66,5 +66,5 @@ uniweb create myproject --template github:user/repo
 
 ## Resources
 
-- [Uniweb Documentation](https://github.com/uniweb/uniweb)
+- [Uniweb Documentation](https://github.com/uniweb/cli)
 - [@uniweb/kit Documentation](https://www.npmjs.com/package/@uniweb/kit)

package/templates/template/template/foundation/src/_entry.generated.js

@@ -0,0 +1,14 @@
+// Auto-generated foundation entry point
+// DO NOT EDIT - This file is regenerated during build
+
+import './styles.css'
+import Features from './components/Features/index.jsx'
+import Hero from './components/Hero/index.jsx'
+
+export const components = { Features, Hero }
+
+export { Features, Hero }
+
+export const runtime = null
+
+export const meta = {}

package/templates/multi/foundations/default/src/index.js

@@ -1,32 +0,0 @@
-/**
- * Default Foundation Entry Point
- */
-
-import Section from './components/Section/index.jsx'
-
-const components = {
-  Section,
-}
-
-export function getComponent(name) {
-  return components[name]
-}
-
-export function listComponents() {
-  return Object.keys(components)
-}
-
-export function getSchema(name) {
-  return components[name]?.schema
-}
-
-export function getAllSchemas() {
-  const schemas = {}
-  for (const [name, component] of Object.entries(components)) {
-    if (component.schema) schemas[name] = component.schema
-  }
-  return schemas
-}
-
-export { Section }
-export default { getComponent, listComponents, getSchema, getAllSchemas, components }

package/templates/single/foundation/scripts/generate-entry.js

@@ -1,15 +0,0 @@
-/**
- * Generate Foundation Entry Point
- *
- * This script is called during postinstall to ensure the foundation
- * entry point exists before the site dev server starts.
- */
-
-import { generateEntryPoint } from '@uniweb/build'
-
-try {
-  await generateEntryPoint('./src', './src/_entry.generated.js')
-} catch (err) {
-  // Silently fail during initial install if dependencies aren't ready
-  console.warn('Note: Entry generation skipped (run foundation dev/build to generate)')
-}