@powerhousedao/academy 2.5.0-dev.4 → 2.5.0-dev.40

package/docs/academy/02-MasteryTrack/05-Launch/03-SetupEnvironment.md

@@ -1,62 +1,23 @@
-# Powerhouse Setup Guide (WIP)
+# Powerhouse Setup Guide
 
 ## Introduction
-Powerhouse is a powerful platform that helps you manage and deploy your applications efficiently. This guide will walk you through the process of setting up both the Powerhouse CLI and configuring your server machine to run Powerhouse services. Whether you're setting up a development environment or preparing for production deployment, this guide provides all the necessary steps and considerations.
+Powerhouse is a powerful platform that helps you manage and deploy your applications efficiently.   
+This guide will walk you through the process of setting up both the Powerhouse CLI and configuring your server machine to run Powerhouse services. Whether you're setting up a development environment or preparing for production deployment, this guide provides all the necessary steps and considerations.
 
 ## Prerequisites
-Before you begin, ensure you have a Linux-based system (Ubuntu or Debian recommended), sudo privileges, and a stable internet connection. These are essential for the installation and configuration process. The system should have at least 1GB of RAM and 10GB of free disk space for optimal performance. While these are minimum requirements, more resources will provide better performance, especially when running multiple services.
+Before you begin, ensure you have a Linux-based system (Ubuntu or Debian recommended), sudo privileges, and a stable internet connection.   
+These are essential for the installation and configuration process. 
+The system should have at least 1GB of RAM and 10GB of free disk space for optimal performance. 
+While these are minimum requirements, more resources will provide better performance, especially when running multiple services.
 
-## 1. Setting up a new cloud environment
-
-The `install` script provides a streamlined way to install the Powerhouse CLI tool and all its necessary dependencies. This script handles the installation of node.js 22, pnpm, Powerhouse CLI itself and the services. It's designed to work across different Linux distributions, though it's optimized for Ubuntu and Debian-based systems. It also prepares your machine for running Powerhouse services. It handles everything from package installation to service configuration, making the setup process straightforward and automated. This script is particularly useful for setting up new servers or reconfiguring existing ones.
-
-
-### Installation Steps:
-1. Run the setup script:
-```bash
-curl -fsSL https://apps.powerhouse.io/install | bash # for macOS, Linux, and WSL
-```
-
-2. After installation, source your shell configuration:
-```bash
-source ~/.bashrc  # or source ~/.zshrc if using zsh
-```
-
-3. Verify the installation:
-```bash
-ph --version
-```
-
-4. You will see ph-cli is not yet installed. But it will get installed automatically in the next step. 
-If you are a builder that wants to make use of the dev releases use `ph use dev` before going to the next step. 
-   - `ph use dev`: Development version - Use this for testing new features or development work
-   - `ph use staging`: Staging version - Use this for pre-production testing
-
-5. Follow the interactive prompts:
-
-### Step 1: Package Installation
-During the package installation phase, you'll be prompted to enter package names that you want to install. For example, you might want to install `@powerhousedao/todo-demo-package` or other Powerhouse packages. This step is crucial for adding the specific functionality you need to your Powerhouse installation. You can press Enter to skip this step if you don't need to install any packages immediately, but you can always install packages later using the `ph install` command.
-
-### Step 2: Database Configuration
-The script offers two options for database configuration. 
-
-**Option 1:** Sets up a local PostgreSQL database, which is ideal for development or small deployments. It automatically creates a database user with a secure random password and configures the database to accept local connections. This option is perfect for getting started quickly or for development environments. 
-
-**Option 2:** Allows you to connect to a remote PostgreSQL database by providing a connection URL in the format `postgres://user:password@host:port/db`. This is recommended for production environments where you might want to use a managed database service or a dedicated database server.
-
-### Step 3: SSL Configuration
-For SSL configuration, you have two choices. 
-
-**Option 1:** The **Let's Encrypt** option is recommended for production environments. It requires you to provide a base domain (like `powerhouse.xyz`) and optional subdomains for your services. The script will automatically obtain and configure SSL certificates for your domains, ensuring secure communication between your services and clients. 
-
-**Option 2:** The self-signed certificate option is suitable for development or testing environments. It uses your machine's hostname and generates a self-signed certificate, configuring the services with appropriate base paths. While this option is convenient for development, browsers will show security warnings, which is why it's not recommended for production use.
+Also make sure you have your preferred domain registered and created subdomains for your Connect & Switchboard instances.
 
 <details>
