@relu-interactives/spatial-ecs 0.5.2 → 0.8.0

package/dist/docs/guide/getting-started/editor/ai-agent.md

@@ -0,0 +1,227 @@
+# AI Agent
+
+The AI Agent is an intelligent assistant integrated into the editor that helps you build scenes, write scripts, troubleshoot issues, and automate workflows through natural language conversation.
+
+![AI Agent Panel](/images/getting-started/editor/ai-agent.png)
+
+## Opening the AI Agent
+
+The agent shows right below the inspector on the right side panel.
+
+## What the AI Agent can do
+
+### Scene Creation and Modification
+
+Ask the agent to create, modify, or organize scene content:
+
+- **"Add a directional light pointing down at 45 degrees"**
+- **"Create a row of 5 cubes spaced 2 meters apart"**
+- **"Move the camera to look at the player spawn point"**
+- **"Add physics to all meshes in the 'obstacles' folder"**
+
+The agent understands spatial relationships, entity hierarchies, and component configurations, executing changes directly in your scene.
+
+<video controls autoplay muted loop playsinline width="100%">
+  <source src="/images/getting-started/editor/agentic-ai.mp4" type="video/mp4">
+  </source>
+</video>
+
+### Script Generation and Editing
+
+Generate or modify `Behaviour` scripts:
+
+- **"Write a script that makes this cube rotate continuously"**
+- **"Add an onGrab handler that changes the material color"**
+- **"Fix the syntax error in PlayerController.ts"**
+- **"Convert this loop to use entity queries instead"**
+
+Scripts are created in your `assets/` folder and can be attached immediately or edited further.
+
+### Component Configuration
+
+Get help configuring components on selected entities:
+
+- **"Set up this model with a dynamic rigidbody"**
+- **"Configure this light as a warm spotlight with shadows"**
+- **"Make this object grabbable in VR with two-hand support"**
+
+The agent reads the current selection and applies settings contextually.
+
+### Workflow Automation
+
+Automate repetitive tasks:
+
+- **"Batch rename all entities starting with 'Prop_' to remove the prefix"**
+- **"Export all animation clips as separate files"**
+- **"Find all entities with missing material assignments"**
+- **"Create a prefab from each top-level entity in the hierarchy"**
+
+### Learning and Documentation
+
+Ask questions about the editor, components, or scripting APIs:
+
+- **"How do I make an object teleportable in VR?"**
+- **"What's the difference between physical and distance grab?"**
+- **"Show me examples of hand pose detection"**
+- **"Explain the XR Rig tracking origin options"**
+
+The agent references the official documentation and provides examples.
+
+## Using the AI Agent
+
+### Chat Interface
+
+The agent uses a conversation-based interface:
+
+1. **Type your request** in the input box at the bottom
+2. **Press Enter or click Send** to submit
+3. **Review the agent's response** - it may show code, apply changes, or ask clarifying questions
+4. **Confirm or refine** - approve proposed changes or provide additional context
+
+### Contextual Awareness
+
+The agent is aware of:
+
+- **Current selection** in the hierarchy or viewport
+- **Project type** (3D, VR, Image Tracking, etc.)
+- **Open files** and active scripts
+- **Recent actions** and undo history
+- **Available assets** in your project folder
+
+Refer to entities by name or say "this entity" / "the selected object" when you have something selected.
+
+### Approval and Safety
+
+For actions that modify your scene or scripts, the agent:
+
+- **Shows a preview** of what will change
+- **Asks for confirmation** before applying destructive operations
+- **Works with undo/redo** - you can revert agent actions
+- **Validates** generated code before creating files
+
+Turn on **Auto-approve safe actions** in settings to skip confirmations for simple tasks like renaming or adding entities.
+
+## Example Workflows
+
+### Building a VR Interaction
+
+```
+You: "Make this object grabbable with both hands"
+Agent: Adds XR Interactable component, sets hands to "two", 
+       and configures attach points. "Done! Users can now grab 
+       with both hands. Want me to add throw physics?"
+
+You: "Yes, and make it teleportable"
+Agent: Adds Physics component with dynamic rigidbody, 
+       and VR Teleport Area to the floor. "Ready to test!"
+```
+
+### Batch Asset Processing
+
+```
+You: "Import all FBX files from my Desktop and place them in a grid"
+Agent: Copies files to assets/, spawns model entities, arranges in 
+       5×5 grid with 3m spacing. "Imported 12 models."
+```
+
+### Script Debugging
+
+```
+You: "Why isn't my onGrab handler firing?"
+Agent: Checks script, finds missing XR Interactable component. 
+       "The entity needs an XR Interactable component with 
+       grabbable: true. Want me to add it?"
+
+You: "Yes"
+Agent: Adds component and validates the fix.
+```
+
+### Learning Workflow
+
+```
+You: "How do I set up teleport locomotion?"
+Agent: Explains XR Rig locomotion modes, shows code example for 
+       custom teleport areas, and offers to configure the current scene.
+```
+
+## Tips
+
+### Be Specific with Spatial References
+
+- **Good:** "Move the camera 5 meters behind the player entity"
+- **Unclear:** "Put the camera somewhere behind"
+
+The agent understands coordinates, directions (up/down/left/right/forward/back), and entity names.
+
+### Use Selection for Context
+
+Select the target entity before asking for modifications:
+- Select a mesh → "Add a point light above this"
+- Select multiple entities → "Parent these under a new empty"
+
+### Iterate Incrementally
+
+For complex tasks, work step-by-step:
+1. **"Create a basic VR scene"** → agent sets up rig, lighting, and floor
+2. **"Add a grabbable cube"** → agent spawns and configures it
+3. **"Make it glow when grabbed"** → agent writes the script
+
+### Ask for Explanations
+
+Prefix with "explain" or "why" to learn instead of execute:
+- **"Explain how animation state machines work"**
+- **"Why is my physics object falling through the floor?"**
+
+### Provide Examples
+
+Show code or describe behavior:
+- **"Write a script like PlayerController but for VR"**
+- **"Create an animation that's similar to the idle clip but faster"**
+
+## Settings and Preferences
+
+Configure the AI Agent behavior in **Editor → Preferences → AI Agent**:
+
+- **Model selection** - choose which AI model powers the assistant
+- **Auto-approve safe actions** - skip confirmations for non-destructive changes
+- **Context depth** - how much project history the agent considers
+- **Code style** - preferred formatting and conventions for generated scripts
+- **Verbosity** - concise responses vs. detailed explanations
+
+## Privacy and Data
+
+The AI Agent:
+
+- **Does not send scene content** to external servers unless explicitly sharing for collaboration
+- **Keeps conversation history locally** in your project folder
+- **Can be disabled** entirely if you prefer manual workflows
+- **Respects .gitignore** - won't reference or modify ignored files
+
+Check **Help → Privacy Policy** for full details on data handling.
+
+## Limitations
+
+The AI Agent is a powerful assistant but has boundaries:
+
+- **Cannot undo destructive file operations** - deleting assets is permanent
+- **May hallucinate APIs** - always verify generated code against the [Component Catalog](../../component-catalog)
+- **Context window limits** - very large scenes may require breaking requests into smaller tasks
+- **No runtime execution** - the agent modifies the editor, not the running preview
+
+When in doubt, review proposed changes before confirming.
+
+## Keyboard Shortcuts
+
+| Action | Shortcut |
+|--------|----------|
+| Open/Close AI Agent | Configurable (default: depends on OS) |
+| Send message | `Enter` |
+| New line in message | `Shift + Enter` |
+<!-- | Clear conversation | `Cmd/Ctrl + K` |
+| Regenerate last response | `Cmd/Ctrl + R` | -->
+
+## Related
+
+- [Custom Behaviours](../../authoring-a-behaviour) - scripting with the agent's help
+- [Component Catalog](../../component-catalog) - reference for agent-generated configurations
+- [Toolbar](./toolbar) - where the AI Agent toggle lives

