Define product names and conventions.

Author: koculu

.vscode/settings.json

@@ -5,30 +5,9 @@
       "url": "./packages/ts-ssg/schema/siteConfig.schema.json"
     }
   ],
-  "editor.defaultFormatter": "biomejs.biome",
-  "editor.codeActionsOnSave": {
-    "source.organizeImports.biome": "explicit"
-  },
-  "[typescript]": {
-    "editor.defaultFormatter": "biomejs.biome"
-  },
-  "[javascript]": {
-    "editor.defaultFormatter": "biomejs.biome"
-  },
-  "[json]": {
-    "editor.defaultFormatter": "biomejs.biome"
-  },
-  "dotnet.server.useOmnisharp": false,
-  "[csharp]": {
-    "editor.defaultFormatter": "ms-dotnettools.csharp",
-    "editor.codeActionsOnSave": {
-      "source.organizeImports": "explicit"
-    }
-  },
   "files.eol": "\n",
   "files.insertFinalNewline": true,
   "files.trimTrailingWhitespace": true,
-  "editor.formatOnSave": true,
   "editor.tabSize": 2,
   "editor.useTabStops": false,
   "editor.detectIndentation": false,

AGENTS.md

@@ -85,3 +85,36 @@ Do not edit generated files under `packages/ts-page-scripts/src/embed` manually.
 When page script source changes require regenerated embeds, update only the source and generator configuration, then tell the user to run the embed script manually.
 
 Use the stable TypeScript 7 `tsc` command to build and type-check TypeScript files.
+
+Product naming rule
+
+Use the following names consistently in documentation, UI copy, CLI output, and code:
+
+| Name               | Meaning                     | Command or package scope       |
+| ------------------ | --------------------------- | ------------------------------ |
+| PureStack          | The ecosystem               | —                              |
+| PureStack CLI      | The command-line tool       | `purestack`                    |
+| PureStack Forge    | PureStack's website builder | Launched with `purestack init` |
+| PureStack Packages | The framework packages      | `@purestack/*`                 |
+
+Introduce **PureStack Forge** by its full name; use **Forge** afterward when the
+context is clear. Describe it as a **website builder**. Its approved purpose
+statement is:
+
+> Build, customize, and maintain your PureStack website.
+
+`purestack init` launches Forge's interactive project creation flow. Project
+creation is one Forge workflow; the product's scope includes ongoing customization
+and maintenance. Describe available features accurately and identify planned
+capabilities as future work.
+
+Use “wizard” only to describe a guided flow. Do not use Studio, Wizard, or
+“visual workspace” as Forge's product name or description. Propose terminology
+changes to the user before adopting a different name or description.
+
+Preserve `purestack.studio`, `PureStackStudio`, and other existing addresses and
+account names. Their spelling does not define the product name.
+
+Keep branding at feature boundaries. Name internal modules, types, and components
+by their responsibility, using folders for context rather than repeating product
+names or generic prefixes such as `Website` throughout the code.

README.md

