@powerhousedao/academy 3.2.0 → 3.3.0-dev.1

package/CHANGELOG.md

@@ -1,43 +1,81 @@
-## 3.2.0 (2025-07-02)
+## 3.3.0-dev.1 (2025-07-04)
 
 This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
 
-## 3.2.0-staging.3 (2025-07-02)
+## 3.3.0-dev.0 (2025-07-02)
 
 ### 🚀 Features
 
-- updated release-notes.md ([843fcc72d](https://github.com/powerhouse-inc/powerhouse/commit/843fcc72d))
-- add RELEASE-NOTES.md from main branch ([8170e40a3](https://github.com/powerhouse-inc/powerhouse/commit/8170e40a3))
+- **academy:** add Drive Analytics documentation and examples ([daedc28a3](https://github.com/powerhouse-inc/powerhouse/commit/daedc28a3))
+- starting to stub out a complete example of the analytics processor ([a84ed2dcf](https://github.com/powerhouse-inc/powerhouse/commit/a84ed2dcf))
+- **connect:** use atom store and provider from state library ([28f646636](https://github.com/powerhouse-inc/powerhouse/commit/28f646636))
+- added drive analytics processor ([#1607](https://github.com/powerhouse-inc/powerhouse/pull/1607))
+
+### 🩹 Fixes
+
+- fix build ([c0cd6988d](https://github.com/powerhouse-inc/powerhouse/commit/c0cd6988d))
+- updated processor generator and added codegen test for it ([6af3bbcf7](https://github.com/powerhouse-inc/powerhouse/commit/6af3bbcf7))
+- added test to generate and compile a generated document-model ([17bbca3bb](https://github.com/powerhouse-inc/powerhouse/commit/17bbca3bb))
+- updated document-engineering ver ([3522179d6](https://github.com/powerhouse-inc/powerhouse/commit/3522179d6))
+- updated atoms with header changes ([2b557197a](https://github.com/powerhouse-inc/powerhouse/commit/2b557197a))
 
 ### ❤️ Thank You
 
-- Callme-T
+- acaldas @acaldas
+- Benjamin Jordan (@thegoldenmule)
+- Guillermo Puente @gpuente
+- Guillermo Puente Sandoval @gpuente
+- ryanwolhuter @ryanwolhuter
 
-## 3.2.0-staging.2 (2025-07-01)
+## 3.2.0-dev.9 (2025-07-02)
+
+### 🩹 Fixes
+
+- updated processor generator and added codegen test for it ([6af3bbcf7](https://github.com/powerhouse-inc/powerhouse/commit/6af3bbcf7))
+- added test to generate and compile a generated document-model ([17bbca3bb](https://github.com/powerhouse-inc/powerhouse/commit/17bbca3bb))
+
+### ❤️ Thank You
+
+- Benjamin Jordan (@thegoldenmule)
+
+## 3.2.0-dev.8 (2025-07-01)
 
 ### 🚀 Features
 
-- **reactor-api,reactor-local:** allow providing processors to be instantiated and enable drive analytics ([1a3800fc2](https://github.com/powerhouse-inc/powerhouse/commit/1a3800fc2))
+- **academy:** add Drive Analytics documentation and examples ([daedc28a3](https://github.com/powerhouse-inc/powerhouse/commit/daedc28a3))
 
 ### ❤️ Thank You
 
-- acaldas @acaldas
+- Guillermo Puente @gpuente
 
-## 3.2.0-staging.1 (2025-07-01)
+## 3.2.0-dev.7 (2025-06-28)
 
 ### 🚀 Features
 
-- **academy:** add Drive Analytics documentation and examples ([430ca8fab](https://github.com/powerhouse-inc/powerhouse/commit/430ca8fab))
-- **connect:** use atom store and provider from state library ([d617a1fe2](https://github.com/powerhouse-inc/powerhouse/commit/d617a1fe2))
+- starting to stub out a complete example of the analytics processor ([a84ed2dcf](https://github.com/powerhouse-inc/powerhouse/commit/a84ed2dcf))
 
 ### ❤️ Thank You
 
-- Guillermo Puente
-- ryanwolhuter
+- Benjamin Jordan (@thegoldenmule)
 
-## 3.2.0-staging.0 (2025-06-26)
+## 3.2.0-dev.6 (2025-06-27)
 
-This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
+### 🚀 Features
+
+- **connect:** use atom store and provider from state library ([28f646636](https://github.com/powerhouse-inc/powerhouse/commit/28f646636))
+- added drive analytics processor ([#1607](https://github.com/powerhouse-inc/powerhouse/pull/1607))
+
+### 🩹 Fixes
+
+- updated document-engineering ver ([3522179d6](https://github.com/powerhouse-inc/powerhouse/commit/3522179d6))
+- updated atoms with header changes ([2b557197a](https://github.com/powerhouse-inc/powerhouse/commit/2b557197a))
+
+### ❤️ Thank You
+
+- Benjamin Jordan (@thegoldenmule)
+- Guillermo Puente
+- Guillermo Puente Sandoval
+- ryanwolhuter
 
 ## 3.2.0-dev.5 (2025-06-26)
 

package/docs/academy/01-GetStarted/00-ExploreDemoPackage.mdx

@@ -1,18 +1,5 @@
 # Explore the demo package
 
-<details>
-<summary>How long will this tutorial take?</summary>
-
-We've designed this "Get Started" track to be as smooth as possible. The time it takes will vary based on your familiarity with modern web development tools.
-
-- **For Experienced Developers** (familiar with TypeScript, React, and CLIs), you can expect to complete the entire four-part tutorial in approximately **1 to 1.5 hours**.
-- **For Developers New to This Stack**, we recommend setting aside **3.5 to 4.5 hours**. This allows for time to understand not just the steps, but the core concepts behind them.
-
-This is just a guideline. The goal is to learn comfortably and build a solid foundation with Powerhouse!
-
-A more theoretical and advanced version of this tutorial can also be found in [Mastery Track - Document Model Creation](../MasteryTrack/DocumentModelCreation/WhatIsADocumentModel).
-</details>
-
 ## Let's get started
 
 To give you a quick idea of how the Powerhouse ecosystem operates on document models and packages, why don't you try installing a package? 
@@ -109,7 +96,55 @@ Here, you'll see that you've installed the `@powerhousedao/todo-demo-package`, w
   <figcaption>The Package Manager showing the installed todo-demo-package.</figcaption>
 </figure>
 
-## Step 4: Log in with Renown
+## Step 4: Create a todo list document
+
+:::tip What is a 'drive' at Powerhouse?
+A **drive** is a folder to store and organize your documents in. Powerhouse offers the ability to build customized 'Drive Apps' for your documents. Think of a Drive App as a specialized lens—it offers **different ways to visualize, organize, and interact with** the data stored within a drive, making it more intuitive and efficient for specific use cases. To learn more, visit [Building A Drive App](/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer)
+:::
+
+### 4.1 Create a local todolist app drive
+
+First, let's create a dedicated drive for your to-do lists:
+
+- Click the new drive icon in the interface
+- In the **Drive App** field, select 'To-do Drive App'
+- This creates a specialized drive that's optimized for to-do list documents
+
+### 4.2 Create a todolist document
+
+Now move into the drive you've just created:
+
+- Click the button at the bottom of the page to create a new to-do list document
+- This opens the to-do list editor where you can start managing your tasks
+
+### 4.3 Add a few todos and inspect the document history
+
+- Add a few to-dos that are on your mind
+- You'll see a statistics widget that counts the open to-dos
+- After closing the document, look at the To-do Drive App interface—you'll see that it tracks your tasks and displays a progress bar
+
+<figure className="image-container">
+  <img src={require("./images/TodoDriveApp.png").default} alt="Todo Drive App" />
+  <figcaption>A list of todo's in the custom todo drive app. </figcaption>
+</figure>
+
+A key feature you get with Connect is the **Operations History**. Every change to a document is stored as an individual operation, creating an immutable and replayable history. This provides complete auditability and transparency, as you can inspect each revision, its details, and any associated signatures. For example, you can see a chronological list of all modifications, along with who made them and when.
+
+<figure className="image-container">
+  <img src={require("./images/OperationsHistoryButton.png").default} alt="Operations History Button" />
+  <figcaption> You can find the button to visit the operations history in the document model toolbar </figcaption>
+</figure>
+
+<figure className="image-container">
+  <img src={require("./images/OperationsHistory.png").default} alt="Operations History" />
+  <figcaption>Example of the operations history for a document, showing all modifications made to it in a list. </figcaption>
+</figure>
+
+Learn more about the [Operations History](../MasteryTrack/BuildingUserExperiences/DocumentTools/OperationHistory) and other document tools you get for free.
+
+This is the power of Drive Apps. They offer a customized interface that works well with the different documents inside your drive. Read more about drive apps in the Mastery Track: [Drive Apps and Drive Explorers](/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer).
+
+## Step 5: Enable operation signing and verification through Renown
 
 Renown is Powerhouse's **decentralized identity and reputation system** designed to address the challenge of trust within open organizations, where contributors often operate under pseudonyms. In traditional organizations, personal identity and reputation are key to establishing trust and accountability. Renown replicates this dynamic in the digital space, allowing contributors to earn experience and build reputation without revealing their real-world identities.
 
@@ -117,16 +152,18 @@ Renown is Powerhouse's **decentralized identity and reputation system** designed
 When signing in with Renown, use an Ethereum or blockchain address that can function as your 'identity', as this address will accrue more experience and history over time.
 :::
 
-### Login flow
-"**Log in with Renown**" is a decentralized authentication flow that enables you to log into applications by signing a credential with your Ethereum wallet. Upon signing in, a Decentralized Identifier (DID) is created based on your Ethereum key. 
+### 5.1 Click the renown icon and connect your eth identity
+
+"**Log in with Renown**" is a decentralized authentication flow that enables you to log into applications by signing a credential with your Ethereum wallet. Upon signing in, a Decentralized Identifier (DID) is created based on your Ethereum key.
 
 <figure className="image-container">
   <img src={require("./images/RenownLogin.png").default} alt="Renown Login" />
   <figcaption>The Renown login screen, prompting for a signature from a wallet.</figcaption>
 </figure>
 
-### Generate a DID to sign operations in Connect
-This DID is then associated with a credential that authorizes a specific Connect instance to act on your behalf. That credential is stored securely on Ceramic, a decentralized data network. When you perform actions through the Powerhouse Connect interface, those operations are signed with the DID and transmitted to Switchboard, which serves as the verifier. 
+### 5.2 Authorize Connect to sign document edits on your behalf
+
+This DID is then associated with a credential that authorizes a specific Connect instance to act on your behalf. That credential is stored securely on Ceramic, a decentralized data network. When you perform actions through the Powerhouse Connect interface, those operations are signed with the DID and transmitted to Switchboard, which serves as the verifier.
 
 <figure className="image-container">
   <img src={require("./images/ConnectAddress.png").default} alt="Connect Address for DID" />
@@ -138,45 +175,17 @@ This DID is then associated with a credential that authorizes a specific Connect
   <figcaption>Confirmation of a successful login with Renown.</figcaption>
 </figure>
 
-### Verifying signatures
-**Switchboard**, our (remote & local) data processing engine, acts as a verifier in the Renown authentication flow. Switchboard checks the validity of the DID and credential, ensuring the operation request is legitimate. This flow is designed to offer a verifiable, cryptographically secure login system that replaces traditional password-based authentication with decentralized identity and signature-based trust.
+### 5.3 Verify the signatures of new operations in the todo list
 
-## Step 5: Create a to-do list and explore the document operations history
-
-<figure className="image-container">
-  <img src={require("./images/OperationsHistory.png").default} alt="Operations History" />
-  <figcaption>Example of the operations history for a document, showing all modifications made to it in a list. </figcaption>
-</figure>
+By leveraging this system, every operation or modification made to a document is cryptographically signed by the contributor's Renown identity. This ensures that each change is verifiable, traceable, and attributable to a specific pseudonymous user, providing a robust audit trail for all document activity.
 
-By leveraging this system, every operation or modification made to a document is cryptographically signed by the contributor's Renown identity. This ensures that each change is verifiable, traceable, and attributable to a specific pseudonymous user, providing a robust audit trail for all document activity. 
-
-A key feature you get with Connect is the **Operations History**. Every change to a document is stored as an individual operation, creating an immutable and replayable history. This provides complete auditability and transparency, as you can inspect each revision, its details, and any associated signatures. For example, you can see a chronological list of all modifications, along with who made them and when. This ensures every action is traceable and verifiable.
-Learn more about the [Operations History](../MasteryTrack/BuildingUserExperiences/DocumentTools/OperationHistory) and other document tools you get for free.
-
-
-### 5.1 Create a to-do list
-
-Now, move back to your local drive and create a to-do list. Add a few to-dos that are on your mind. You'll see a statistics widget that counts the open to-dos.
-
-### 5.2 Create a specific to-do drive app
-
-:::tip What is a 'drive' at Powerhouse?
-A **drive** is a folder to store and organize your documents in. Powerhouse offers the ability to build customized 'Drive Apps' for your documents. Think of a Drive App as a specialized lens—it offers **different ways to visualize, organize, and interact with** the data stored within a drive, making it more intuitive and efficient for specific use cases. To learn more, visit [Building A Drive App](/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer)
-:::
-
-Since your previous to-do list was created inside a local drive with a general-purpose drive explorer, it didn't look particularly special.
-
-- Now let's create a new drive by clicking the new drive icon. In the **Drive App** field, select 'To-do Drive App'.  
-- Now move into the drive you've just created and create a new to-do list by clicking the button at the bottom of the page. 
-- Add a new set of random to-dos
-- After closing the document, look at the To-do Drive App interface. You'll see that it tracks your tasks and displays a progress bar.
+Now, return to your to-do list and make some additional changes. You'll notice that these operations are now signed with your Renown identity, making every action traceable and verifiable in the operations history.
 
 <figure className="image-container">
-  <img src={require("./images/TodoDriveApp.png").default} alt="Operations History" />
-  <figcaption>A list of todo's in the custom todo drive app. </figcaption>
+  <img src={require("./images/OperationsHistorySignature.png").default} alt="Operation History Signature" />
+  <figcaption>Your DID is now signing the operations that are being added to the history.</figcaption>
 </figure>
 
-This is the power of Drive Apps. They offer a customized interface that works well with the different documents inside your drive. Read more about drive apps in the Mastery Track: [Drive Apps and Drive Explorers](/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer).
 ## Step 6: Export a document
 
 Export the document as a `.phd` (Powerhouse Document) file using the export button in the document toolbar at the top. In this toolbar, you will find all available functionality for your documents. The `.phd` file can be sent through any of your preferred channels to other users on your network. 

package/docs/academy/01-GetStarted/01-CreateNewPowerhouseProject.md

@@ -1,4 +1,4 @@
-# Create a to-do list document
+# Create a new to-do list document
 
 ## Overview
 This tutorial guides you through creating a simplified version of a 'Powerhouse project' for a **To-do List**.   
@@ -18,52 +18,32 @@ Create a new Powerhouse project with a single command:
 ```bash
 ph init
 ```
-<details>
-<summary>How to use 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>
 
 ## Before you begin
 1. Open your terminal (either your system terminal or IDE's integrated terminal)
-2. Navigate to your desired project directory using:
+2. Optionally, create a folder first to keep your Powerhouse projects:
 
    ```bash
-   cd your-directory
+   mkdir ph-projects
+   cd ph-projects
    ```
 3. Ensure you're in the correct directory before running the `ph init` command.  
 In the terminal, you will be asked to enter the project name. Fill in the project name and press Enter.
    ```bash
-    you@yourmachine:~/Powerhouse$ ph init
+    you@yourmachine:~/ph-projects % ph init
 
-    ? What is the project name? ‣ <ToDoList>
+    ? What is the project name? ‣ getting-started
     ```	
 
     Once the project is created, you will see the following output:
     ```bash
-    Initialized empty Git repository in /Users/yourmachine/<ToDoList>/.git/
+    Initialized empty Git repository in /Users/you/ph-projects/getting-started/.git/
     The installation is done! 
     ```
 
     Navigate to the newly created project directory:
     ```bash
-    cd <yourprojectname>
+    cd getting-started
     ```
     Once in the project directory, run the `ph connect` command to start a local instance of the Connect application. This allows you to start your document model specification document.
     Run the following command to start the Connect application:

package/docs/academy/01-GetStarted/02-DefineToDoListDocumentModel.md

@@ -1,4 +1,4 @@
-# Define the to-do list document specification 
+# Write the document specification 
 
 In this tutorial, you will learn how to define the specifications for a **To-do List** document model within the Connect application using its GraphQL schema, and then export the resulting document model specification document for your Powerhouse project.
 If you don't have a document specification file created yet, have a look at the previous step of this tutorial to create a new document specification.

package/docs/academy/02-MasteryTrack/03-BuildingUserExperiences/02-ConfiguringDrives.md

@@ -1,6 +1,6 @@
 # Configure a drive
 
-A drive in Powerhouse is a container or a wrapper for documents and data. It's a place where you can organize and store your documents and share them with others. This guide will walk you through the process of configuring and managing drives in your Powerhouse environment.   
+A drive in Powerhouse is a container for documents and data. It's a place where you can organize and store your documents and share them with others. This guide walks you through configuring and managing drives in your Powerhouse environment.   
 
 :::info **Prerequisites**
 
@@ -14,64 +14,74 @@ Before configuring a drive, ensure you have:
 
 ### Local drives
 
-A local drive is a container for local documents and data, hosted on your local machine. Technically a drive is just another document model with a list of the documents inside the drive. When you run connect locally with `ph connect` a local drive is automatically added. You can also create a new local drive by clicking **'add drive'** in connect.
+A local drive is a container for local documents and data, hosted on your local machine. Technically, a drive is itself a document that contains a list of the documents inside it. When you run Connect locally with `ph connect`, a local drive is automatically added. You can also create a new local drive by clicking **'Create New Drive'** in Connect.
 
 ### Remote drives vs. reactors 
 
-Remote drives in Powerhouse allow you to connect to and work with data stored in external systems or cloud services. These drives act as bridges between Powerhouse contributors and/or other data sources, enabling seamless data synchronization. Drives can exist in 3 category locations.
+Remote drives in Powerhouse allow you to connect to and work with data stored in external systems or cloud services. These drives act as bridges between Powerhouse contributors or other data sources, enabling seamless data synchronization. Drives can exist in three types of locations:
 
 - **Local Storage**: For offline or on-device access.
 - **Cloud Storage**: For centralized, scalable data management.
 - **Decentralized Storage**: Such as Ceramic or IPFS, enabling distributed and blockchain-based storage options.
 
 :::tip **Explainer**
-**Powerhouse Reactors** are the nodes in the network that store and synchronise documents & drives , resolve conflicts and rerun operations to verify document event histories. 
-Reactors can be configured for local storage, centralized cloud storage or on a decentralized storage network. 
+**Powerhouse Reactors** are the nodes in the network that store and synchronize documents and drives, resolve conflicts, and rerun operations to verify document event histories. 
+Reactors can be configured for local storage, centralized cloud storage, or a decentralized storage network. 
 
-A reactor allows you to store multiple documents, but also host **drives** & Drive Explorers with different organisational purposes, users, access rights and more.
+A reactor allows you to store multiple documents and host **drives** and Drive Explorers with different organizational purposes, users, access rights, and more.
 :::
 
-A drive exists by making use of a reactor and the storagelayer that specific reactor is based on. A reactor is the lower level component that makes synchronisation of documents & drives possible. 
+A drive uses a reactor and its underlying storage layer. A reactor is the low-level component that enables the synchronization of documents and drives. 
 
 ### Drive apps 
 
-**Drive Explorers** (also known as Drive Apps) are specialized interfaces that enhance how users interact with document models within a drive. As mentioned previously, technically a drive is just another document, with a list of the documents inside the drive. So it is obvious that you can create a custom editor for your drive-document. 
+**Drive Explorers** (also known as Drive Apps) are specialized interfaces that enhance how users interact with documents within a drive. As mentioned, a drive is technically just another document containing a list of other documents. This means you can create a custom editor for your drive document. 
 
-These customized editors are called Drive explorers or Drive Apps. They provide custom views, organization tools, and interactive features tailored to specific use cases. For example, a Drive Explorer might present data as a Kanban board, provide aggregated insights, or offer specialized widgets for data processing. 
+These customized editors are called Drive Explorers or Drive Apps. They provide custom views, organization tools, and interactive features tailored to specific use cases. For example, a Drive Explorer might present data as a Kanban board, provide aggregated insights, or offer specialized widgets for data processing. 
 
 To learn more about building and customizing Drive Explorers, check out our [Building a Drive Explorer](/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer) guide.
 
 
 ## Creating a new drive
 
-![Create New Drive](./images/CreateNewDrive.png)
+<figure className="image-container">
+  <img src={require("./images/CreateDrive.png").default} alt="Create a new drive" />
+  <figcaption>The drive management modal after clicking the 'Create New Drive' button.</figcaption>
+</figure>
 
 To create a new drive in Powerhouse, follow these steps:
-1. Click on the "**Create New Drive**" button in the Connect interface or in the Connect sidebar on the (+) Icon. 
+1. Click the "**Create New Drive**" button in the Connect interface or the **+** icon in the Connect sidebar. 
 2. In the modal that appears, enter a name for your drive in the "**Drive Name**" field.
 3. Select the desired Drive App (such as the Generic Drive Explorer, or any other Drive App you've installed).
 4. Choose the location for your drive: **Local** (only available to you), **Cloud** (available to people in this drive), or **Public** (available to everyone).
 5. (Optional) Enable the "Make available offline" toggle if you want to keep a local backup of your drive.
 6. Once all options are set, click the "Create new drive" button to finalize and create your drive.
 
-## Adding a new remote drive via graphql mutation
+## Add a new remote drive via GraphQL mutation
 
 You can also add a new remote drive to your Connect environment programmatically using GraphQL mutations. This is especially useful for automation, scripting, or integrating with external systems.
 
 :::info **Prerequisites**
-- Access to the Switchboard or remote reactor (server node) of your Connect instance.
-- The GraphQL endpoint for your instance. For example, for the staging environment, use: `https://staging.switchboard.phd/graphql/system` (this is a supergraph gateway).
+- Access to the Switchboard or remote reactor (server node) of your Connect instance. In your local project, you can start your Reactor by running the following command in a different terminal from Connect Studio. 
+  `bash
+  ph reactor
+  `
+- The GraphQL endpoint of your instance. For example, for the staging environment, use: `https://staging.switchboard.phd/graphql/system` (this is a supergraph gateway. Read more about [subgraphs and supergraphs here](/academy/MasteryTrack/WorkWithData/WorkingWithSubgraphs).
 - Appropriate permissions to perform mutations.
 :::
 
-### Steps
-1. **Navigate to the GraphQL Playground or use a GraphQL client**
-   - Open [https://staging.switchboard.phd/graphql/system](https://staging.switchboard.phd/graphql/system) in your browser, or use a tool like [GraphQL Playground](https://www.apollographql.com/docs/apollo-server/testing/graphql-playground/).
+<figure className="image-container">
+  <img src={require("./images/CreateNewDrive.png").default} alt="Create a new drive" />
+  <figcaption>The GraphQL interface for creating a new drive through a mutation.</figcaption>
+</figure>
 
-2. **Prepare the Mutation**
+### 1. **Navigate to the GraphQL Playground or use a GraphQL client**
+   - Open [https://switchboard.phd/graphql/system](https://switchboard.phd/graphql/system) in your browser, or use a tool like [GraphQL Playground](https://www.apollographql.com/docs/apollo-server/testing/graphql-playground/).
+
+### 2. **Prepare the Mutation**
    - Use the following mutation to create a new drive:
 
-   ```graphql
+   ```graphql title="Create Drive Mutation"
    mutation Mutation($name: String!, $icon: String, $addDriveId: String, $slug: String) {
      addDrive(name: $name, icon: $icon, id: $addDriveId, slug: $slug) {
        icon
@@ -82,8 +92,8 @@ You can also add a new remote drive to your Connect environment programmatically
    }
    ```
 
-   - Example variables:
-   ```json
+   - These are the example variables, feel free to change these as you like and add a different name or logo for your drive:
+   ```json title="Example Variables"
    {
      "name": "AcademyTest",
      "icon": "https://static.thenounproject.com/png/3009860-200.png",
@@ -91,12 +101,12 @@ You can also add a new remote drive to your Connect environment programmatically
      "slug": null
    }
    ```
-   - You can also provide a custom `id`, `slug`, or `preferredEditor` if needed.
+   - You can also provide a custom `id` or `slug` if needed.
 
-3. **Execute the Mutation**
+### 3. **Execute the Mutation**
    - Run the mutation. On success, you will receive a response containing the new drive's `icon`, `id`, `name`, and `slug`:
 
-   ```json
+   ```json title="Successful Response"
    {
      "data": {
        "addDrive": {
@@ -109,16 +119,30 @@ You can also add a new remote drive to your Connect environment programmatically
    }
    ```
 
-4. **Construct the Drive URL**
+### 4. **Construct the Drive URL**
    - Once you have the `id` or `slug`, you can construct the drive URL for Connect:
-     - Format: `domain/d/driveId` or `domain/d/driveSlug`
-     - Example: `https://staging.connect.phd/d/6461580b-d317-4596-942d-f6b3d1bfc8fd`
+     - Format: `domain/d/<driveId>` or `domain/d/<driveSlug>` 
+     - Depending on whether you are using a hosted or a local environment, the domain in your URL will change.
+     - Example: `https://connect.phd/d/6461580b-d317-4596-942d-f6b3d1bfc8fd`
+     - Example: `https://localhost:4001/d/6461580b-d317-4596-942d-f6b3d1bfc8fd`
+
+### 5. **Add the Drive in Connect**
+   - Use the constructed URL to add or access the drive in your Connect environment via the 'Add Drive' button. 
 
-5. **Add the Drive in Connect**
-   - Use the constructed URL to add or access the drive in your Connect environment.
+<figure className="image-container">
+  <img src={require("./images/AddDrive.png").default} alt="Create a new drive" />
+  <figcaption>The 'Add Drive' button that allows you to enter your constructed Drive URL.</figcaption>
+</figure>
 
 ---
 
 This approach allows you to automate drive creation and integration with other systems, making it easy to manage drives at scale.
 
+## Up next 
+
+You've now experienced the use of GraphQL to modify or read data captured in Powerhouse for the first time. 
+You can now either continue with:
+- User interfaces and [build a custom drive experiences](/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer) 
+- Keep playing with data and the [Switchboard API](/academy/MasteryTrack/WorkWithData/ReadingAndWritingThroughTheAPI)
 
+Enjoy!