package/dist/docs/guide/getting-started/editor/hierarchy.md

@@ -20,7 +20,7 @@ Each row represents one entity:
 
 ## Searching
 
-The search box above the tree filters rows by name. It searches the displayed name only — not component values.
+The search box above the tree filters rows by name. It searches the displayed name only not component values.
 
 ## Adding entities
 
@@ -35,7 +35,7 @@ Drag a row onto another row to **re-parent** it. The dragged entity becomes a ch
 - Drop on **empty space** → re-parent to the scene root.
 
 > [!IMPORTANT]
-> Some entities — for example image-target anchors — control their own children. Re-parenting them across different anchor groups can change runtime behavior. See the [Component Catalog](../../component-catalog) for component-specific notes.
+> Some entities, for example image-target anchors control their own children. Re-parenting them across different anchor groups can change runtime behavior. See the [Component Catalog](../../component-catalog) for component-specific notes.
 
 ## Renaming
 

package/dist/docs/guide/getting-started/editor/index.md

@@ -7,10 +7,11 @@ The editor window is divided into a handful of regions. Each one has a dedicated
 | Region | Purpose |
 | --- | --- |
 | [Hierarchy](./hierarchy) | The scene tree. Add, select, parent, and reorder entities. |
-| [Toolbar](./toolbar) | Global actions — settings, transform tools, save, preview, publish. |
+| [Toolbar](./toolbar) | Global actions settings, save, preview, publish. |
 | [Viewport](./viewport) | The 3D scene view. Click to select, drag gizmos to transform. |
 | [Inspector](./inspector) | Edit components on the selected entity. |
 | [Assets Browser](./assets-browser) | Files in your project's `assets/` folder. Drag into the scene to add. |
