uniweb 0.2.21 → 0.2.23

package/README.md

@@ -29,10 +29,10 @@ my-project/
 │   │   └── home/
 │   │       ├── page.yml      # Page metadata
 │   │       └── 1-hero.md     # Section content
-│   ├── locales/              # i18n (mirrors pages/)
-│   │   └── es/
-│   ├── src/
-│   │   └── main.jsx          # 1-line entry point
+│   ├── locales/              # i18n (hash-based translations)
+│   │   ├── manifest.json     # Auto-extracted strings
+│   │   └── es.json           # Spanish translations
+│   ├── main.js               # 1-line entry point
 │   ├── vite.config.js        # 3-line config
 │   └── public/               # Static assets
 │
@@ -86,14 +86,19 @@ Components receive validated, localized data. Natural content stays in markdown;
 export function Hero({ content, params }) {
   const { title } = content.main.header;
   const { paragraphs, links } = content.main.body;
-  const { theme = 'light' } = params;
+  const { theme = "light" } = params;
 
   return (
-    <section className={`py-20 text-center ${theme === 'dark' ? 'bg-gray-900 text-white' : ''}`}>
+    <section
+      className={`py-20 text-center ${theme === "dark" ? "bg-gray-900 text-white" : ""}`}
+    >
       <h1 className="text-4xl font-bold">{title}</h1>
       <p className="text-xl text-gray-600">{paragraphs[0]}</p>
       {links[0] && (
-        <a href={links[0].url} className="mt-8 px-6 py-3 bg-blue-600 text-white rounded inline-block">
+        <a
+          href={links[0].url}
+          className="mt-8 px-6 py-3 bg-blue-600 text-white rounded inline-block"
+        >
           {links[0].text}
         </a>
       )}
@@ -102,26 +107,9 @@ export function Hero({ content, params }) {
 }
 ```
 
-Standard React. Standard Tailwind. The `{ content, params }` interface is only for *exposed* components—the ones content creators select in markdown frontmatter. Internal components (the majority of your codebase) use regular React props.
+Standard React. Standard Tailwind. The `{ content, params }` interface is only for _exposed_ components—the ones content creators select in markdown frontmatter. Internal components (the majority of your codebase) use regular React props.
 
-No framework to learn. Foundations are purpose-built component systems designed for a specific domain (marketing, documentation, learning, etc.). Sites are Vite apps that load content from markdown files. Configuration is minimal—both site and foundation use 3-line Vite configs:
-
-```javascript
-// site/vite.config.js
-import { defineSiteConfig } from '@uniweb/build/site'
-export default defineSiteConfig()
-
-// foundation/vite.config.js
-import { defineFoundationConfig } from '@uniweb/build'
-export default defineFoundationConfig()
-```
-
-The site entry point is equally minimal:
-
-```javascript
-// site/src/main.jsx
-import 'virtual:uniweb-site-entry'
-```
+No framework to learn. Foundations are purpose-built component systems designed for a specific domain (marketing, documentation, learning, etc.). Sites are Vite apps that load content from markdown files.
 
 ## The Bigger Picture
 
@@ -146,6 +134,7 @@ npm install -g uniweb
 ```
 
 **Requirements:**
+
 - Node.js 20.19 or later
 - pnpm 9+ (recommended) or npm 10+
 
@@ -163,19 +152,19 @@ uniweb create [project-name] [options]
 
 **Options:**
 
-| Option              | Description                           |
-| ------------------- | ------------------------------------- |
-| `--template <type>` | Project template (see below)          |
+| Option              | Description                  |
+| ------------------- | ---------------------------- |
+| `--template <type>` | Project template (see below) |
 
 **Template Sources:**
 
-| Source | Example | Description |
-| ------ | ------- | ----------- |
-| Built-in | `single`, `multi` | Minimal starter templates |
-| Official | `marketing` | Feature-rich showcase templates |
-| npm | `@org/my-template` | Published npm packages |
-| GitHub | `github:user/repo` | GitHub repositories |
-| GitHub URL | `https://github.com/user/repo` | Full GitHub URLs |
+| Source     | Example                        | Description                     |
+| ---------- | ------------------------------ | ------------------------------- |
+| Built-in   | `single`, `multi`              | Minimal starter templates       |
+| Official   | `marketing`                    | Feature-rich showcase templates |
+| npm        | `@org/my-template`             | Published npm packages          |
+| GitHub     | `github:user/repo`             | GitHub repositories             |
+| GitHub URL | `https://github.com/user/repo` | Full GitHub URLs                |
 
 **Examples:**
 
@@ -233,11 +222,9 @@ uniweb build --target site
 uniweb build --platform vercel
 ```
 
-## Project Templates
-
-### Built-in Templates
+## Built-in Templates
 
-#### Single (Default)
+### Single (Default)
 
 A minimal workspace with a site and foundation as sibling packages. This is the recommended starting point.
 
@@ -249,11 +236,10 @@ my-project/
 │
 ├── site/                     # Site package (content + entry)
 │   ├── package.json
-│   ├── vite.config.js        # 3-line config using defineSiteConfig()
+│   ├── vite.config.js        # 3-line config
 │   ├── index.html
 │   ├── site.yml              # Site configuration (foundation, title, i18n)
-│   ├── src/
-│   │   └── main.jsx          # 1-line entry: import 'virtual:uniweb-site-entry'
+│   ├── main.js               # 1-line entry point
 │   ├── pages/                # Content pages (file-based routing)
 │   │   └── home/
 │   │       ├── page.yml
@@ -262,7 +248,7 @@ my-project/
 │
 └── foundation/               # Foundation package (components)
     ├── package.json
-    ├── vite.config.js        # 3-line config using defineFoundationConfig()
+    ├── vite.config.js        # 3-line config
     └── src/
         ├── index.js          # Component exports
         ├── entry-runtime.js  # Runtime entry (imports styles + index)
@@ -281,7 +267,7 @@ my-project/
 - **Zero extraction** — `foundation/` is already a complete, publishable package
 - **Scales naturally** — Rename to `sites/marketing/` and `foundations/marketing/` when needed
 
-#### Multi
+### Multi
 
 A monorepo for multi-site or multi-foundation development.
 
@@ -296,7 +282,7 @@ my-workspace/
 │   │   ├── package.json
 │   │   ├── vite.config.js    # 3-line config
 │   │   ├── site.yml
-│   │   ├── src/main.jsx      # 1-line entry
+│   │   ├── main.js         # 1-line entry point
 │   │   └── pages/
 │   └── docs/                 # Documentation site
 │
@@ -314,11 +300,11 @@ Use this when you need:
 - Multiple foundations for different purposes
 - A testing site for foundation development
 
-### Official Templates
+## Official Templates
 
 Feature-rich templates that demonstrate what's possible with Uniweb. These include real components, sample content, and production-ready structure.
 
-#### Marketing
+### Marketing
 
 A complete marketing site with landing page components:
 
@@ -331,11 +317,12 @@ uniweb create my-site --template marketing
 Perfect for product launches, SaaS websites, and business landing pages.
 
 **Tailwind v3 variant:**
+
 ```bash
 uniweb create my-site --template marketing --variant tailwind3
 ```
 
-#### Academic
+### Academic
 
 A professional academic site for researchers, labs, and departments:
 
@@ -347,7 +334,7 @@ uniweb create my-site --template academic
 
 Perfect for researcher portfolios, lab websites, and academic department sites.
 
-#### Docs
+### Docs
 
 A documentation site with navigation levels:
 
@@ -359,7 +346,7 @@ uniweb create my-site --template docs
 
 Perfect for technical documentation, guides, and API references.
 
-### External Templates
+## External Templates
 
 You can use templates from npm or GitHub:
 
@@ -406,14 +393,14 @@ cd foundation && pnpm add embla-carousel
 The `defineSiteConfig()` function handles all Vite configuration for sites:
 
 ```javascript
-import { defineSiteConfig } from '@uniweb/build/site'
+import { defineSiteConfig } from "@uniweb/build/site";
 
 export default defineSiteConfig({
   // All options are optional
-  tailwind: true,        // Enable Tailwind CSS v4 (default: true)
-  plugins: [],           // Additional Vite plugins
+  tailwind: true, // Enable Tailwind CSS v4 (default: true)
+  plugins: [], // Additional Vite plugins
   // ...any other Vite config options
-})
+});
 ```
 
 ### Foundation Configuration
@@ -421,28 +408,28 @@ export default defineSiteConfig({
 The `defineFoundationConfig()` function handles all Vite configuration for foundations:
 
 ```javascript