-<summary>Setting up a domain in DigitalOcean</summary>
+<summary>**Setting up a Droplet (Digital Ocean) instance and connecting your domain**</summary>
 
 This tutorial will guide you through the process of creating a new virtual private server (called a "Droplet") on DigitalOcean and then pointing your custom domain name to it. This will allow users to access your server using a memorable URL like `www.yourdomain.com`.
 
-**Current Date:** May 15, 2025
+**Current Date:** May 15, 2024
 
 ## Part 1: Setting Up Your DigitalOcean Droplet
 
@@ -156,6 +117,18 @@ Now your Droplet is running! Now you can continue with the Powerhouse tutorial o
      - **WILL DIRECT TO:** Your Droplet's IP
      - **TTL:** 3600
 
+   - **Connect Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** connect
+     - **WILL DIRECT TO:** Your Droplet's IP
+     - **TTL:** 3600
+
+   - **Switchboard Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** switchboard
+     - **WILL DIRECT TO:** Your Droplet's IP
+     - **TTL:** 3600
+
 #### Option B: Using Your Existing Nameservers (NS locked)
 
 1. **Just Create DNS Records at Your Registrar:**
@@ -171,6 +144,18 @@ Now your Droplet is running! Now you can continue with the Powerhouse tutorial o
      - **VALUE:** Your Droplet's IP
      - **TTL:** 3600
 
+   - **Connect Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** connect
+     - **VALUE:** Your Droplet's IP
+     - **TTL:** 3600
+
+   - **Switchboard Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** switchboard
+     - **VALUE:** Your Droplet's IP
+     - **TTL:** 3600
+
 **Note:** DNS changes may take up to 48 hours to propagate globally.
 
 ### Verify Configuration
@@ -179,20 +164,43 @@ Now your Droplet is running! Now you can continue with the Powerhouse tutorial o
    ```bash
    dig +short yourdomain.com
    dig +short www.yourdomain.com
+   dig +short connect.yourdomain.com
+   dig +short switchboard.yourdomain.com
    ```
 
-2. Both should return your Droplet's IP address
+2. All should return your Droplet's IP address
 
 **Congratulations!** You have successfully set up your DigitalOcean Droplet and configured your domain. Your server is now ready to host your Powerhouse services.
 
 </details>
 
 <details>
-<summary>Setting up a domain with AWS EC2</summary>
+<summary> **Setting up an EC2 instance and connecting your domain** </summary>
 
 This tutorial will guide you through the process of assigning a static IP (Elastic IP) to your EC2 instance and configuring your domain to point to it.
 
-**Current Date:** May 15, 2025
+**Current Date:** May 15, 2024
+
+   - Make sure your region is set to eu-west-1 (Ireland)
+   - Name your instance something like `cloud-server` or your project's name
+   - Select Ubuntu 24.04 LTS
+   - Architecture 64-bit (x86)
+   - Scroll down to Instance type and select t2.medium (recommended)
+      - 2 vCPUs and 4 GiB of memory are the recommended minimum specs
+      - For larger projects or higher load, consider t2.large or t2.xlarge
+   - Create a new key pair and save it in a secure location from which you can connect to your instance with the SSH client later.
+   - Configure the security group to allow inbound traffic:
+      - SSH (Port 22) from your IP address
+      - HTTP (Port 80) from anywhere
+      - HTTPS (Port 443) from anywhere
+      - Custom TCP (Port 8442) for Connect
+      - Custom TCP (Port 8441) for Switchboard
+   - **Launch the instance**
+
+   :::warning
+   Make sure to keep your key pair file (.pem) secure and never share it. Without it, you won't be able to access your instance. Also, consider setting up AWS IAM roles and policies for better security management.
+   :::
+
 
 ## Part 1: Assigning a Static IP to EC2 Instance
 