+| [AI Agent](./ai-agent) | AI-powered assistant for scene creation, scripting, and workflow automation. |
 <!-- | [Modules](./modules) | Optional per-project-type module panels. | -->
 
-Read these in any order — most pages are short and focused on one region.
+Read these in any order, most pages are short and focused on one region.

package/dist/docs/guide/getting-started/editor/inspector.md

@@ -4,14 +4,14 @@ The inspector (right panel) is where you edit the **components** of whatever is
 
 ![Inspector](/images/getting-started/editor/inspector.png)
 
-## Two top-level tabs
+<!-- ## Two top-level tabs
 
 At the top of the inspector are two tabs:
 
 | Tab | Shows |
 | --- | --- |
 | **Object** | Components of the entity currently selected in the [hierarchy](./hierarchy). When nothing is selected, the tab is empty. |
-| **Scene** | Scene wide singletons like skybox, fog, gravity, postprocessing. See [Scene → Environment](../../scene/environment) and [Scene → Postprocessing](../../scene/postprocessing). |
+| **Scene** | Scene wide singletons like skybox, fog, gravity, postprocessing. See [Scene → Environment](../../scene/environment) and [Scene → Postprocessing](../../scene/postprocessing). | -->
 
 ## Component panels
 

package/dist/docs/guide/getting-started/editor/scene-inspector.md

@@ -1,12 +1,12 @@
 # Scene Inspector
 
-The **Scene** tab in the inspector panel exposes scene wide singleton components settings that apply globally to the entire project rather than to a specific entity.
+The **Scene** configs in the inspector panel exposes scene wide singleton components settings that apply globally to the entire project rather than to a specific entity.
 
 ## Opening the Scene tab
 
-Click the **Scene** tab at the top of the inspector (right panel). The Object tab shows the selected entity's components; the Scene tab always shows the same global settings regardless of selection.
+Deselect any selected object in the scene and the **Scene** config will show in the inspector (right panel). When an Object is selected it shows the selected entity's components; the Scene config shows the global settings when no object is selected in the scene.
 
