uniweb 0.5.14 → 0.6.0

package/README.md

@@ -13,7 +13,7 @@ pnpm install
 pnpm dev
 ```
 
-Open http://localhost:5173 to see your site. Edit files in `site/pages/` and `foundation/src/components/` to see changes instantly.
+Open http://localhost:5173 to see your site. Edit files in `site/pages/` and `foundation/src/sections/` to see changes instantly.
 
 > **Need pnpm?** Run `npm install -g pnpm` or see [pnpm installation](https://pnpm.io/installation).
 
@@ -27,7 +27,7 @@ pnpm build      # Build foundation + site for production
 pnpm preview    # Preview the production build
 ```
 
-The `build` command generates static HTML in `site/dist/`. Open those files to verify your output before deploying.
+The `build` command outputs to `site/dist/`. With pre-rendering enabled (the default for official templates), you get static HTML files ready to deploy anywhere.
 
 The `marketing` template includes real components (Hero, Features, Pricing, Testimonials, FAQ, and more) with sample content—a working site you can explore and modify.
 
@@ -72,10 +72,13 @@ my-project/
 │
 └── foundation/               # Your components
     ├── src/
-    │   └── components/
-    │       └── Hero/
-    │           ├── index.jsx
-    │           └── meta.js
+    │   ├── sections/         # Section types (addressable from markdown)
+    │   │   ├── Hero.jsx      # Bare file → section type (no meta.js needed)
+    │   │   └── Features/
+    │   │       ├── meta.js   # Content interface (params, presets)
+    │   │       └── Features.jsx
+    │   └── components/       # Regular React components
+    │       └── Button.jsx
     ├── vite.config.js        # 3-line config
     └── dist/                 # Built output
 ```
@@ -128,22 +131,19 @@ Natural content stays in markdown; structured data goes in tagged blocks (YAML o
 ### Components as React
 
 ```jsx
-export function Hero({ content, params }) {
+export default function Hero({ content, params }) {
   const { title, paragraphs, links } = content
-  const { theme = 'light' } = params
 
   return (
-    <section
-      className={`py-20 text-center ${theme === 'dark' ? 'bg-gray-900 text-white' : ''}`}
-    >
+    <section className="py-20 text-center">
       <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}
+          href={links[0].href}
           className="mt-8 px-6 py-3 bg-blue-600 text-white rounded inline-block"
         >
-          {links[0].text}
+          {links[0].label}
         </a>
       )}
     </section>
@@ -151,7 +151,7 @@ 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 use regular React props.
+Standard React. Standard Tailwind. The `{ content, params }` interface is only for _section types_ — components that content creators select in markdown frontmatter. Everything else uses regular React props.
 
 ## Next Steps
 
@@ -163,7 +163,7 @@ After creating your project:
 
 3. **Learn the configuration** — Run `uniweb docs site` or `uniweb docs page` for quick reference on configuration options.
 
