@powerhousedao/academy 2.5.0-dev.28 → 2.5.0-dev.29

package/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 2.5.0-dev.29 (2025-06-17)
+
+This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
+
 ## 2.5.0-dev.28 (2025-06-16)
 
 ### 🚀 Features

package/docs/academy/02-MasteryTrack/02-DocumentModelCreation/02-SpecifyTheStateSchema.md

@@ -141,5 +141,5 @@ By completing these steps, you have successfully specified the data structure fo
 
 </details>
 
-For a complete, working example, you can always refer to the [Example ToDoList Repository](./ExampleToDoListRepository.md) which contains the full implementation of the concepts discussed in this Mastery Track.
+For a complete, working example, you can always refer to the [Example ToDoList Repository](/academy/MasteryTrack/DocumentModelCreation/ExampleToDoListRepository) which contains the full implementation of the concepts discussed in this Mastery Track.
 

package/docs/academy/02-MasteryTrack/02-DocumentModelCreation/03-SpecifyDocumentOperations.md

@@ -115,7 +115,7 @@ export const reducer: ToDoListToDoListOperations = {
 Now that you understand the theory, let's walk through the practical steps of defining these operations for our `ToDoList` document model within the Powerhouse Connect application.
 
 <details>
-<summary>Tutorial: Specifying `ToDoList` Operations</summary>
+<summary>Tutorial: Specifying ToDoList Operations</summary>
 
 Assuming you have already defined the state schema for the `ToDoList` as covered in the previous section, follow these steps to add the operations:
 

package/docs/academy/02-MasteryTrack/02-DocumentModelCreation/04-UseTheDocumentModelGenerator.md

@@ -95,7 +95,7 @@ Leveraging the `ph generate` command offers numerous advantages:
 Now that you understand what the Document Model Generator does, let's walk through the practical steps of using it with our `ToDoList` example.
 
 <details>
-<summary>Tutorial: Generating the `ToDoList` Document Model</summary>
+<summary>Tutorial: Generating the ToDoList Document Model</summary>
 
 This tutorial assumes you have completed the previous steps in this Mastery Track, where you defined the state schema and operations for the `ToDoList` model in Connect and exported it.
 

package/docs/academy/02-MasteryTrack/02-DocumentModelCreation/05-ImplementDocumentReducers.md

@@ -237,7 +237,7 @@ Using these types provides:
 Now that you understand the principles, let's put them into practice by implementing the reducers for our `ToDoList` document model.
 
 <details>
-<summary>Tutorial: Implementing the `ToDoList` Reducers</summary>
+<summary>Tutorial: Implementing the ToDoList Reducers</summary>
 
 This tutorial assumes you have followed the steps in the previous chapters, especially using `ph generate ToDoList.phdm.zip` to scaffold your document model's code.
 

package/docs/academy/02-MasteryTrack/02-DocumentModelCreation/06-ImplementDocumentModelTests.md

@@ -134,5 +134,6 @@ Implementing comprehensive tests for your document model reducers is an investme
 By following the tutorial and applying these best practices, you can build a strong suite of tests that safeguard the integrity and functionality of your document models. This diligence is a hallmark of a "Mastery Track" developer, ensuring that the solutions you build are not just functional but also stable, maintainable, and trustworthy.
 
 ## Up Next
-In the next chapter of the Mastery Track you will learn how to implement an editor for your document model so you can see a simple user interface for the **ToDoList** document model in action.
-For a complete, working example, you can always refer to the [Example ToDoList Repository](./ExampleToDoListRepository.md) which contains the full implementation of the concepts discussed in this Mastery Track.
+In the next chapter of the Mastery Track - Building User Experiences you will learn how to implement an editor for your document model so you can see a simple user interface for the **ToDoList** document model in action.
+
+For a complete, working example, you can always refer to the [Example ToDoList Repository](/academy/MasteryTrack/DocumentModelCreation/ExampleToDoListRepository) which contains the full implementation of the concepts discussed in this Mastery Track.

package/docs/academy/02-MasteryTrack/03-BuildingUserExperiences/01-BuildingDocumentEditors.md

@@ -1,4 +1,4 @@
-# Build Document Editors (WIP)
+# Build Document Editors
 
 ## Build with React on Powerhouse
 
@@ -499,10 +499,10 @@ Click on it to create a new ToDoList document.
 The editor will update dynamically, so you can play around with your editor styling while seeing your results appear in Connect Studio. 
 :::
 
+</details>
+
 Congratulations!
 If you managed to follow this tutorial until this point, you have successfully implemented the **ToDoList** document model with its reducer operations and editor. 
 
 Now you can move on to creating a [custom drive explorer](/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer) for your ToDoList document.    
 Imagine you have many ToDoLists sitting in a drive. A custom drive explorer will allow you to organize and track them at a glance, opening up a new world of possibilities to increase the functionality of your documents!
-
-</details>

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

@@ -2,12 +2,13 @@
 
 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.   
 
-## Prerequisites
+:::info **Prerequisites**
 
 Before configuring a drive, ensure you have:
 - Powerhouse [CLI installed](/academy/MasteryTrack/BuilderEnvironment/BuilderTools)
 - Access to a Powerhouse instance
 - Appropriate permissions to create and manage drives
+:::
 
 ## Understanding Drives
 
@@ -23,7 +24,7 @@ Remote drives in Powerhouse allow you to connect to and work with data stored in
 - **Cloud Storage**: For centralized, scalable data management.
 - **Decentralized Storage**: Such as Ceramic or IPFS, enabling distributed and blockchain-based storage options.
 
-:::tip
+:::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. 
 
@@ -57,10 +58,11 @@ To create a new drive in Powerhouse, follow these steps:
 
 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.
 
-### Prerequisites
+:::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).
 - Appropriate permissions to perform mutations.
+:::
 
 ### Steps
 1. **Navigate to the GraphQL Playground or use a GraphQL client**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@powerhousedao/academy",
-  "version": "2.5.0-dev.28",
+  "version": "2.5.0-dev.29",
   "homepage": "https://powerhouse.academy",
   "repository": {
     "type": "git",