-![Scene Inspector](/images/getting-started/editor/scene-inspector.gif)
+![Scene Inspector](/images/getting-started/editor/scene-inspector.png)
 
 ## Sections
 

package/dist/docs/guide/getting-started/editor/toolbar.md

@@ -4,34 +4,34 @@ The toolbar is the global header at the top of the editor window. It groups proj
 
 ![Toolbar with Settings, Report, transform tools, preview, save and publish.](/images/getting-started/editor/toolbar.png)
 
-## Left group — project
+## Left group
 
 | Control | Action |
 | --- | --- |
-| ![Logo](/images/getting-started/editor/toolbar/logo.png) | Relu Spatial logo. Clicking this returns to the project dashboard. |
-| ![Shortcuts](/images/getting-started/editor/toolbar/shortcuts.png) | Opens the shortcuts modal (shows various keyboard shortcuts). |
-| ![Report](/images/getting-started/editor/toolbar/report.png) | Opens the in-app issue reporter. |
+| ![Home](/images/getting-started/editor/toolbar/home.png) | Clicking this returns to the project dashboard. |
+<!-- | ![Shortcuts](/images/getting-started/editor/toolbar/shortcuts.png) | Opens the shortcuts modal (shows various keyboard shortcuts). |
+| ![Report](/images/getting-started/editor/toolbar/report.png) | Opens the in-app issue reporter. | -->
 
-## Center group — scene & preview
+## Center group
 
 | Control | Action |
 | --- | --- |
-| ![Transform tools](/images/getting-started/editor/toolbar/transform-tools.png) | Active manipulation mode (move / rotate / scale). Mirrors the gizmo shown on the selected entity. |
 | ![Add object](/images/getting-started/editor/toolbar/add-object.png) | Adds a new entity to the scene (cube, sphere, plane, light, camera, etc.). |
-| ![Preview](/images/getting-started/editor/toolbar/preview.png) | Launches the **preview runtime** in a separate window using the current saved snapshot. |
+| ![Preview](/images/getting-started/editor/toolbar/preview.png) | Launches a **preview** of your experience in a separate browser window using the current saved snapshot. |
+<!-- | ![Transform tools](/images/getting-started/editor/toolbar/transform-tools.png) | Active manipulation mode (move / rotate / scale). Mirrors the gizmo shown on the selected entity. | -->
 
-## Right group — history & publishing
+## Right group
 
 | Control | Action |
 | --- | --- |
 | ![Undo](/images/getting-started/editor/toolbar/undo.png) | Reverts the last scene-affecting action. Bound to `Cmd/Ctrl + Z`. |
 | ![Redo](/images/getting-started/editor/toolbar/redo.png) | Re-applies the last undone action. Bound to `Cmd/Ctrl + Shift + Z`. |
 | ![Save](/images/getting-started/editor/toolbar/save.png) | Writes the current scene to disk. Bound to `Cmd/Ctrl + S`. |
-| ![Publish](/images/getting-started/editor/toolbar/publish.png) | Uploads the project to Relu and makes it shareable. |
-| ![Help](/images/getting-started/editor/toolbar/help.png) | Opens the in-app tour and links to this documentation. |
+| ![Publish](/images/getting-started/editor/toolbar/publish.png) | Uploads the project to Relu Spatial cloud and makes it shareable. |
+| ![User Avatar](/images/getting-started/editor/toolbar/avatar.png) | Opens the global project settings menu. |
 
 > [!TIP]
-> Save and Publish are independent. You always need to **save** before previewing or publishing — preview/publish read the on-disk snapshot, not the in-memory state.
+> Save and Publish are independent. You always need to **save** before previewing or publishing, preview/publish read the on-disk snapshot, not the in-memory state.
 
 ## Related
 

package/dist/docs/guide/getting-started/editor/viewport.md

