uniweb 0.2.3 → 0.2.5

package/README.md

@@ -136,7 +136,17 @@ uniweb create [project-name] [options]
 
 | Option              | Description                           |
 | ------------------- | ------------------------------------- |
-| `--template <type>` | Project template: `single` or `multi` |
+| `--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 |
 
 **Examples:**
 
@@ -152,6 +162,15 @@ uniweb create my-project --template single
 
 # Multi-site/foundation monorepo
 uniweb create my-workspace --template multi
+
+# Official marketing template (landing pages, pricing, testimonials)
+uniweb create my-site --template marketing
+
+# From npm package
+uniweb create my-site --template @myorg/starter-template
+
+# From GitHub repository
+uniweb create my-site --template github:myorg/uniweb-template
 ```
 
 ### `build`
@@ -187,7 +206,9 @@ uniweb build --platform vercel
 
 ## Project Templates
 
-### Single (Default)
+### Built-in Templates
+
+#### Single (Default)
 
 A minimal workspace with a site and foundation as sibling packages. This is the recommended starting point.
 
@@ -233,7 +254,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.
 
@@ -265,6 +286,44 @@ Use this when you need:
 - Multiple foundations for different purposes
 - A testing site for foundation development
 
+### Official Templates
+
+Feature-rich templates that demonstrate what's possible with Uniweb. These include real components, sample content, and production-ready structure.
+
+#### Marketing
+
+A complete marketing site with landing page components:
+
+```bash
+uniweb create my-site --template marketing
+```
+
+**Includes:**
+- **Hero** — Gradient/light/dark banner with CTAs
+- **Features** — Grid layout with icons
+- **Pricing** — Tiered pricing tables
+- **Testimonials** — Customer quotes
+- **CTA** — Call-to-action sections
+
+Perfect for product launches, SaaS websites, and business landing pages.
+
+### External Templates
+
+You can use templates from npm or GitHub:
+
+```bash
+# npm package
+uniweb create my-site --template @myorg/template-name
+
+# GitHub repository
+uniweb create my-site --template github:user/repo
+
+# GitHub with specific branch/tag
+uniweb create my-site --template github:user/repo#v1.0.0
+```
+
+External templates must follow the same structure as official templates. See [`@uniweb/templates`](https://github.com/uniweb/templates) for the template format specification.
+
 ## Dependency Management
 
 Each package manages its own dependencies:
@@ -401,6 +460,7 @@ Pages can define data sources that auto-generate subroutes. A `/blog` page can h
 
 - [`@uniweb/build`](https://github.com/uniweb/build) — Foundation build tooling
 - [`@uniweb/runtime`](https://github.com/uniweb/runtime) — Runtime loader for sites
+- [`@uniweb/templates`](https://github.com/uniweb/templates) — Official templates and template processing
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.2.3",
+  "version": "0.2.5",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -32,8 +32,8 @@
   },
   "dependencies": {
     "@uniweb/build": "^0.1.0",
-    "@uniweb/templates": "workspace:*",
     "prompts": "^2.4.2",
-    "tar": "^7.0.0"
+    "tar": "^7.0.0",
+    "@uniweb/templates": "0.1.2"
   }
-}
+}

package/src/index.js

@@ -451,7 +451,7 @@ Learn more:
   // Update site to reference workspace foundation
   const sitePackageJson = join(projectDir, 'site/package.json')
   const sitePkg = JSON.parse(readFile(sitePackageJson))
-  sitePkg.dependencies['foundation'] = 'workspace:*'
+  sitePkg.dependencies['foundation'] = 'file:../foundation'
   writeJSON(sitePackageJson, sitePkg)
 
   success(`Created project: ${projectName}`)
@@ -566,7 +566,7 @@ pnpm --filter foundations/marketing build
   // Update site to reference workspace foundation
   const sitePackageJson = join(projectDir, 'sites/marketing/package.json')
   const sitePkg = JSON.parse(readFile(sitePackageJson))
-  sitePkg.dependencies['marketing'] = 'workspace:*'
+  sitePkg.dependencies['marketing'] = 'file:../../foundations/marketing'
   writeJSON(sitePackageJson, sitePkg)
 
   // Update site.yml to reference the marketing foundation