@powerhousedao/academy 5.0.0-staging.9 → 5.0.1-staging.2

package/docs/academy/02-MasteryTrack/04-WorkWithData/_ARCHIVE-AnalyticsProcessorTutorial/_03-GenerateAnAnalyticsProcessor.md

@@ -5,7 +5,7 @@
 **First**, navigate to the project directory with `cd rwa-analytics` to start the reactor from the project directory.
 Now open the directory with your code editor with the command `code . `
 
-Next, launch the reactor by running the following command in your terminal. 
+Next, launch the reactor by running the following command in your terminal.
 `ph reactor` . A Reactor instance is a local (or remote) node in the Powerhouse network that can hold & sychronize data. You'll see the following output in your terminal while the reactor is starting up and a new browser window opens with the Connect application. The reactor you've created will become available as a public drive in Connect's left hand side bar, named `Powerhouse`.
 
 ```bash
@@ -22,59 +22,55 @@ Next, launch the reactor by running the following command in your terminal.
 [Connect]:   ➜  Local:   http://localhost:3000/
 ```
 
-As you can see the reactor registered the default system subgraph but also the `d/:drive` subgraph for fetching documents and pushing updates. It also registered the analytics subgraph, which we'll use later for running analytics queries on the document model in the next steps. 
+As you can see the reactor registered the default system subgraph but also the `d/:drive` subgraph for fetching documents and pushing updates. It also registered the analytics subgraph, which we'll use later for running analytics queries on the document model in the next steps.
 
 ### Generate the analytics processor
+
 **Next** we'll open up a second terminal window and generate the analytics processor.
 Use the following command to generate the analytics processor in a seperate terminal window.
+
 ```bash
 npm run generate -- --processor rwa-analytics --document-types makerdao/rwa-portfolio
 ```
-In your project directory you'll now see the folder 'processors' being created. 
+
+In your project directory you'll now see the folder 'processors' being created.
 Later we'll see how this processor is actively listening for the operations on a document model.
 Eventually we'll replace the default code of the generated processor with our own custom analytics processor code to listen to specific operations, dimensions and metrics.
 
 ### Add data to the document model in the reactor
 
 Now that we've generated the analytics processor we need to give it some data to listen to.
-For this we've created the local reactor instance, which will represent a node in the Powerhouse network. 
-It represents a node that is usually hosted as a remote server, but in our case we run it locally on our machine. 
-The document model data will be stored in the local reactor instance and be analyzed by the analytics processor. 
+For this we've created the local reactor instance, which will represent a node in the Powerhouse network.
+It represents a node that is usually hosted as a remote server, but in our case we run it locally on our machine.
+The document model data will be stored in the local reactor instance and be analyzed by the analytics processor.
 
 Let's move on to the next step where we'll create a new RWA document model and add data to it.
 
 ### A brief introduction to the RWA document model
 
 :::info
-An RWA document model helps an arranger for Sky (previously MakerDAO) to accurately track the value of a Real World Asset (RWA) such as US treasury bills by tracking the purchase, sale and other transactions on the asset. 
-In the case of Sky these real world assets are used to back the Sky/MakerDAO stablecoin. 
-Let's pretend we're an arranger and we want to track the value of a new RWA asset and analyze the total value of the assetclass on a monthly basis. 
-Aside from setting up an analytics processor you'll now also become familiar with how the RWA reporting workflow is captured in a document model. 
+An RWA document model helps an arranger for Sky (previously MakerDAO) to accurately track the value of a Real World Asset (RWA) such as US treasury bills by tracking the purchase, sale and other transactions on the asset.
+In the case of Sky these real world assets are used to back the Sky/MakerDAO stablecoin.
+Let's pretend we're an arranger and we want to track the value of a new RWA asset and analyze the total value of the assetclass on a monthly basis.
+Aside from setting up an analytics processor you'll now also become familiar with how the RWA reporting workflow is captured in a document model.
 :::
 