-4. **Create a component** — Add a folder in `foundation/src/components/`, create `index.jsx` and `meta.js`, then rebuild. See the [Component Metadata Guide](https://github.com/uniweb/cli/blob/main/docs/component-metadata.md) for the full schema.
+4. **Create a section type** — Add a file to `foundation/src/sections/` (e.g., `Banner.jsx`) and rebuild. Bare files at the root are discovered automatically — no `meta.js` needed. Add `meta.js` when you want to declare params or presets. See the [Component Metadata Guide](./docs/component-metadata.md) for the full schema.
 
 The `meta.js` file defines what content and parameters a component accepts. The runtime uses this metadata to apply defaults and guarantee content structure—no defensive null checks needed in your component code.
 
@@ -187,10 +187,10 @@ Save and see the change instantly in your browser.
 
 ### Your First Component Change
 
-Open `foundation/src/components/Hero/index.jsx`. The component receives parsed content:
+Open `foundation/src/sections/Hero.jsx`. The component receives parsed content:
 
 ```jsx
-export function Hero({ content, params }) {
+export default function Hero({ content }) {
   const { title, paragraphs, links, imgs, items } = content
   // Edit the JSX below...
 }
@@ -198,25 +198,6 @@ export function Hero({ content, params }) {
 
 The parser extracts semantic elements from markdown—`title` from the first heading, `paragraphs` from body text, `links` from `[text](url)`, and so on. The `items` array contains child groups created when headings appear after content (useful for features, pricing tiers, team members, etc.).
 
-**Learn more:**
-
-- [Site Configuration](./docs/site-configuration.md) — Complete site.yml reference
-- [Page Configuration](./docs/page-configuration.md) — Complete page.yml reference
-- [Content Structure](./docs/content-structure.md) — How content is parsed and structured
-- [Navigation Patterns](./docs/navigation-patterns.md) — Building navbars, menus, and sidebars
-- [Special Sections](./docs/special-sections.md) — @header, @footer, and sidebars
-- [Linking](./docs/linking.md) — Stable page references that survive reorganization
-- [Component Metadata](./docs/component-metadata.md) — Full meta.js schema reference
-- [Foundation Configuration](./docs/foundation-configuration.md) — CSS variables and custom Layout
-- [Site Theming](./docs/site-theming.md) — Colors, typography, and dark mode
-- [Internationalization](./docs/internationalization.md) — Multi-language sites
-- [Data Fetching](./docs/data-fetching.md) — Load external data from files or APIs
-- [Dynamic Routes](./docs/dynamic-routes.md) — Generate pages from data (blogs, catalogs)
-- [Content Collections](./docs/content-collections.md) — Manage articles, team members, and more
-- [Versioning](./docs/versioning.md) — Multi-version documentation
-- [Site Search](./docs/search.md) — Built-in full-text search
-- [Runtime API](./docs/runtime-api.md) — Hooks and core objects
-
 ## Foundations Are Portable
 
 The `foundation/` folder ships with your project as a convenience, but a foundation is a self-contained artifact with no dependency on any specific site. Sites reference foundations by configuration, not by folder proximity.
@@ -253,249 +234,26 @@ Start with local files deployed anywhere. The same foundation works across all t
 
 ---
 
-## Create a Project
-
-```bash
-# pnpm (recommended)
-pnpm create uniweb my-site --template marketing
-
-# npm (use -- before options)
-npm create uniweb@latest my-site -- --template marketing
-
-# npx
-npx uniweb@latest create my-site --template marketing
-```
-
-Alternatively, install the CLI globally:
-
-```bash
-npm install -g uniweb
-uniweb create my-site --template marketing
-```
-
-**Requirements:**
-
-- Node.js 20.19 or later
-- pnpm 10+ (recommended) or npm 10+
-
-Projects use Vite 7 and Tailwind CSS v4 by default.
-
-### Setting up pnpm
-
-We recommend pnpm for dependency management (npm also works). Install pnpm via npm:
-
-```bash
-npm install -g pnpm
-```
-
-Or see the [official pnpm installation guide](https://pnpm.io/installation) for other options including Corepack, Homebrew, and more.
-
-## Commands
-
-### `create`
-
-Create a new Uniweb project. See [Create a Project](#create-a-project) for usage examples.
-
-```bash
-uniweb create [project-name] [options]
-```
-
-**Options:**
-
-| 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                |
-
-### `build`
-
-Build the current project.
-
-```bash
-uniweb build [options]
-```
-
-**Options:**
-
-| Option              | Description                                                           |
-| ------------------- | --------------------------------------------------------------------- |
-| `--target <type>`   | Build target: `foundation` or `site` (auto-detected if not specified) |
-| `--prerender`       | Force pre-rendering (overrides site.yml)                              |
-| `--no-prerender`    | Skip pre-rendering (overrides site.yml)                               |
-| `--foundation-dir`  | Path to foundation directory (for prerendering)                       |
-| `--platform <name>` | Deployment platform (e.g., `vercel`) for platform-specific output     |
-
-**Examples:**
-
-```bash
-# Auto-detect and build
-uniweb build
-
-# Explicitly build as foundation
-uniweb build --target foundation
-
-# Explicitly build as site
-uniweb build --target site
-
-# Build site with pre-rendering (SSG) - force on
-uniweb build --prerender
-
-# Skip pre-rendering even if enabled in site.yml
-uniweb build --no-prerender
-
-# Build for Vercel deployment
-uniweb build --platform vercel
-```
-
-### Pre-rendering (SSG)
-
-Pre-rendering generates static HTML for each page at build time. Enable it in `site.yml`:
-
-```yaml
-build:
-  prerender: true
-```
-
-Or use the `--prerender` flag. This gives you:
-
-- **SEO**: Search engines see fully rendered content immediately
-- **Performance**: First contentful paint is instant
-- **Hosting**: Deploy to any static host (GitHub Pages, Netlify, S3, etc.)
-
-The pre-rendered HTML includes embedded site content. When the page loads, React hydrates the existing DOM—no flash of loading state, then full client-side interactivity.
-
-## Built-in Templates
-
-### Single (Default)
-
-A minimal workspace with a site and foundation as sibling packages. The recommended starting point.
-
-```
-my-project/
-├── package.json              # Workspace root
-├── pnpm-workspace.yaml
-├── site/
-│   ├── package.json
-│   ├── vite.config.js
-│   ├── site.yml
-│   ├── main.js
-│   └── pages/
-└── foundation/
-    ├── package.json
-    ├── vite.config.js
-    └── src/components/
-```
-
-### Multi
-
-A monorepo for foundation development or multi-site projects.
-
-```
-my-workspace/
-├── sites/
-│   ├── marketing/            # Main site or test site
-│   └── docs/                 # Additional site
-└── foundations/
-    ├── marketing/            # Primary foundation
-    └── documentation/        # Additional foundation
-```
-
-Use this when you need multiple sites sharing foundations, multiple foundations for different purposes, or test sites for foundation development.
-
-## Official Templates
-
-Feature-rich templates with real components and sample content. **[View all demos](https://uniweb.github.io/templates/)**
-
-### Marketing
-
-[**Live Demo**](https://uniweb.github.io/templates/marketing/) · `pnpm create uniweb my-site --template marketing`
-
-**Includes:** Hero, Features, Pricing, Testimonials, CTA, FAQ, Stats, LogoCloud, Video, Gallery, Team
-
-Perfect for product launches, SaaS websites, and business landing pages.
-
-**Tailwind v3 variant:** `--variant tailwind3`
-
-### Academic
-
-[**Live Demo**](https://uniweb.github.io/templates/academic/) · `pnpm create uniweb my-site --template academic`
-
-**Includes:** ProfileHero, PublicationList, ResearchAreas, TeamGrid, Timeline, ContactCard, Navbar, Footer
-
-Perfect for researcher portfolios, lab websites, and academic department sites.
-
-### Docs
-
-[**Live Demo**](https://uniweb.github.io/templates/docs/) · `pnpm create uniweb my-site --template docs`
-
-**Includes:** Header, LeftPanel, DocSection, CodeBlock, Footer
+## Guides and Documentation
 
-Perfect for technical documentation, guides, and API references.
+[Developer Guides](./guides/developers/) — Building foundations and components, converting designs, component patterns, theming contexts
 
-### International
+[Content Author Guides](./guides/authors/) — Writing pages in markdown, writing dynamic content, site setup, theming, recipes
 
-[**Live Demo**](https://uniweb.github.io/templates/international/) · `pnpm create uniweb my-site --template international`
+[Reference Docs](./docs/) — Full reference for all configuration, commands, and framework
 
-**Includes:** Hero, Features, Team, CTA, Header (with language switcher), Footer (with language links)
+### Quick Reference
 
-**Languages:** English (default), Spanish, French
+| Topic              | Guide                                                               |
+| ------------------ | ------------------------------------------------------------------- |
+| Content Structure  | [How markdown becomes component props](./docs/content-structure.md) |
+| Component Metadata | [The meta.js schema](./docs/component-metadata.md)                  |
+| Site Configuration | [site.yml reference](./docs/site-configuration.md)                  |
+| CLI Commands       | [create, build, docs, i18n](./docs/cli-commands.md)                 |
+| Templates          | [Built-in, official, and external templates](./docs/templates.md)   |
+| Deployment         | [Vercel, Netlify, Cloudflare, and more](./docs/deployment.md)       |
 
-A multilingual business site demonstrating Uniweb's i18n capabilities. Includes pre-configured translation files and a complete localization workflow:
-
-```bash
-uniweb i18n extract   # Extract translatable strings
-uniweb i18n status    # Check translation coverage
-uniweb build          # Generates dist/es/, dist/fr/
-```
-
-Perfect for international businesses and learning the i18n workflow.
-
-## External Templates
-
-Use templates from npm or GitHub:
-
-```bash
-# npm package
-pnpm create uniweb my-site --template @myorg/template-name
-
-# GitHub repository
-pnpm create uniweb my-site --template github:user/repo
-
-# GitHub with specific branch/tag
-pnpm create uniweb my-site --template github:user/repo#v1.0.0
-```
-
-## Dependency Management
-
-Each package manages its own dependencies:
-
-**`site/package.json`:**
-
-- `@uniweb/runtime`
-- `@my-project/foundation` (workspace link)
-- Vite, Tailwind (dev)
-
-**`foundation/package.json`:**
-
-- Component libraries (carousel, icons, etc.)
-- React as peer dependency
-
-```bash
-# Add component dependency
-cd foundation && pnpm add embla-carousel
-
-# Site references foundation via workspace
-# No path gymnastics needed
-```
+---
 
 ## Configuration
 
@@ -542,30 +300,7 @@ export default defineFoundationConfig({
 })
 ```
 
-## Foundation Build Process
-
-When you run `uniweb build` on a foundation:
-
-1. **Discovers** components from `src/components/*/meta.js`
-2. **Generates** entry point (`_entry.generated.js`)
-3. **Runs** Vite build
-4. **Processes** preview images (converts to WebP)
-5. **Generates** `schema.json` with full metadata
-
-**Output:**
-
-```
-dist/
-├── foundation.js       # Bundled components
-├── foundation.js.map   # Source map
-├── schema.json         # Component metadata
-└── assets/
-    ├── style.css       # Compiled CSS
-    └── [Component]/    # Preview images
-        └── [preset].webp
-```
-
-## Workspace Configuration
+### Workspace Configuration
 
 Both templates use the same unified workspace configuration:
 
@@ -588,25 +323,6 @@ Also set in `package.json` for npm compatibility.
 
 This means no config changes when evolving from single to multi-site.
 
-## Releasing a Foundation
-
-Publish your foundation to npm:
-
-```bash
-cd foundation
-npm publish
-```
-
-Or to [uniweb.app](https://uniweb.app) for use with platform-managed sites:
-
-```bash
-uniweb login          # First time only
-uniweb build
-uniweb publish
-```
-
-Sites control their own update strategy—automatic, minor-only, patch-only, or pinned to a specific version.
-
 ## FAQ
 
 **How is this different from MDX?**
@@ -623,7 +339,7 @@ No. Local markdown files work great for developer-managed sites. The platform ad
 
 **Can I use an existing component library?**
 
-Yes. Foundations are standard React. Import any library into your foundation components. The `{ content, params }` interface only applies to exposed components—internal components use regular props.
+Yes. Foundations are standard React. Import any library into your foundation components. The `{ content, params }` interface only applies to section types (components with `meta.js`) — everything else uses regular React props.
 
 **Is this SEO-friendly?**
 
@@ -633,80 +349,6 @@ Yes. Content is pre-embedded in the initial HTML—no fetch waterfalls, no layou
 
 Pages can define data sources that auto-generate subroutes. A `/blog` page can have an index and a `[slug]` template that renders each post.
 
-## Common Gotchas
-
-### Homepage Configuration
-
-Set your homepage with `index:` in `site.yml`:
-
-```yaml
-# site.yml
-index: home # The page folder that becomes /
-```
-
-The `index:` option tells the build which page folder becomes the root route (`/`). The page still exists in `pages/home/`, but visitors access it at `/`.
-
-Don't confuse this with `pages:` (which explicitly lists pages and hides any not listed).
-
-### Content Shapes
-
-Lists and items in markdown become **objects**, not strings. A bullet list:
-
-```markdown
-- First item
-- Second item
-```
-
-Becomes:
-
-```js
-content.items = [
-  { title: 'First item', paragraphs: [], links: [], imgs: [] },
-  { title: 'Second item', paragraphs: [], links: [], imgs: [] },
-]
-```
-
-Each item has the same structure as a content block. See [Content Structure](./docs/content-structure.md) for the full shape.
-
-### Tagged Data Blocks
-
-Tagged code blocks like:
-
-````markdown
-```yaml:team-member
-name: Sarah Chen
-role: Lead Architect
-```
-````
-
-Are accessible via `content.data`:
-
-```jsx
-function TeamMember({ content }) {
-  const member = content.data['team-member']
-  return (
-    <div>
-      {member.name} - {member.role}
-    </div>
-  )
-}
-```
-
-The tag name (after the colon) becomes the key in `content.data`.
-
-### Root vs Package Commands
-
-In a Uniweb workspace, commands run differently at different levels:
-
-| Location      | Command        | What it does                            |
-| ------------- | -------------- | --------------------------------------- |
-| Project root  | `pnpm build`   | Builds all packages (foundation + site) |
-| Project root  | `pnpm dev`     | Starts dev server for site              |
-| `foundation/` | `uniweb build` | Builds just the foundation              |
-| `site/`       | `uniweb build` | Builds just the site                    |
-
-For day-to-day development, run `pnpm dev` from the project root. The workspace scripts handle the rest.
-
 ## Related Packages
 
 - [`@uniweb/build`](https://github.com/uniweb/build) — Foundation build tooling

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.5.14",
+  "version": "0.6.0",
   "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.4.9",
-    "@uniweb/runtime": "0.5.11",
+    "@uniweb/build": "0.5.0",
     "@uniweb/core": "0.3.10",
-    "@uniweb/kit": "0.4.11"
+    "@uniweb/kit": "0.4.11",
+    "@uniweb/runtime": "0.5.11"
   }
 }

package/partials/agents-md.hbs

@@ -1,6 +1,6 @@
 # AGENTS.md
 
-Guidance for AI agents working with this Uniweb project. For deeper reference, see the [developer guides](./guides/developers/) and [content author guides](./guides/authors/).
+Guidance for AI agents working with this Uniweb project.
 
 ## Project Structure
 
@@ -13,8 +13,8 @@ project/
 
 Multi-site variant uses `foundations/` and `sites/` (plural) folders.
 
-- **Foundation**: React components. Those with `meta.js` are *exposed* — selectable by content authors via `type:` in frontmatter.
-- **Site**: Markdown content + configuration. Each section file references an exposed component.
+- **Foundation**: React components. Those with `meta.js` are *section types* — selectable by content authors via `type:` in frontmatter. Everything else is ordinary React.
+- **Site**: Markdown content + configuration. Each section file references a section type.
 
 ## Commands
 
@@ -212,7 +212,7 @@ theme: dark           ← sets context-dark, all tokens resolve to dark values
 
 **Site controls the palette** in `theme.yml`. The same foundation looks different across sites because tokens resolve from the site's color configuration, not from component code.
 
-**When to break the rules:** Header/footer components that float over content may need direct color logic (reading the first section's theme). Decorative elements with fixed branding (logos) use literal colors. See the [Thinking in Contexts](./guides/developers/thinking-in-contexts.md) guide.
+**When to break the rules:** Header/footer components that float over content may need direct color logic (reading the first section's theme). Decorative elements with fixed branding (logos) use literal colors.
 
 ## Component Development
 
@@ -277,24 +277,25 @@ All defaults belong in `meta.js`, not inline in component code.
 
 **Utilities:** `cn()` (Tailwind class merge), `filterSocialLinks(links)`, `getSocialPlatform(url)`
 
-### Component Organization
+### Foundation Organization
 
 ```
 foundation/src/
-├── components/          # Exposed (auto-discovered via meta.js)
+├── sections/            # Section types (auto-discovered via meta.js)
 │   ├── Hero/
-│   │   ├── index.jsx
+│   │   ├── Hero.jsx     # Entry — or index.jsx, both work
 │   │   └── meta.js
 │   └── Features/
-│       ├── index.jsx
+│       ├── Features.jsx
 │       └── meta.js
-├── shared/              # Internal helpers (no meta.js, not selectable)
-│   ├── Button.jsx
+├── components/          # Your React components (no meta.js, not selectable)
+│   ├── ui/              # shadcn-compatible primitives
+│   │   └── button.jsx
 │   └── Card.jsx
 └── styles.css
 ```
 
-Components without `meta.js` are internal — imported by exposed components but invisible to content authors.
+Only folders with `meta.js` in `sections/` (or `components/` for older foundations) become section types. Everything else is ordinary React — organize however you like.
 
 ### Website and Page APIs
 
@@ -325,7 +326,7 @@ const firstBody = block.page.getFirstBodyBlockInfo()
 
 ### Custom Layouts
 
-Export a Layout from `foundation/src/exports.js`. Kit provides `SidebarLayout` for sidebar-based sites (docs, dashboards):
+Export a Layout from `foundation/src/foundation.js`. Kit provides `SidebarLayout` for sidebar-based sites (docs, dashboards):
 
 ```jsx
 import { SidebarLayout } from '@uniweb/kit/styled'
@@ -341,9 +342,9 @@ When given a monolithic React file (AI-generated or hand-built), don't port line
 1. **Name by purpose** — `Institutions` → `Testimonial`, `WorkModes` → `FeatureColumns`. Components render a *kind* of content, not specific content.
 2. **Separate content from code** — Hardcoded strings → markdown. Layout/styling stays in JSX. Content authors edit words without touching code.
 3. **Use semantic tokens** — Replace `text-slate-900` with `text-heading`, `bg-white` with `bg-surface`. Component works in any context and any brand.
-4. **Shared UI → `shared/`** — Buttons, badges, cards become internal components (no `meta.js`).
+4. **UI components → `components/`** — Buttons, badges, cards go in `src/components/` (no `meta.js` needed).
 
-You don't have to convert everything at once. Each section is independent — one can use hardcoded content while another reads from markdown. See the [Converting Existing Designs](./guides/developers/converting-existing-designs.md) guide for the full walkthrough.
+You don't have to convert everything at once. Each section is independent — one can use hardcoded content while another reads from markdown.
 
 ## Tailwind CSS v4
 
@@ -351,7 +352,7 @@ Theme defined in `foundation/src/styles.css`:
 
 ```css
 @import "tailwindcss";
-@source "./components/**/*.{js,jsx}";
+@source "./sections/**/*.{js,jsx}";
 @source "../node_modules/@uniweb/kit/src/**/*.jsx";
 
 @theme {

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

@@ -9,7 +9,7 @@
  * Identity (name, version, description) comes from package.json.
  */
 
-// import Layout from './components/Layout'
+// import Layout from './sections/Layout'
 
 /**
  * CSS custom properties that sites can override in theme.yml

package/templates/multi/foundations/default/src/styles.css

@@ -1,6 +1,6 @@
 @import "tailwindcss";
 
-@source "./components/**/*.{js,jsx}";
+@source "./sections/**/*.{js,jsx}";
 @source "../node_modules/@uniweb/kit/src/**/*.{js,jsx}";
 
 @theme {

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

@@ -9,7 +9,7 @@
  * Identity (name, version, description) comes from package.json.
  */
 
-// import Layout from './components/Layout'
+// import Layout from './sections/Layout'
 
 /**
  * CSS custom properties that sites can override in theme.yml

package/templates/single/foundation/src/styles.css

@@ -1,6 +1,6 @@
 @import "tailwindcss";
 
-@source "./components/**/*.{js,jsx}";
+@source "./sections/**/*.{js,jsx}";
 @source "../node_modules/@uniweb/kit/src/**/*.{js,jsx}";
 
 @theme {

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

@@ -1,14 +0,0 @@
-// 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
-
-// Per-component runtime metadata (from meta.js)
-export const meta = {}

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

@@ -1,14 +0,0 @@
-// 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
-
-// Per-component runtime metadata (from meta.js)
-export const meta = {}