@@ -8,10 +8,11 @@ The viewport is the central live 3D view of your scene. You navigate the editor
 
 | Input | Action |
 | --- | --- |
-| **Left mouse drag** | Orbit (look around). |
-| **Shift + Left mouse drag** | Pan. |
+| **`Alt / Option + Left mouse drag`** | Orbit (look around). |
+| **`Shift + Alt / Option + Left mouse drag`** | Pan. |
 | **Mouse wheel** | Zoom in / out. |
 | **`F`** | Focus on the selected entity. |
+| **`Shift + F`** | Frame and focus on the selected entity. |
 
 The bottom-left **axis gizmo** shows the current orientation of the editor camera. Click an axis to snap the view to that direction.
 
@@ -23,15 +24,22 @@ The bottom-left **axis gizmo** shows the current orientation of the editor camer
 
 ## Transform gizmos
 
-When an entity is selected, a gizmo appears at its origin. Switch the active mode from the [top bar](./toolbar) or with the keyboard:
+When an entity is selected, a gizmo appears at its origin. Switch the active mode from the transform mode controls on the top right of the viewport or with the keyboard:
+
+![Transform Controls](/images/getting-started/editor/tranform-controls.gif)
 
 | Key | Mode |
 | --- | --- |
-| **`W`** | Move (translate) — _disabled while flying with right mouse held._ |
-| **`E`** | Rotate. |
-| **`R`** | Scale. |
+| **`q`** | All transform modes |
+| **`w`** | Ground mode (_moves objects on the ground plane_). |
+| **`e`** | Front mode (_moves objects on the front plane_). |
+| **`r`** | Side mode (_moves objects on the side plane_). |
+
+
+
+Drag a colored arrow / ring / handle to constrain the operation to that axis. Hold **`Shift`** while dragging to enable snapping or in any of the plane mode drag an object on that plane.
 
-Drag a colored arrow / ring / handle to constrain the operation to that axis. Hold **`Shift`** while dragging to enable snapping.
+![Transform Gizmo](/images/getting-started/editor/transform-gizmo.gif)
 
 <!-- ## Editor-only helpers
 
@@ -39,5 +47,5 @@ Some helpers are visible only while editing — wireframe colliders, light cones
 
 ## Related
 
-- [Top bar](./toolbar) — transform tool buttons.
-- [Keyboard shortcuts](../shortcuts) — the full list.
+- [Toolbar](./toolbar) - transform tool buttons.
+- [Keyboard shortcuts](../shortcuts) - the full list.

package/dist/docs/guide/getting-started/index.md

@@ -1,6 +1,6 @@
 # Introduction
 
-**Relu Spatial** is a desktop first 3D editor and runtime for building interactive AR / VR / spatial experiences. It combines a visual scene editor with a TypeScript scripting API powered by an entity component system (ECS) runtime, so you can author scenes visually and drive them with code that runs the same way in preview and in production.
+**Relu Spatial** is a desktop first 3D editor and runtime for building interactive web3d and webxr spatial experiences. It combines a visual scene editor with a TypeScript scripting API powered by an entity component system (ECS) runtime, so you can author scenes visually and drive them with code that runs the same way in preview and in production.
 
 You compose scenes from entities, meshes, lights, cameras, image targets, and custom prefabs and you bring them to life with `Behaviour` scripts that read input, query the world, and mutate components every frame.
 

package/dist/docs/guide/getting-started/installation.md

@@ -6,7 +6,7 @@ The Relu Spatial editor is distributed as a desktop application for macOS, Windo
 
 Get the latest installer from the official downloads page:
 