-We'll run through the following scenario:			
-	1. Add the Asset "T-Bill 4565446" with CUSIP : TB4565446, maturity 01/12/2024. So we have a new asset to track and work with in the document model.		
-	2. Make a "principal draw" of $10,000,000 on May 1. We're simulating an arranger borrowing $10,000,000 from Sky to purchase the asset.				
-	3. Make a purchase of 2,500,000 TB4565446 bills for $2,490,000 on May 15.				
-	4. Make a purchase of 2,000,000 TB4565446 bills for $1,995,000 on June 15.				
-	5. Make a sale of 4,000,000 TB4565446 bills for $4,000,000 on July 1.				
-	6. Verify that the document data is correctly entered.					
-	7. Inspect the document history.
+We'll run through the following scenario: 1. Add the Asset "T-Bill 4565446" with CUSIP : TB4565446, maturity 01/12/2024. So we have a new asset to track and work with in the document model. 2. Make a "principal draw" of $10,000,000 on May 1. We're simulating an arranger borrowing $10,000,000 from Sky to purchase the asset. 3. Make a purchase of 2,500,000 TB4565446 bills for $2,490,000 on May 15. 4. Make a purchase of 2,000,000 TB4565446 bills for $1,995,000 on June 15. 5. Make a sale of 4,000,000 TB4565446 bills for $4,000,000 on July 1. 6. Verify that the document data is correctly entered. 7. Inspect the document history.
 
 ### Create a new RWA document model in Connect
 
-Under the 'New Document' section in Connect, click on the 'RWA Portfolio' document. 
+Under the 'New Document' section in Connect, click on the 'RWA Portfolio' document.
 Name your document model `Sky Rwa's` and click on 'Create'.
 
 ![Create a new RWA document](./images/create-a-new-RWA-document.gif)
 
-You'll immmediaty see that you've arrived in the portfolio editor with the option to add a new asset. 
-Since this document model is a portfolio for tracking the value of different assets, we'll first need to create the asset to be able to add any transaction history to them and track the value of the assets. 
+You'll immmediaty see that you've arrived in the portfolio editor with the option to add a new asset.
+Since this document model is a portfolio for tracking the value of different assets, we'll first need to create the asset to be able to add any transaction history to them and track the value of the assets.
 
-Hit the 'create asset' button. Which will offer you an overview of all the fields you need to fill in. 
-Before we can add an asset, we need to create a new "Special purpose vehicle" (SPV) for the asset. 
-A SPV is a legal entity that is created to hold the real world asset such as a US treasury bill. 
-For the sake of easily remembering the SPV let's name it 'SPV A'. 
+Hit the 'create asset' button. Which will offer you an overview of all the fields you need to fill in.
+Before we can add an asset, we need to create a new "Special purpose vehicle" (SPV) for the asset.
+A SPV is a legal entity that is created to hold the real world asset such as a US treasury bill.
+For the sake of easily remembering the SPV let's name it 'SPV A'.
 
 ![Create a new SPV](./images/Create-SPV.gif)
 
@@ -94,9 +90,9 @@ Your new asset should look like this:
 
 ### Add a transaction to the asset
 
-We're now going to add a transaction to the asset and therefor simulate an arranger borrowing $10,000,000 through a loan from Sky to purchase the asset. 
+We're now going to add a transaction to the asset and therefor simulate an arranger borrowing $10,000,000 through a loan from Sky to purchase the asset.
 
-To do this, move to the transaction tab and click on the 'create transaction' button below the table. 
+To do this, move to the transaction tab and click on the 'create transaction' button below the table.
 
 Fill in the following details to complete the transaction of $10,000,000 from Sky to the SPV, known as a principal draw.
 
@@ -113,7 +109,7 @@ You'll now see the transaction appear in the transaction table.
 
 ### Let's buy and sell some T-bills!
 