-import { defineFoundationConfig } from '@uniweb/build'
+import { defineFoundationConfig } from "@uniweb/build";
 
 export default defineFoundationConfig({
   // All options are optional
-  entry: 'src/entry-runtime.js',     // Entry point path
-  fileName: 'foundation',             // Output file name
-  externals: [],                      // Additional packages to externalize
-  includeDefaultExternals: true,      // Include react, @uniweb/core, etc.
-  tailwind: true,                     // Enable Tailwind CSS v4 Vite plugin
-  sourcemap: true,                    // Generate sourcemaps
-  plugins: [],                        // Additional Vite plugins
-  build: {},                          // Additional Vite build options
+  entry: "src/entry-runtime.js", // Entry point path
+  fileName: "foundation", // Output file name
+  externals: [], // Additional packages to externalize
+  includeDefaultExternals: true, // Include react, @uniweb/core, etc.
+  tailwind: true, // Enable Tailwind CSS v4 Vite plugin
+  sourcemap: true, // Generate sourcemaps
+  plugins: [], // Additional Vite plugins
+  build: {}, // Additional Vite build options
   // ...any other Vite config options
-})
+});
 ```
 
 For Tailwind CSS v3 projects, set `tailwind: false` and use PostCSS:
 
 ```javascript
 export default defineFoundationConfig({
-  tailwind: false  // Uses PostCSS instead of Vite plugin
-})
+  tailwind: false, // Uses PostCSS instead of Vite plugin
+});
 ```
 
 ## Foundation Build Process

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.2.21",
+  "version": "0.2.23",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -36,6 +36,9 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/build": "0.1.9"
+    "@uniweb/build": "0.1.9",
+    "@uniweb/kit": "0.1.4",
+    "@uniweb/core": "0.1.6",
+    "@uniweb/runtime": "0.2.3"
   }
 }

package/src/versions.js

@@ -63,17 +63,15 @@ export function getResolvedVersions() {
   const pkg = getCliPackageJson()
   const deps = { ...pkg.dependencies, ...pkg.devDependencies }
 
+  // All @uniweb/* packages are now direct dependencies of the CLI.
+  // When publishing with pnpm, workspace:* gets resolved to actual versions.
+  // Fallbacks are only used during local development.
   resolvedVersions = {
-    // Direct CLI dependencies - use fallbacks for workspace:* versions
-    '@uniweb/build': resolveVersionSpec(deps['@uniweb/build'], '^0.1.4'),
-    '@uniweb/templates': resolveVersionSpec(deps['@uniweb/templates'], '^0.1.6'),
-
-    // These come from @uniweb/build's dependencies, use compatible versions
-    '@uniweb/runtime': '^0.1.0',
-    '@uniweb/core': '^0.1.0',
-
-    // Foundation utility library (used by official templates)
-    '@uniweb/kit': '^0.1.0',
+    '@uniweb/build': resolveVersionSpec(deps['@uniweb/build'], '^0.1.0'),
+    '@uniweb/core': resolveVersionSpec(deps['@uniweb/core'], '^0.1.0'),
+    '@uniweb/kit': resolveVersionSpec(deps['@uniweb/kit'], '^0.1.0'),
+    '@uniweb/runtime': resolveVersionSpec(deps['@uniweb/runtime'], '^0.1.0'),
+    '@uniweb/templates': resolveVersionSpec(deps['@uniweb/templates'], '^0.1.0'),
 
     // CLI itself (use current version)
     'uniweb': `^${pkg.version}`,

package/templates/_shared/CLAUDE.md.hbs

@@ -34,7 +34,7 @@ cd site && pnpm build
 
 **Site:**
 - `site/vite.config.js` - 3-line config using `defineSiteConfig()` from `@uniweb/build/site`
-- `site/src/main.jsx` - 1-line entry: `import 'virtual:uniweb-site-entry'`
+- `site/main.js` - 1-line entry: `import 'virtual:uniweb-site-entry'`
 - `site/site.yml` - Site configuration (foundation path, title, i18n)
 - `site/pages/` - Content pages (file-based routing)
 

package/templates/multi/CLAUDE.md.hbs

@@ -73,7 +73,7 @@ pnpm build:all
 
 **Sites:**
 - `sites/*/vite.config.js` - 3-line config using `defineSiteConfig()` from `@uniweb/build/site`
-- `sites/*/src/main.jsx` - 1-line entry: `import 'virtual:uniweb-site-entry'`
+- `sites/*/main.js` - 1-line entry: `import 'virtual:uniweb-site-entry'`
 - `sites/*/site.yml` - Site configuration (foundation reference, title, i18n)
 - `sites/*/pages/` - Content pages (file-based routing)
 

package/templates/multi/README.md.hbs

@@ -26,7 +26,7 @@ Visit `http://localhost:5173` to see your site.
 │   └── main/            # Main site
 │       ├── pages/
 │       ├── site.yml
-│       ├── src/main.jsx
+│       ├── main.js
 │       └── vite.config.js
 │
 ├── CLAUDE.md            # AI assistant instructions

package/templates/multi/sites/main/index.html.hbs

@@ -8,6 +8,6 @@
   </head>
   <body>
     <div id="root"></div>
-    <script type="module" src="/src/main.jsx"></script>
+    <script type="module" src="/main.js"></script>
   </body>
 </html>

package/templates/single/site/index.html.hbs

@@ -14,6 +14,6 @@
     <div id="root">
       <div class="loading">Loading...</div>
     </div>
-    <script type="module" src="/src/main.jsx"></script>
+    <script type="module" src="/main.js"></script>
   </body>
 </html>

package/templates/template/template/site/index.html.hbs

@@ -8,6 +8,6 @@
   </head>
   <body>
     <div id="root"></div>
-    <script type="module" src="/src/main.jsx"></script>
+    <script type="module" src="/main.js"></script>
   </body>
 </html>