@@ -247,6 +255,18 @@ This tutorial will guide you through the process of assigning a static IP (Elast
      - **VALUE:** Your Elastic IP
      - **TTL:** 3600
 
+   - **Connect Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** connect
+     - **VALUE:** Your Elastic IP
+     - **TTL:** 3600
+
+   - **Switchboard Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** switchboard
+     - **VALUE:** Your Elastic IP
+     - **TTL:** 3600
+
 ### Option B: Using Your Existing Nameservers
 
 1. **Create DNS Records at Your Registrar:**
@@ -262,6 +282,18 @@ This tutorial will guide you through the process of assigning a static IP (Elast
      - **VALUE:** Your Elastic IP
      - **TTL:** 3600
 
+   - **Connect Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** connect
+     - **VALUE:** Your Elastic IP
+     - **TTL:** 3600
+
+   - **Switchboard Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** switchboard
+     - **VALUE:** Your Elastic IP
+     - **TTL:** 3600
+
 1. **Set Up DNS First:**
    - Create A records for all subdomains before running the setup script
    - Point them to your EC2 instance's public IP address
@@ -273,27 +305,83 @@ This tutorial will guide you through the process of assigning a static IP (Elast
    ```bash
    dig +short yourdomain.com
    dig +short www.yourdomain.com
+   dig +short connect.yourdomain.com
+   dig +short switchboard.yourdomain.com
    ```
 
-2. Both should return your Elastic IP address
+2. All should return your Elastic IP address
 
 **Congratulations!** You have successfully set up your EC2 instance with a static IP and configured your domain. Your server is now ready to host your Powerhouse services.
 
 </details>
 
-### Step 4: Service Configuration
+## 1. Setting up a new cloud environment
+
+The `install` script provides a streamlined way to install the Powerhouse CLI tool and all its necessary dependencies. This script handles the installation of Node.js 22, pnpm, and the Powerhouse CLI itself. It's designed to work across different Linux distributions, though it's optimized for Ubuntu and Debian-based systems. It also prepares your machine for running Powerhouse services. It handles everything from package installation to service configuration, making the setup process straightforward and automated. This script is particularly useful for setting up new servers or reconfiguring existing ones.
+
+### Installation
+
+1.  Run the setup script:
+    ```bash
+    curl -fsSL https://apps.powerhouse.io/install | bash # for macOS, Linux, and WSL
+    ```
+
+2.  After installation, source your shell configuration:
+    ```bash
+    source ~/.bashrc  # or source ~/.zshrc if using zsh
+    ```
+
+3.  Verify that the Powerhouse CLI is ready to be installed in the next step:
+    ```bash
+    ph --version
+    ```
+    You will see that `ph-cli` is not yet installed. This is expected, as it will be installed by the service setup command.
+
+4. Create a project with `ph-init <projectname>`. 
+
+5. After creation, move into the project with `cd <projectname>`. 
+
+Up next is the configurations of your services. 
+
+### Service Configuration
+
+Next, run `ph service setup` and follow the interactive prompts. This command installs the Powerhouse services (Connect and Switchboard) and guides you through their configuration.
+
+:::info
+**What does `ph service setup` do?**
+The script takes care of all the necessary service configuration automatically.
+It installs and configures **Nginx** as a reverse proxy, sets up SSL certificates, and configures the proxy settings for optimal performance.
+It also installs **PM2** for process management and starts your services with the appropriate configuration based on your SSL choice.
+The Nginx configuration includes optimizations for **WebSocket connections**, static file serving, and security headers.
+PM2 is configured to automatically restart services if they crash and to start them on system boot.
+:::
+
+The setup command will prompt you for the following information:
+
+#### Package Installation
+During this phase, you can enter package names that you want to install. For example, you might want to `ph install @powerhousedao/todo-demo-package` or other Powerhouse packages. This step is crucial for adding the specific functionality you need. You can also press Enter to skip this step and install packages later using the `ph install` command.
+
+#### Database Configuration
+The script offers two options for database configuration:
+*   **Option 1: Local Database** Sets up a local PostgreSQL database, which is ideal for development or small deployments. It automatically creates a database user with a secure random password and configures the database to accept local connections. This option is perfect for getting started quickly.
+*   **Option 2: Remote Database** Allows you to connect to a remote PostgreSQL database by providing a connection URL in the format `postgres://user:password@host:port/db`. This is recommended for production environments.
 
-The script takes care of all the necessary service configuration automatically. It installs and configures **Nginx** as a reverse proxy, sets up SSL certificates, and configures the proxy settings for optimal performance. It also installs **PM2** for process management and starts your services with the appropriate configuration based on your SSL choice. The Nginx configuration includes optimizations for **WebSocket connections**, static file serving, and security headers. PM2 is configured to automatically restart services if they crash and to start them on system boot.
+#### SSL Configuration
+For SSL configuration, you have two choices:
+*   **Option 1: Let's Encrypt (Recommended for Production)** This option requires you to provide a base domain (e.g., `powerhouse.xyz`) and subdomains for your services. The script will automatically obtain and configure SSL certificates for your domains.
+*   **Option 2: Self-signed Certificate** This is suitable for development or testing. It uses your machine's hostname and generates a self-signed certificate. Browsers will show security warnings with this option.
 
-### Step 5: Security Features
-Security is a top priority in the setup process. The script implements automatic SSL certificate management, generates secure database passwords, and configures security headers in Nginx. It also sets up proper proxy settings to support WebSocket connections securely. The security headers include protection against common web vulnerabilities, and the SSL configuration uses modern cipher suites and protocols. The script also ensures that sensitive files and directories have appropriate permissions.
+#### Domain Setup
+You will be asked to enter your `connect` and `switchboard` subdomains to complete the setup. If you need more information, revisit the cloud provider setup sections at the beginning of this guide.
 
+#### Security Features
+Security is a top priority. The script implements automatic SSL certificate management, generates secure database passwords, and configures security headers in Nginx, and sets up proper proxy settings to support WebSocket connections securely.
 
-## 3. Verifying the Setup
+## 2. Verifying the Setup
 
 After the installation is complete, it's important to verify that everything is working correctly. You can check the status of your services using PM2, verify the Nginx configuration, and ensure your SSL certificates are properly installed. This step is crucial for identifying any potential issues before they affect your users.
 
-1. Check service status of switchboard & connect:
+1. Check service status of switchboard and connect:
 ```bash
 ph service status
 ```
@@ -302,7 +390,7 @@ You can also use
 ```bash
 ph service start | stop | restart 
 ```
-- to start | stop | restart switchboard and connect
+to start | stop | restart switchboard and connect
 
 2. View Nginx configuration:
 ```bash
@@ -314,9 +402,10 @@ sudo nginx -t
 sudo certbot certificates  # if using Let's Encrypt
 ```
 
-## 4. Accessing Services
+## 3. Accessing the Services
 
-Once everything is set up, you can access your services through the configured domains. If you chose Let's Encrypt, your services will be available at their respective subdomains. With a self-signed certificate, you'll access the services through your machine's hostname with the appropriate base paths. The services are configured to use HTTPS by default, ensuring secure communication.
+Once everything is set up, you can access your services through the configured domains.   
+If you chose Let's Encrypt, your services will be available at their respective subdomains. With a self-signed certificate, you'll access the services through your machine's hostname with the appropriate base paths. The services are configured to use HTTPS by default, ensuring secure communication.
 
 ### With Let's Encrypt:
 - Connect: `https://connect.yourdomain.com`
@@ -326,18 +415,18 @@ Once everything is set up, you can access your services through the configured d
 - Connect: `https://your-hostname/connect`
 - Switchboard: `https://your-hostname/switchboard`
 
-## 5. Troubleshooting
+## 4. Troubleshooting
 
 When issues arise, there are several common problems you might encounter. 
-- The "ph: command not found" error usually means you need to source your shell configuration file. 
+- The "`ph`: command not found" error usually means you need to source your shell configuration file. 
 - Nginx configuration errors can be investigated through the error logs, and service issues can be diagnosed using PM2 logs. 
 - SSL certificate problems often relate to DNS settings or certificate paths. Understanding these common issues and their solutions will help you maintain a stable Powerhouse installation.
 
 ### Common Issues:
-1. **"ph: command not found"**
+1. **"`ph`: command not found"**
    - Run `source ~/.bashrc` or restart your terminal
-   - Verify that the PNPM_HOME environment variable is set correctly
-   - Check if the ph binary exists in the PNPM_HOME directory
+   - Verify that the `PNPM_HOME` environment variable is set correctly
+   - Check if the `ph` binary exists in the `PNPM_HOME` directory
 
 2. **Nginx configuration errors**
    - Check logs: `sudo tail -f /var/log/nginx/error.log`
@@ -354,7 +443,7 @@ When issues arise, there are several common problems you might encounter.
    - Check certificate paths in Nginx config
    - Ensure that the certificate files are readable by Nginx
 
-## 6. Maintenance
+## 5. Maintenance
 
 Regular maintenance is crucial for keeping your Powerhouse installation running smoothly. You can update services using the Powerhouse CLI, restart services through PM2, and monitor logs to ensure everything is functioning correctly. Regular maintenance helps prevent issues and ensures that your services are running with the latest security patches and features.
 
@@ -368,16 +457,16 @@ ph update <package-name>
 ph service restart
 ```
 
-### Viewing Logs:
+### Checking Service Status and Logs:
 ```bash
 ph service status
 ```
 
-## 7. Security Notes
+## 6. Security Notes
 
 Maintaining security is an ongoing process. It's essential to keep your database credentials secure and regularly update your SSL certificates. Regular monitoring of system logs helps identify potential security issues, and keeping your system and packages updated ensures you have the latest security patches. Consider implementing additional security measures such as firewall rules, intrusion detection systems, and regular security audits.
 
-## 8. Backup
+## 7. Backup
 
 Regular backups are crucial for data safety. The database can be backed up using pg_dump, and your configuration files can be archived using tar. These backups should be stored securely and tested regularly to ensure they can be restored if needed. Consider implementing an automated backup schedule and storing backups in multiple locations for redundancy.
 
@@ -391,7 +480,7 @@ pg_dump -U powerhouse -d powerhouse > backup.sql
 sudo tar -czf powerhouse-config.tar.gz /etc/powerhouse/
 ```
 
-## 9. Best Practices
+## 8. Best Practices
 
 To get the most out of your Powerhouse installation, follow these best practices:
 
@@ -401,7 +490,7 @@ To get the most out of your Powerhouse installation, follow these best practices
 4. **Testing**: Test your backup and restore procedures regularly.
 5. **Security**: Regularly review and update your security measures.
 
-## 10. Getting Help
+## 9. Getting Help
 
 If you encounter issues or need assistance, there are several resources available:
 

package/docs/academy/02-MasteryTrack/05-Launch/{03-RunOnACloudServer.md → _03-RunOnACloudServer}

@@ -17,7 +17,8 @@ Let's have a look at how to set up Connect & Switchboard apps on a cloud server.
 Ask your IT provider to get access to the AWS environment to set up a server.
 Launch a new server instance for Connect and Switchboard with the specific specs that fit your project.
 
-The steps to create an EC2 instance:
+<details>
+<summary> **The steps to create an EC2 instance** </summary>
    - Make sure your region is set to eu-west-1 (Ireland)
    - Name your instance something like `cloud-server` or your project's name
    - Select Ubuntu 24.04 LTS
@@ -34,13 +35,15 @@ The steps to create an EC2 instance:
       - Custom TCP (Port 8441) for Switchboard
    - **Launch the instance**
 
+   :::warning
+   Make sure to keep your key pair file (.pem) secure and never share it. Without it, you won't be able to access your instance. Also, consider setting up AWS IAM roles and policies for better security management.
+   :::
+
+</details>
+
 Now click on your instance ID, which will open a new window with the instance details. Hit the 'Connect' button to get the connection details.
 Within the instance details, you'll find the public IP address of your server instance. We'll use this to connect to our server instance later.
 
-:::warning
-Make sure to keep your key pair file (.pem) secure and never share it. Without it, you won't be able to access your instance. Also, consider setting up AWS IAM roles and policies for better security management.
-:::
-
 ### 1.2. Setting up your SSH connection
 
 Once you've generated your key pairs and added them to the designated folder, you can set up the SSH connections to start the process.

package/docs/academy/03-ExampleUsecases/Chatroom/02-CreateNewPowerhouseProject.md

@@ -1,20 +1,21 @@
 # Create New Powerhouse Project
 
-## Create New Powerhouse Document Model Library Project
+:::tip  **Prerequisites**
+- Powerhouse CLI installed: `pnpm install -g ph-cmd`
+- node.js 22 and pnpm installed
+- Visual Studio Code (or your preferred IDE)
+- Terminal/Command Prompt access
+
+If you need help with installing the prerequisites you can visit our page [prerequisites](/academy/MasteryTrack/BuilderEnvironment/Prerequisites)
+:::
 
 To create a new Powerhouse Document Model Library project, you can use the `ph init` command in your terminal. This command will create a new project in the current directory.
+This command will create a new project in the current directory. You can run the command in the terminal window of your OS or you open the newly installed VSCode and run the command in the terminal window of VSCode.Make sure the terminal reflects the directory where you want to create the new project.
 
-:::info
-This command will create a new project in the current directory.
-You can run the command in the terminal window of your OS or you open the newly installed VSCode and run the command in the terminal window of VSCode.
-You will need VSCode later in the tutorial once you have generated the document model.
-Make sure the terminal reflects the directory where you want to create the new project.
-To open a directory in a terminal, you use the cd command to change your current directory. The cd command takes an argument, usually the name of the folder you want to move to, so the full command is 
 ```bash
 cd your-directory
 ```
 This essentially opens that folder and places you in it.
-:::
 
 Once you've navigated to the directory where you want to create the new project and in your terminal, run the following command:
 
@@ -22,7 +23,7 @@ Once you've navigated to the directory where you want to create the new project
 ph init
 ```
 
-In the terminal, you will be asked to enter the project name. Fill in the project name and press enter. Make sure to use the name `ChatRoom` as the project name with capital letter R so all of our tutorial code works.
+In the terminal, you will be asked to enter the project name. Fill in the project name and press enter. Make sure to pay attention to the capitalization of our name `ChatRoom` as it will influence your code generation. 
 
 ```bash
 you@yourmachine:~/Powerhouse$ ph init

package/docs/academy/03-ExampleUsecases/Chatroom/03-DefineChatroomDocumentModel.md

@@ -9,9 +9,8 @@ Before you start, make sure you have the Connect application running.
 
 We use GraphQL Schema Definition Language (SDL) to define the document model schema. Below, you can see the SDL for the `ChatRoom` document model.
 
-:::info
-This schema contains the data structure of the document model and the basic operations that can be performed on the document model.
-Document models in Powerhouse leverage event sourcing principles, where every state transition is represented by an operation. GraphQL input types describe operations, ensuring that user intents are captured effectively. These operations detail the parameters needed for state transitions The use of GraphQL aligns these transitions with explicit, validated, and reproducible commands, supporting CQRS (Command Query Responsibility Segregation) patterns.
+:::info **The State Schema**
+This schema contains the data structure of the document model and the basic operations that can be performed on the document model. For more in depth information please visit [State Schema](/academy/MasteryTrack/DocumentModelCreation/SpecifyTheStateSchema)
 :::
 
 ## State Schema (See next steps)
@@ -101,7 +100,7 @@ The steps below show you how to do this:
 1. In the Connect application, click on the `ChatRoom` document model you've created in the previous step, to open the document model editor.
 2. You'll be welcomed with a form to fill, this is metadata about the document model, fill in the details in the fields. 
 
-    In the `Document Type` field, type `powerhouse/chatroom`. This defines the new type of document that will be created with this document model.
+    In the `Document Type` field, type `powerhouse/chat-room`. This defines the new type of document that will be created with this document model.
     
     ![Chatroom Document Model Form Metadata](image-2.png)
 

package/docs/academy/03-ExampleUsecases/Chatroom/05-ImplementChatroomEditor.md

@@ -191,4 +191,4 @@ Below GIF shows the `Chatroom` editor in action.
 
 ![Chatroom Editor](./images/ChatRoomTest.gif)
 
-If you managed to follow this tutorial until this point, you have successfully implemented the `ChatRoom` document model with its reducer operations and editor. In the next chapter we'll be showing you how to simulate a synchronisation between two nodes or users making use of the chatroom by starting up a local reactor.
+If you managed to follow this tutorial until this point, you have successfully implemented the `ChatRoom` document model with its reducer operations and editor. 

package/docs/academy/03-ExampleUsecases/Chatroom/_category_.json

@@ -3,6 +3,6 @@
   "position": 2,
   "link": {
     "type": "generated-index",
-    "description": "Get started with the Chatroom tutorial! Jump into creating a new Powerhouse project if you have NodeJs, VSCode, and Git installed. Whe are going to create a new document model that represents a chat.  So you as a user can post messages into that chat room, react to the messages. This chatroom will be synchronized between different connect instances. Let's explore the potential of the tools available in the powerhouse toolkit"
+    "description": "Get started with the Chatroom tutoria: Jump into creating a new Powerhouse project if you have NodeJs, VSCode, and Git installed. Whe are going to create a new document model that represents a chat.  So you as a user can post messages into that chat room, react to the messages. This chatroom will be synchronized between different connect instances. Let's explore the potential of the tools available in the powerhouse toolkit"
   }
 }

package/docs/academy/04-APIReferences/00-PowerhouseCLI.md

@@ -2,20 +2,19 @@
 
 ### Installing the Powerhouse CLI 
 :::tip
-The **Powerhouse CLI tool** is the only essential tool to install on this page. Install it with the command below. 
+The **Powerhouse CLI tool** is the only essential tool to install on this page. Install it with the command below.    
+
 You can find all of the commands on this page, similar to what would displayed when using ph --help or ph *command* --help. 
-Use the table of content or the search function to find what you are looking for.
-The Powerhouse CLI (`ph-cmd`) is a command-line interface tool that provides essential commands for managing Powerhouse projects. You can get access to the Powerhouse ecosystem tools by installing them globally using:
+Use the table of content or the search function to find what you are looking for.   
+
+The Powerhouse CLI (`ph-cmd`) is a command-line interface tool that provides essential commands for managing Powerhouse projects. You can get access to the Powerhouse ecosystem tools by installing them globally.
 
 ```bash
 pnpm install -g ph-cmd
 ``` 
  :::
 
-<!-- AUTO-GENERATED-CLI-COMMANDS-START -->
-
-## ph-cmd Commands
-- [Init](#init)
+<!-- AUTO-GENERATED-CLI-COMMANDS-START -->\n<!-- This content is automatically generated. Do not edit directly. -->\n### ph-cmd Commands\n\n- [Init](#init)
 - [Setup Globals](#setup-globals)
 - [Update](#update)
 - [Use](#use)
@@ -229,6 +228,7 @@ Command Overview:
   The Connect build command creates a connect build with the project's local and external packages included.
 
 Options:
+  --base <path> The base path for the app. Default is "/".
   --project-root <path>  The root directory of the project. Default is "process.cwd()".
   --assets-dir-name <name> The name of the assets directory. Default is "${DEFAULT_ASSETS_DIR_NAME}".
   --external-packages-file-name <name> The name of the external packages file. Default is "${DEFAULT_EXTERNAL_PACKAGES_FILE_NAME}".
@@ -244,6 +244,7 @@ Command Overview:
   NOTE: You must run \`ph connect build\` first.
 
 Options:
+  --base <path>          The base path for the app. Default is "/".
   --project-root <path>  The root directory of the project. Default is "process.cwd()".
   --port <port>          The port to run the server on. Default is 4173.
   --open                 Open the browser. Default is true.
@@ -571,13 +572,11 @@ Arguments:
                         - all: Act on all services (default)
 
 Examples:
-  $ ph service                               # List all services (same as 'ph service list all')
-  $ ph service start switchboard             # Start the Switchboard service
-  $ ph service stop connect                  # Stop the Connect service
-  $ ph service start all                     # Start all services
+  $ ph service setup                              # Setup services
+  $ ph service start              # Start the services
+  $ ph service stop                   # Stop the services
   $ ph service status                        # Check status of all services
-  $ ph service startup                       # Configure services to start on system boot
-  $ ph service unstartup                     # Remove services from system startup
+  
 
 Notes:
   - Services are managed using PM2, a process manager for Node.js applications
@@ -702,39 +701,4 @@ Notes:
 
 ---
 
-*This document was automatically generated from the help text in the codebase.*\n<!-- AUTO-GENERATED-CLI-COMMANDS-END -->
-
-<details>
-<summary> How to make use of different branches? </summary>
-
-When installing or using the Powerhouse CLI commands you are able to make use of the dev & staging branches. These branches contain more experimental features then the latest stable release the PH CLI uses by default. They can be used to get access to a bugfix or features under development.
-
-| Command | Description |
-|---------|-------------|
-| **pnpm install -g ph-cmd** | Install latest stable version |
-| **pnpm install -g ph-cmd@dev** | Install development version |
-| **pnpm install -g ph-cmd@staging** | Install staging version |
-| **ph init** | Use latest stable version of the boilerplate |
-| **ph init --dev** | Use development version of the boilerplate |
-| **ph init --staging** | Use staging version of the boilerplate |
-| **ph use** | Switch all dependencies to latest production versions |
-| **ph use dev** | Switch all dependencies to development versions |
-| **ph use prod** | Switch all dependencies to production versions |
-
-Please be aware that these versions can contain bugs and experimental features that aren't fully tested.
-</details>
-
-
-the ph connect command now uses three subcommands:
-
-studio (default) — runs connect studio. since this is the default argument, running ph connect still has the same behavior as before,
-
-build — bundles the project's local and external model/editor code and injects the js/css into the already-built connect bundle for deployment,
-
-preview — runs the vite preview server with the output of build for testing purposes,
-
-running ph connect --help now lists the sub-commands. Running ph connect studio --help now shows the help for the studio command, likewise for the other new commands.
-
-This approach avoids redundant build/compilation which is great for minimizing server resource use. The only compilation that runs is the esbuild of the project code (does not need tsc as that is handled separately) and then tailwind for the local project styles. The whole thing takes less than a second, albeit on my macbook.
-
-This should just work with the current boilerplate since these are just new arguments to the existing ph-cli connect command. 
+*This document was automatically generated from the help text in the codebase.*\n<!-- AUTO-GENERATED-CLI-COMMANDS-END -->

package/docs/academy/05-Architecture/00-PowerhouseArchitecture.md

@@ -12,6 +12,9 @@ These five applications are:
 
 Each application is designed to be modular yet complementary, ensuring smooth data flows, structured collaboration, and scalable automation. The functionality of the four host apps offers an integrated experience for running decentralized operations.
 
+![Powerhouse Host Apps Interaction](./images/PowerhouseArchitecture.png)
+
+
 ## How the Five Applications Work Together
 
 The Powerhouse ecosystem functions as a decentralized operating system, where each of the four core applications works in synergy to ensure seamless collaboration, structured data management, and automated workflows. Each application has a distinct purpose, yet their interconnectivity is what makes the system powerful.