-Now that we've created the T-bill asset and took out a loan from Sky to purchase it, we can start buying some T-bills. 
+Now that we've created the T-bill asset and took out a loan from Sky to purchase it, we can start buying some T-bills.
 Let's buy 2,500,000 T-bills for $2,490,000 on May 15.
 
 Create a new transaction and fill in the following details:
@@ -136,7 +132,7 @@ Create a new transaction and fill in the following details:
 - Asset name: T-Bill 4565446 - US0045654460 - TB4565446
 - Quantity: 2,000,000
 - Asset proceeds: $1,995,000
-- Transaction reference: 0x123456789 
+- Transaction reference: 0x123456789
 
 Click on the 'Save' button to save the transaction.
 
@@ -157,7 +153,7 @@ Your table of transactions should now look like this:
 
 ![RWA Portfolio](./images/Transaction-table.png)
 
-### Verify that the document data is correctly entered and inspect the document history		
+### Verify that the document data is correctly entered and inspect the document history
 
 Connect offers you with a few ways to inspect the document data and history. Click on the 'revision history' button in the top right corner of your document model in Connect to see the history of your operations on the document model.
 
@@ -168,6 +164,6 @@ This allows you to inspect the document data and history in a structured way. Cu
 
 To inspect the document data, click on the 'Switchboard' icon in the top right corner of your document model in Connect.
 
-This will open a new tab with the graphql interface to the document model. If you click 'run' the base query will be executed and you'll see the document data and history. You'll find all the transactions we've added to the asset in the document model previously. 
+This will open a new tab with the graphql interface to the document model. If you click 'run' the base query will be executed and you'll see the document data and history. You'll find all the transactions we've added to the asset in the document model previously.
 
-Now let's move on to the next step where we'll update the analytics processor code to listen to the document model and calculate the total value of the asset class on a monthly basis.
+Now let's move on to the next step where we'll update the analytics processor code to listen to the document model and calculate the total value of the asset class on a monthly basis.

package/docs/academy/02-MasteryTrack/04-WorkWithData/_ARCHIVE-AnalyticsProcessorTutorial/_04-UpdateAnalyticsProcessor.md

@@ -7,7 +7,7 @@ You will likely already be in the desired directory, but if not, navigate to the
 cd rwa-analytics
 ```
 
-Now open the directory with your code editor. 
+Now open the directory with your code editor.
 
 ```bash
 code .
@@ -23,9 +23,7 @@ import {
   type IAnalyticsStore,
   AnalyticsSeriesInput,
 } from "@powerhousedao/reactor-api";
-import {
-  CreateGroupTransactionInput,
-} from "document-model-libs/real-world-assets";
+import { CreateGroupTransactionInput } from "document-model-libs/real-world-assets";
 import { DateTime } from "luxon";
 import { IProcessor } from "document-drive/processors/types";
 import { InternalTransmitterUpdate } from "document-drive/server/listener/transmitter/internal";