@@ -48,23 +48,24 @@ The aim is a source model that remains understandable as the product grows.
 files work for prose pages. See the [Regor guide](https://purestack.studio/guides/extending/regor/)
 for the markup and browser app model.
 
-## Get your first page running
+## Get your first site running
 
-Open PureStack Studio, the local site wizard:
+**PureStack Forge** is PureStack's website builder. Build, customize, and maintain
+your PureStack website.
 
 ```sh
 npx purestack@latest init
 ```
 
-Studio prints a link to open in your browser. Name your site, choose a template
-and its options, decide whether to install dependencies and set up Git, then
-create it. Studio shows each step, starts the live site, and stays open while
-you explore. Source edits appear on the live site automatically.
+PureStack CLI opens PureStack Forge to set up your website. Follow the link in your
+terminal, choose a template, configure plugins, and shape your project in the browser.
+Create your site and explore it live. Saved source changes appear in the preview
+as you work.
 
-Each project includes `README.md` and `AGENTS.md` to guide customization, plus
-dev, build, and publish scripts. Run `npx purestack@latest init --help` for
-options that preset Studio's choices, or that create a site without Studio in
-scripts and CI.
+Your project includes development and publishing commands, with `README.md` and
+`AGENTS.md` to guide you and your AI assistant through the source. The
+[CLI guide](https://purestack.studio/guides/getting-started/purestack-cli/) walks
+you through your first site and covers options for automated setup.
 
 To assemble a site manually instead, follow the steps below.
 

docs/site-studio.md docs/forge.mddocs/site-studio.md renamed to docs/forge.md

@@ -1,42 +1,49 @@
-# Site Studio wizard
+# PureStack Forge
 
-Run `yarn purestack init` from `sites/` to serve the wizard locally. The CLI calls
-PureStack's existing `startDevServer` with `packages/purestack/wizard` as its
+Build, customize, and maintain your PureStack website.
+
+PureStack is the ecosystem. PureStack CLI (`purestack`) is its command-line tool;
+PureStack Forge is its website builder. `purestack init` launches Forge's
+interactive project creation experience. PureStack Packages (`@purestack/*`)
+provide the reusable framework capabilities.
+
+Run `yarn purestack init` from `sites/` to serve Forge locally. The CLI calls
+PureStack's existing `startDevServer` with `packages/purestack/forge` as its
 content directory. Open the complete printed URL, including its session token.
-Studio binds to `127.0.0.1` on an available port by default. Override the wizard
+Forge binds to `127.0.0.1` on an available port by default. Override Forge's
 listener with `yarn purestack init --host 0.0.0.0 --port 4700`; `--port 0` selects
-an available port. These flags affect Studio; generated-site previews keep their
-own loopback listener and automatically assigned port. Studio and preview servers
+an available port. These flags affect Forge; generated-site previews keep their
+own loopback listener and automatically assigned port. The Forge and preview servers
 log warnings and errors while creation progress remains visible.
 
-Studio builds the complete wizard before printing its URL, then serves the
+The CLI builds the Forge app before printing its URL, then serves the
 generated site with file watching and live reload disabled. Its WebSocket
 connection remains available for configuration, creation progress, and shutdown.
 
-The wizard is ordinary PureStack content:
-- `wizard/index.mdx`: static introduction and native `RegorApp` mount.
-- `wizard/header.mdx` and `footer.mdx`: shared native `TopBar`, `ThemeToggle`,
+Forge is ordinary PureStack content:
+- `forge/index.mdx`: static introduction and native `RegorApp` mount.
+- `forge/header.mdx` and `footer.mdx`: shared native `TopBar`, `ThemeToggle`,
   and `SiteFooter`.
-- `wizard/siteConfig.json`: site settings.
-- `wizard/modules/purestack.config.ts`: plugin configuration selected by the CLI.
-- `wizard/modules/wizardPlugin.ts`: generates a branded light/dark pair through the
+- `forge/siteConfig.json`: site settings.
+- `forge/modules/purestack.config.ts`: plugin configuration selected by the CLI.
+- `forge/modules/plugin.ts`: generates a branded light/dark pair through the
   standard skin generator and registers fluent TypeScript styles.
-- `wizard/modules/skin.ts`: refines both returned palettes for surfaces, readable
+- `forge/modules/skin.ts`: refines both returned palettes for surfaces, readable
   text, borders, typography, radii, shadows, and accent interaction states.
-- `wizard/modules/styles/`: custom shell and dashboard rules using semantic palettes;
+- `forge/modules/styles/`: custom shell and dashboard rules using semantic palettes;
   ordinary layout and spacing use native components and generated utilities.
-- `wizard/modules/model.ts`: shared reactive configuration, validation, and navigation.
-- `wizard/modules/connection.ts`: native browser WebSocket transport and reconnection.
-- `wizard/modules/shared/protocol.ts`: typed commands, snapshots, progress, and results.
-- `wizard/modules/components/dashboard.ts`: dashboard layout composing the navigation
+- `forge/modules/model.ts`: shared reactive configuration, validation, and navigation.
+- `forge/modules/connection.ts`: native browser WebSocket transport and reconnection.
+- `forge/modules/shared/protocol.ts`: typed commands, snapshots, progress, and results.
+- `forge/modules/components/dashboard.ts`: dashboard layout composing the navigation
   and individual site, template, options, setup, and review steps.
-- `wizard/modules/components/`: focused, typed Regor components, including reusable
+- `forge/modules/components/`: focused, typed Regor components, including reusable
   step layouts, Back/Next actions, and template cards built from native primitives.
-- `wizard/modules/wizard.ts`: mounts the browser app with explicit component registration.
-- `src/cli/wizard/run.ts`: starts PureStack and prints the setup URL.
-- `src/cli/wizard/session.ts`: validates commands, owns creation and progress,
+- `forge/modules/app.ts`: mounts the browser app with explicit component registration.
+- `src/cli/forge/run.ts`: starts PureStack and prints the setup URL.
+- `src/cli/forge/session.ts`: validates commands, owns creation and progress,
   retains state across reconnects, and rejects duplicate creation requests.
-- `src/cli/wizard/preview.ts` and `preview-process.ts`: launch an isolated child
+- `src/cli/forge/preview.ts` and `preview-process.ts`: launch an isolated child
   process using the same CLI and PureStack server, with IPC readiness and cleanup.
 
 The Regor app connects to a WebSocket endpoint on the existing PureStack HTTP
@@ -47,16 +54,16 @@ state and task progress. Reconnecting observes the same operation without
 resubmitting creation. No third-party WebSocket library is used.
 
 After creation, **Browse live site** opens the generated project on a separate
-loopback port. A child process isolates its theme and build registries from the
-wizard; source edits are watched and reloaded by PureStack. A failed preview can
-be retried without regenerating the project. The wizard remains open until
-**Finish Studio** or Ctrl+C, which closes both servers and cleans their temporary
+loopback port. A child process isolates its theme and build registries from
+Forge; source edits are watched and reloaded by PureStack. A failed preview can
+be retried without regenerating the project. Forge remains open until
+**Finish Forge** or Ctrl+C, which closes both servers and cleans their temporary
 build directories. Generated project files are preserved. The terminal prints
 copyable commands for continuing independently.
 
 The live site uses the generated project's `dev` script (`purestack serve ...`),
 including its content directory, host, port, and watch/reload options. For example,
-`--port 5000` opens the live site on port 5000. Studio keeps its own listener and
+`--port 5000` opens the live site on port 5000. Forge keeps its own listener and
 stores preview build output in a temporary directory.
 
 ## Retained generation services
@@ -70,11 +77,11 @@ yarn purestack init my-site --template starter --set palette=mint --install --ye
 
 Template fetching, archive validation, compatibility checks, typed settings,
 project generation, optional installation/Git setup, and terminal progress and
-completion output remain independent of the wizard. See
+completion output remain independent of Forge. See
 [Project creation](template-scaffolding.md) for the package contract.
 
 Template categories, nested categories, fields, choices, defaults, and configuration
 bindings are defined by `template.ui.json` and rendered with native PureStack
-controls. CLI arguments prefill the wizard, including custom template sources and
+controls. CLI arguments prefill Forge, including custom template sources and
 `--set` values. The live site is started after creation; template-specific optional
 previews and custom template setup code remain separate future capabilities.

docs/template-scaffolding.md

@@ -7,10 +7,10 @@ code. Generated files belong to the user; templates are not project dependencies
 
 ## First release
 
-See [Site Studio](site-studio.md) for the browser wizard's PureStack content,
+See [PureStack Forge](forge.md) for its PureStack content,
 template-defined categories, configuration bindings, and extension points.
 - Official alias: `starter`.
-- `init` serves the wizard content with PureStack; `--yes` creates directly.
+- `init` serves Forge content with PureStack; `--yes` creates directly.
 - Install dependencies with the template's package manager only when `--install` is supplied or selected. The starter pins Yarn; templates without a `packageManager` field use npm.
 - For Yarn projects, installation also sets up missing Corepack and enables Yarn
   through npm's global prefix, then prepares the project's pinned Yarn version.

frontend/IMPLEMENTATION.md

@@ -1,4 +1,4 @@
-# PureStack Studio launch site
+# PureStack launch site
 
 ## Component documentation pilot
 
@@ -30,7 +30,7 @@ calls. There is no shared example contract, lookup table, or mounting helper.
 Browser verification found existing shared-framework accessibility issues:
 - The default doc template emits no `lang` for a site without locale routing.
 - Navigation and TOC header opacity gives insufficient text contrast in the
-  studio skin.
+  website skin.
 - Generated Tabs controls have `aria-selected` on buttons without tab roles;
   the original tablist contains inputs and panels, and enhanced radios refer
   to hidden labels.
@@ -93,7 +93,7 @@ line-by-line audit of every source file or generated asset.
    a closing call to explore the repository.
 
 The landing page uses MDX and typed PureStack compositions for its content,
-a registered studio skin for its identity, and typed style registrations for
+a registered site skin for its identity, and typed style registrations for
 its layout. One explicit TypeScript entry point provides progressive enhancement.
 It does not require changes to generated embeds or framework APIs.
 
@@ -121,14 +121,14 @@ Keep build output and browser tooling under ignored directories.
 
 ## Framework-native frontend
 
-- Register the studio skin before config resolution. Register custom compositions
+- Register the PureStack site skin before config resolution. Register custom compositions
   and styles in `onConfigResolved`, after the SSG initializes its DOM and builtins.
 - Use native `Grid`/`Flex` layouts and `BtnLink` actions in MDX. Compose typed
-  `StudioFeature`, `StudioPackage`, `StudioCopy`, `StudioFaq`, `StudioWorkbench`,
-  `StudioBrand`, and `StudioActivityChart` components from framework primitives.
+  `FeatureShowcase`, `PackageLink`, `CopyButton`, `FaqItem`, `SourceWorkbench`,
+  `Brand`, and `ActivityChartPreview` components from framework primitives.
 - Let component tone/variant classes own button, panel, badge, and icon-frame
   colors and states. Reuse the standard palette contract for page typography,
-  semantic colors, radii, and effects. Keep site-specific styles scoped to `.studio`.
+  semantic colors, radii, and effects. Keep site-specific styles scoped to `.landing-page`.
 - Replace the handwritten stylesheet with typed `styleBuilder` registrations,
   emitted through the existing light/dark stylesheet pipeline. Both modes use
   the dark identity. The document supplies an initial theme for no-JavaScript use.