-[**reluspatial.com/downloads**](https://reluspatial.com/downloads)
+[**reluspatial.com/editor**](https://reluspatial.com/editor)
 
 ![Download Page Image](/images/getting-started/installation/download-page.png)
 

package/dist/docs/guide/getting-started/preview-and-test.md

@@ -4,7 +4,7 @@ The editor ships with a runtime preview so you can test your scene without leavi
 
 ## Starting a preview
 
-Click the **Preview** button in the [toolbar](./editor/toolbar). The editor saves the current scene, spins up a local runtime server, and opens a preview window.
+Click the **Preview** button in the [toolbar](./editor/toolbar). The editor spins up a local runtime server, and opens a preview window.
 
 ![Previewing scene](/images/getting-started/preview-and-test/preview.gif)
 
@@ -33,8 +33,8 @@ Preview is **not** a live link to the editor. To see changes:
 
 For project types that need real device sensors (image tracking, face tracking, AR, VR) the desktop preview only goes so far. Use these strategies:
 
-- **Image / face tracking:** desktop preview can use your laptop camera. For phone camera quality, publish a draft build and open it on the target device.
-- **WebXR (AR / VR):** publish a draft and open it on a headset or AR capable phone over your local network or via a tunnel like [ngrok](https://ngrok.com).
+- **Image / Face tracking:** desktop preview can use your laptop camera. For phone camera quality, connect your phone to the same wifi network as your laptop and scan the qrcode to open it on the target device.
+- **WebXR (AR / VR):** preview and open it on a headset or AR capable phone over your local network just like described for __Image / Face tracking__ projects described above.
 
 ## Common preview issues
 
@@ -49,7 +49,7 @@ For project types that need real device sensors (image tracking, face tracking,
 
 You're done with **Getting Started**. Continue with:
 
-- [Concepts](../concepts) — how the ECS runtime is organized.
-- [Custom Behaviours](../authoring-a-behaviour) — write scripts.
-- [Component Catalog](../component-catalog) — full component reference.
-- [World API](../world-api) — query and mutate the runtime from scripts.
+- [Concepts](../concepts) - how the ECS runtime is organized.
+- [Custom Behaviours](../authoring-a-behaviour) - write scripts.
+- [Component Catalog](../component-catalog) - full component reference.
+- [World API](../world-api) - query and mutate the runtime from scripts.

package/dist/docs/guide/getting-started/project-types/image-tracking.md

@@ -13,30 +13,42 @@ Use this for posters, business cards, product packaging, museum exhibits, and an
 When you open an image-tracking project, the editor changes in three ways:
 
 1. **Image targets are first-class entities** in the hierarchy. Each anchor represents one image and contains the children that should appear when that image is detected.
-2. **A floating Compile Targets button** appears in the viewport overlay. It opens the **image compilation modal** which packages your image targets into a binary the runtime can load.
-3. **The Image Targets panel** lives in the inspector when an image-target entity is selected. From there you upload reference images, set physical sizes, and preview tracking quality.
+2. **The Image Targets panel** a panel on the right side of the hierarchy view showing each image target and a button to compile new image targets. From there you upload reference images, set physical sizes, and preview tracking quality.
 
 ![Image Target Compile Modal](/images/getting-started/project-types/image-tracking/image-tracking-compile-modal.gif)
 
 ## Workflow
 
-1. **Add an Image Target entity** from the toolbar `+` menu (or hierarchy panel). The editor creates an image-target anchor at the scene root.
-2. **Select the anchor** and use the **Image Targets panel** in the inspector to upload one or more reference images. For each, set its real-world physical width.
-3. **Add child entities** under the anchor. Anything you parent to it becomes visible only when that image is detected.
-4. **Compile targets** — click the floating **Compile Targets** button in the viewport. The compilation modal runs through tracker quality analysis and writes the compiled binary into `bin/targets/`.
-5. **Preview** — press the preview button. The runtime loads the compiled targets and starts the device camera.
+1. **Add an Image Target entity** from the image targets panel click `Add Image Targets` button. 
+2. **Drag or pick tracking images** and click the compile button to compile image targets.
+3. In the **Image Targets panel** select an image target to **Add child entities** under the anchor. Anything you add in the scene when that image target is selected becomes visible only when that image is detected.
+4. **Preview** - press the preview button. The runtime loads the compiled targets and starts the device camera.
 
 ![Image Target Panel](/images/getting-started/project-types/image-tracking/image-tracking-panel.gif)
 
 
 ## Tips
 
-- High-contrast, feature-rich images track best. Photos of faces, gradients, and large flat colors are weak targets.
-- Keep the **physical size** field accurate — this is what the runtime uses to scale your 3D content to the printed image.
+### Choosing Good Image Targets
+
+AR engines rely on distinct visual features (edges and corners) to detect and track images. **High-contrast, feature-rich images track best**, while images with the following characteristics will fail or track poorly:
+
+| Characteristic | Why It Fails | Example |
+|----------------|--------------|---------|
+| **Low Contrast & Gradients** | AR engines rely on sharp changes in pixels (edges and corners) to find feature points; gradual color gradients offer no distinct tracking anchors. | A soft pastel watercolor wash or a blurry photo. |
+| **Repetitive Patterns & Symmetry** | Repeating elements create identical feature points that confuse the algorithm, while strict symmetry prevents the engine from determining correct orientation. | Brick walls, checkerboards, or a symmetrical tribal logo. |
+| **Excessive Blank/Empty Space** | Large flat areas or empty borders contain zero feature data, forcing the tracker to rely on a restricted surface area. | A tiny corporate logo centered in the middle of a massive blank white sheet of paper. |
+| **Reflective or Glossy Finishes** | Shiny surfaces bounce ambient light and create moving glares/reflections, generating dynamic visual noise that breaks tracking. | Laminated prints under direct office lights or displaying the target on a low-luminosity phone screen. |
+
+**In summary:** avoid faces, gradients, large flat colors, repetitive patterns, excessive white space, and glossy/reflective surfaces.
+
+### Other Tips
+
+- Keep the **physical size** field accurate, this is what the runtime uses to scale your 3D content to the printed image.
 - Children of an image-target anchor inherit its transform. Position objects in **local space** relative to the anchor, not world space.
 - Recompile targets whenever you add or change reference images.
 
 ## Related
 
-- [Component Catalog → Image Target](../../component-catalog) — runtime component reference.
-- [Spawning → Image Target](../../spawning/image-target) — spawning anchors from scripts.
+- [Component Catalog → Image Target](../../component-catalog) - runtime component reference.
+- [Spawning → Image Target](../../spawning/image-target) - spawning anchors from scripts.

package/dist/docs/guide/getting-started/project-types/index.md

@@ -1,6 +1,6 @@
 # Project Types
 
-When you create a new project the editor asks for a **project type**. The type determines:
+When you create a new project you need to choose a **project type**. The type determines:
 
 - the **default scene** seeded into the project,
 - which **components and panels** are available in the inspector,
@@ -16,10 +16,10 @@ You can't change a project's type after creation, so pick the one that matches t
 | [Image Tracking](./image-tracking) | AR experiences anchored to printed images, posters, or product packaging. |
 | [3D](./3d) | Plain interactive 3D scenes, games, product viewers, configurators, embedded experiences. |
 | [Face Tracking](./face-tracking) | Face filters, avatars, and try-on experiences. *(Coming Soon)* |
-| [VR](./vr) | Fully immersive virtual reality scenes for headsets. *(Coming Soon)* |
+| [VR](./vr) | Fully immersive virtual reality scenes for headsets. |
 | [AR](./ar) | World-space augmented reality without a specific anchor. *(Coming Soon)* |
 
-![Project Types.](/images/getting-started/projects-new-dialog.png)
+![Project Types.](/images/getting-started/projects-list.png)
 
 > [!TIP]
-> If you're not sure, start with **3D** — it has the simplest scene setup with no tracking or device requirements. You can always create a second project to try a tracking-based or immersive type.
+> If you're not sure, start with **3D**, it has the simplest scene setup with no tracking or device requirements. You can always create a second project to try a tracking-based or immersive type.