@@ -35,10 +33,10 @@ export class RwaAnalyticsProcessor implements IProcessor {
   constructor(private readonly analyticsStore: IAnalyticsStore) {
     //
   }
-  
+
   // This is the function that is called when the processor receives a new strand.
   async onStrands<TDocument extends PHDocument>(
-    strands: InternalTransmitterUpdate<TDocument>[]
+    strands: InternalTransmitterUpdate<TDocument>[],
   ): Promise<void> {
     if (strands.length === 0) {
       return;
@@ -60,12 +58,13 @@ export class RwaAnalyticsProcessor implements IProcessor {
         `ph/${strand.driveId}/${documentId}/${strand.branch}/${strand.scope}`,
       );
 
-      if (firstOp.index === 0) { // This is the index of the operation in the strand.
+      if (firstOp.index === 0) {
+        // This is the index of the operation in the strand.
         // This is the function that clears the source of the operation since there could be data existing from previous runs for the same document to avoid double counting.
         await this.analyticsStore.clearSeriesBySource(source, true);
       }
 
-      for (const operation of strand.operations) {	
+      for (const operation of strand.operations) {
         // This is the type of the operation that is being displayed in the terminal.
         console.log(">>> ", operation.type);
 
@@ -87,16 +86,15 @@ export class RwaAnalyticsProcessor implements IProcessor {
           }
 
           // Up next we'll go through the crucial design decision of defining the different dimensions or categories that are relevant to our analytics and queries. In this case we'll create 2 series values for each transaction type. Cash and Fixed Income transactions.
-          const { fixedIncomeTransaction, cashTransaction } =
-            groupTransaction;
+          const { fixedIncomeTransaction, cashTransaction } = groupTransaction;
 
           if (fixedIncomeTransaction) {
             const dimensions = {
               // We're selecting T-bills as one of the dimensions.
               asset: AnalyticsPath.fromString(
-                `sky/rwas/assets/t-bills/${fixedIncomeTransaction.assetId}`
+                `sky/rwas/assets/t-bills/${fixedIncomeTransaction.assetId}`,
               ),
-              // We're selecting the portfolio as another dimension.	
+              // We're selecting the portfolio as another dimension.
               portfolio: AnalyticsPath.fromString(
                 `sky/rwas/portfolios/${documentId}`,
               ),
@@ -104,9 +102,9 @@ export class RwaAnalyticsProcessor implements IProcessor {
 
             values.push({
               dimensions,
-              metric: "AssetBalance",	// We're selecting the AssetBalance metric.
+              metric: "AssetBalance", // We're selecting the AssetBalance metric.
               source,
-              start: DateTime.fromISO(fixedIncomeTransaction.entryTime),	// We're selecting the entryTime as the start of the series value.
+              start: DateTime.fromISO(fixedIncomeTransaction.entryTime), // We're selecting the entryTime as the start of the series value.
               value:
                 groupTransaction.type === "AssetPurchase"
                   ? fixedIncomeTransaction.amount
@@ -125,14 +123,14 @@ export class RwaAnalyticsProcessor implements IProcessor {
 
             values.push({
               dimensions,
-              metric: "AssetBalance",	// We're selecting the AssetBalance metric for our tutorial scenario
+              metric: "AssetBalance", // We're selecting the AssetBalance metric for our tutorial scenario
               source,
-              start: DateTime.fromISO(cashTransaction.entryTime),	// We're selecting the entryTime as the start of the series value.
+              start: DateTime.fromISO(cashTransaction.entryTime), // We're selecting the entryTime as the start of the series value.
               value:
                 groupTransaction.type === "AssetPurchase" ||
                 groupTransaction.type === "PrincipalReturn"
-                  ? -cashTransaction.amount	
-                  : cashTransaction.amount,	
+                  ? -cashTransaction.amount
+                  : cashTransaction.amount,
             });
           }
         }
@@ -157,7 +155,7 @@ You'll need to use this specific endpoint to access the graphql playground `http
 Then, use this query to get the data from the analytics store, but don't forget to also add the variables below.
 
 ```graphql
-query analytics ($filter: AnalyticsFilter) {
+query analytics($filter: AnalyticsFilter) {
   analytics {
     series(filter: $filter) {
       start
@@ -174,7 +172,8 @@ query analytics ($filter: AnalyticsFilter) {
   }
 }
 ```
-With the following variables: 
+
+With the following variables:
 
 ```graphql
 {
@@ -190,11 +189,11 @@ With the following variables:
         "select": "sky"
       }
     ]
-  }  
+  }
 }
 ```
 
-You'll see that the data is now being displayed per month for each of the asset classes. 
+You'll see that the data is now being displayed per month for each of the asset classes.
 
 `sum`: Displays the total cumulative sum of the asset class for the month.
 
@@ -208,10 +207,10 @@ When you play around with the variables of our query you can see the different g
 
 If you would take 'total' you would see the total value left in the portfolio.
 
-To see more changes become present in the analytics store, you could add more transactions to the portfolio. We could do this by adding a rwa portfolio with a different documentId. 
-Imagine that this is similar to real time updates that might happen to a live environment when new transactions are added to a porftolio. 
+To see more changes become present in the analytics store, you could add more transactions to the portfolio. We could do this by adding a rwa portfolio with a different documentId.
+Imagine that this is similar to real time updates that might happen to a live environment when new transactions are added to a porftolio.
 
-Now you know how to implement a custom analytics processor and how to query the data from the analytics store! 
+Now you know how to implement a custom analytics processor and how to query the data from the analytics store!
 In case you'd want to try it out on another document model follow the steps below.
 
 1. Generate the processor
@@ -220,4 +219,4 @@ In case you'd want to try it out on another document model follow the steps belo
 4. Launch the reactor (again) and add your data
 5. Query the data from the analytics store
 
-Enjoy! 
+Enjoy!

package/docs/academy/02-MasteryTrack/04-WorkWithData/_ARCHIVE-AnalyticsProcessorTutorial/_category_.json

@@ -5,4 +5,4 @@
     "type": "generated-index",
     "description": "Learn how to make use of an Analytics Processor in this tutorial!"
   }
-}
+}

package/docs/academy/02-MasteryTrack/04-WorkWithData/_category_.json

@@ -1,8 +1,8 @@
 {
-    "label": "Work with Data",
-    "position": 5,
-    "link": {
-      "type": "generated-index",
-      "description": "Learn how to work with data in Powerhouse."
-    }
-  }
+  "label": "Work with Data",
+  "position": 5,
+  "link": {
+    "type": "generated-index",
+    "description": "Learn how to work with data in Powerhouse."
+  }
+}

package/docs/academy/02-MasteryTrack/05-Launch/01-IntroductionToPackages.md

@@ -18,10 +18,9 @@ By packaging document models together, developers can create well-organized, int
 - **Contributor Billing Package** – Defines document models for tracking work, invoicing, and facilitating payments (in both fiat and crypto) for contributors in decentralized organizations. link
 - **Governance Package** – Models for proposals, voting, contributor agreements, and decision-making processes. link
 - **People Ops Package** – Documents managing contributor profiles, roles, task assignments, and reputation tracking. link
-- **Project Management Package** – Models for task tracking, milestones, resource allocation, and deliverables. link  
+- **Project Management Package** – Models for task tracking, milestones, resource allocation, and deliverables. link
 
-
-    A **Powerhouse Package** is a **modular unit** that defines and automates **data structures and workflows** within the Powerhouse ecosystem. Each package includes several components that work together to ensure **seamless interaction, data processing, and automation** for different areas of decentralized operations.
+  A **Powerhouse Package** is a **modular unit** that defines and automates **data structures and workflows** within the Powerhouse ecosystem. Each package includes several components that work together to ensure **seamless interaction, data processing, and automation** for different areas of decentralized operations.
 
 Packages follow a **scoped naming convention** based on the organization that owns them or created the package:
 
@@ -76,4 +75,4 @@ A **UI component** that allows users to **interact with document models visually
 
 ---
 
-Each of these modules plays a crucial role in making **Powerhouse Packages extensible, reusable, and efficient**, allowing developers and organizations to **streamline operations and automate workflows** within decentralized environments.
+Each of these modules plays a crucial role in making **Powerhouse Packages extensible, reusable, and efficient**, allowing developers and organizations to **streamline operations and automate workflows** within decentralized environments.

package/docs/academy/02-MasteryTrack/05-Launch/02-PublishYourProject.md

@@ -1,40 +1,42 @@
 # Publish your package
 
-This tutorial is a step by step guide tackling the following topics: 
-1. the process of **building a powerhouse project** 
+This tutorial is a step by step guide tackling the following topics:
+
+1. the process of **building a powerhouse project**
 2. the process of **publishing it as a package**
 
 :::info
 Let's start with some **key concepts** that will help you understand the process we're going to go through in this tutorial.
 
 - **Powerhouse Project**: The construction site of your package: A project is built with document models and editors which you will publish to NPM as a package with modules.
-- **Powerhouse Modules**: The modules that are part of your project, such as the document models, editors, processors or scripts. 
-- **Powerhouse Drive Apps**: Customized drive interfaces that function as a drive add and enhance or augment the functionality of your documents and workflows within the drive. 
+- **Powerhouse Modules**: The modules that are part of your project, such as the document models, editors, processors or scripts.
+- **Powerhouse Drive Apps**: Customized drive interfaces that function as a drive add and enhance or augment the functionality of your documents and workflows within the drive.
 - **Powerhouse Package**: A package is a collection of modules that are published to NPM and can be installed on a server instance or locally on your machine with help of the host apps such as Connect, Switchboard & Fusion. Organizations build packages for specific purposes or workflows.
 
 ![Key Concepts](images/keyconcepts.png)
 :::
 
-
-## 1. Building your project 
+## 1. Building your project
 
 To start building your project with it's dedicated document models and editors we'll run the following command:
 
-  ```bash
-   ph init
-   ```
+```bash
+ ph init
+```
 
 <details>
 <summary> Command not working? Did you install `ph-cmd`? </summary>
 
 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:
+
 ```bash
 pnpm install -g ph-cmd
-``` 
+```
 
-For experimental features, use --version [version] which allows selecting a specific branch of our document-model-boilerplate. There are --dev and --staging options. Select `ph init --dev` to use the latest development version. Please be aware that this version can contain bugs and experimental features that aren't fully tested.  
+For experimental features, use --version [version] which allows selecting a specific branch of our document-model-boilerplate. There are --dev and --staging options. Select `ph init --dev` to use the latest development version. Please be aware that this version can contain bugs and experimental features that aren't fully tested.
 
 Key commands include:
+
 - `ph connect` for running the Connect application locally
 - `ph switchboard` or `ph reactor` for starting the API service
 - `ph init` to start a new project and build a document model
@@ -64,6 +66,7 @@ yarn cache list
 yarn cache clean --force
 yarn cache list
 ```
+
 </details>
 
 <details>
@@ -71,35 +74,36 @@ yarn cache list
 
 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 |
+| 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>
 
 ### 1.1. Specifying your project details
 
-When you are creating your own project, you will be asked to name your project. 
+When you are creating your own project, you will be asked to name your project.
 Which will also become the package name when someone else wants to install it in a cloud environment via npm in the future.
 
 Please feel free to navigate to the package.json file and fill in all the other available fields such as `name`, `version`, `author`, `license` and `main`.
 
-  ```bash
-{  
-"name": "@your-org-ph/package-name",  #Your organization name with the -ph suffix to indicate it's a powerhouse related organization & package. 
-"version": "1.0.0", 
+```bash
+{
+"name": "@your-org-ph/package-name",  #Your organization name with the -ph suffix to indicate it's a powerhouse related organization & package.
+"version": "1.0.0",
 "author": "Your Name",
 "license": "AGPL-3.0-only",
-"main": "index.js"  
+"main": "index.js"
 }
 ```
 
@@ -108,17 +112,19 @@ Now that you've created your powerhouse project you are ready to generate the ne
 ```bash
 ph generate
 ```
-The **generate** command will start the configuration of your powerhouse project and generates a directory with the necessary files and folders to build your project. 
+
+The **generate** command will start the configuration of your powerhouse project and generates a directory with the necessary files and folders to build your project.
 These include:
+
 - `document-models`: A folder containing the document models schemas you've defined in Connect Studio Mode.
-- `editors`: A folder containing the editors you've defined in react, potentially making use of the reusable components. 
-- `processors`: A folder containing the processors you might be running on your document models later on. 
+- `editors`: A folder containing the editors you've defined in react, potentially making use of the reusable components.
+- `processors`: A folder containing the processors you might be running on your document models later on.
 - `scripts`: A folder containing the scripts you might use.
 - `tests`: A folder containing your unit tests.
 
 ### 1.2. Adding document models, editors and unit tests
 
-Now that you've set up your directory. 
+Now that you've set up your directory.
 Go ahead and add the document models you'd like to add by going through the standard document model building flow:
 
 :::info
@@ -134,9 +140,11 @@ These steps are explained more in depth in any of our tutorials. Follow along wi
 7. Add a **manifest file** to your project and updating your index.js file to export your modules.
 
 ### 1.3. Verifying your project
-Now that we've completed our directory with the reducers, tests and editors, and your project is populated with modules we'll verify the build output and see if everything is working correctly. 
+
+Now that we've completed our directory with the reducers, tests and editors, and your project is populated with modules we'll verify the build output and see if everything is working correctly.
 
 Let's **verify the package build output** with the following command:
+
 ```bash
 pnpm build
 ```
@@ -145,7 +153,7 @@ This command will **build** the project and create a build directory with the ou
 
 This command will **start a local server** and serve the build output.
 Inspect the build output and verify that the document models are working correctly.
-Instead of `pnpm serve`, we'll be using: 
+Instead of `pnpm serve`, we'll be using:
 
 ```bash
 ph connect
@@ -154,7 +162,8 @@ ph connect
 ### 1.4 Storing your project in a git repository
 
 Now that you've verified your project is working correctly, you can store your project in a git repository.
-Why? 
+Why?
+
 - So you can track the changes of your project in a remote repository and benefit from the collaboration features of git.
 - So you can publish your project to the npm registry and install it on a server instance or locally on your machine.
 
@@ -172,24 +181,29 @@ This will initialize a git repository and add all the files to the repository.
 
 For this step you'll need to register your organization on npm.
 If you haven't already registered your organization on npm, you can do so by running the following command:
+
 ```bash
 pnpm adduser
 ```
+
 Create an organization on [NPM](https://www.npmjs.com/) using the naming convention: `@yourorganization-ph`
-   - The `-ph` suffix indicates its a Powerhouse ecosystem package to help you and others identify it from regular NPM packages. 
-   - Example: `@acme-ph`
+
+- The `-ph` suffix indicates its a Powerhouse ecosystem package to help you and others identify it from regular NPM packages.
+- Example: `@acme-ph`
 
 To make sure you can differentiate between Powerhouse ecosystem packages and other packages we recommend setting up a separate npm account for your organization with the -ph suffix. **example: @yourorg-ph**
 We advise you to **use a dedicated npm account for your organization and not your personal account**.
 
-Once you've registered your organization on npm, you can now publish your project to the npm registry. 
+Once you've registered your organization on npm, you can now publish your project to the npm registry.
 Log in via the command line:
+
 ```bash
 npm login
 ```
-You'll be prompted for your username, password, and email in a separate browser window. 
 
-Once you've logged in, you can configure your package.json for npm before publishing. 
+You'll be prompted for your username, password, and email in a separate browser window.
+
+Once you've logged in, you can configure your package.json for npm before publishing.
 If you're publishing a package under a scope (like @your-org/my-package), you might need to add the `publishConfig` to ensure it's public, otherwise scoped packages default to private:
 
 ```json
@@ -210,6 +224,7 @@ Before publishing, it's crucial to version your package correctly and tag the re
 #### 1. Versioning with pnpm
 
 Use the `pnpm version` command to update your package version according to semantic versioning rules (`patch` for bugfixes, `minor` for new features, `major` for breaking changes). This command will:
+
 - Update the `version` in your `package.json`.
 - Create a Git commit for the version change.
 - Create a Git tag for the new version (e.g., `v1.0.1`).
@@ -224,6 +239,7 @@ pnpm version minor
 # For a major release (e.g., from 1.1.0 to 2.0.0)
 pnpm version major
 ```
+
 Take note of the new version tag created (e.g., `v1.0.1`), as you'll need it in the next step.
 
 #### 2. Pushing changes to Git
@@ -239,9 +255,11 @@ git push origin main
 # Replace vX.Y.Z with the actual tag name (e.g., v1.0.1)
 git push origin vX.Y.Z
 ```
+
 The specific tag name (e.g., `v1.0.1`) is usually output by the `pnpm version` command. Pushing the specific tag is recommended to avoid unintentionally pushing other local tags.
 
 Alternatively, to push all new local tags (use with caution):
+
 ```bash
 # git push --tags
 ```
@@ -250,10 +268,10 @@ Alternatively, to push all new local tags (use with caution):
 
 It's important to distinguish between Git tags and NPM distributor tags (dist-tags):
 
--   **Git Tags**: These are markers in your Git repository's history. They are primarily for developers to pinpoint specific release versions in the codebase (e.g., `v1.0.0`, `v1.0.1`). The `pnpm version` command creates these.
--   **NPM Distributor Tags (dist-tags)**: These are labels used by the NPM registry to point to specific published versions of your package. Common NPM tags include:
-    -   `latest`: This is the default tag. When someone runs `pnpm install my-package`, NPM installs the version tagged as `latest`.
-    -   `beta`, `next`, `alpha`: Often used for pre-release versions.
+- **Git Tags**: These are markers in your Git repository's history. They are primarily for developers to pinpoint specific release versions in the codebase (e.g., `v1.0.0`, `v1.0.1`). The `pnpm version` command creates these.
+- **NPM Distributor Tags (dist-tags)**: These are labels used by the NPM registry to point to specific published versions of your package. Common NPM tags include:
+  - `latest`: This is the default tag. When someone runs `pnpm install my-package`, NPM installs the version tagged as `latest`.
+  - `beta`, `next`, `alpha`: Often used for pre-release versions.
     When you publish a package without specifying an NPM tag, it usually gets the `latest` tag by default.
 
 #### 4. Publishing to npm
@@ -263,23 +281,28 @@ Now you are ready to publish your package to the NPM registry. Ensure you are lo
 ```bash
 pnpm publish
 ```
+
 This command will publish the version of your package that is currently specified in your `package.json`. By default, this will also set the `latest` NPM dist-tag for this version.
 
 If your package is scoped (e.g., `@your-org/my-package`) and intended to be public, ensure your `package.json` includes the `publishConfig` shown earlier. If this is not set in `package.json` (and your package is scoped), you might need to use:
+
 ```bash
 pnpm publish --access public
 ```
 
 You can also publish a version to a specific NPM dist-tag. For example, to publish a beta version:
+
 ```bash
 # Ensure your package.json version reflects the beta (e.g., 1.1.0-beta.0)
 pnpm publish --tag beta
 ```
+
 This is useful for testing releases before making them `latest`.
 
 Now let's verify that the package(s) get published in the package repository, next to pre-existing packages that you might have been publishing before.
 
 ## 3. Deploying the host apps and project
+
 Now that we've installed all the necessary services on our server instance, we can start deploying the host apps & our packaged project from npm.
 
 Install your project package we've published earlier on your local connect (`ph connect`) instance by running the following command:
@@ -287,9 +310,10 @@ Install your project package we've published earlier on your local connect (`ph
 ```bash
 ph install @<your-org/package-name>
 ```
+
 Alternatively you can also install the package in the settings of Connect in the 'package manager' section. (Not available yet)
 Where you'll be able to use the same package name as you've used in the `package.json` file and install it at the click of a button.
 
 ![package manager](images/homedesign.png)
 
-Got this far? Congratulations on publishing your first package! 
+Got this far? Congratulations on publishing your first package!