@powerhousedao/academy 3.2.0-dev.3 → 3.2.0-dev.4

package/CHANGELOG.md

@@ -1,3 +1,13 @@
+## 3.2.0-dev.4 (2025-06-25)
+
+### 🚀 Features
+
+- added drive analytics processor ([#1607](https://github.com/powerhouse-inc/powerhouse/pull/1607))
+
+### ❤️ Thank You
+
+- Guillermo Puente Sandoval
+
 ## 3.2.0-dev.3 (2025-06-24)
 
 ### 🩹 Fixes

package/docs/academy/01-GetStarted/home.mdx

@@ -70,9 +70,9 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
       </h3>
     </div>
     <div className={styles.cardContent}>
-      <a href="/academy/GetStarted/BuildToDoListEditor" className="path-button">Building a todo-list editor</a>
-      <a href="/academy/MasteryTrack/BuildingUserExperiences/BuildingDocumentEditors" className="path-button">Building document editors</a>
-      <a href="/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer" className="path-button">Building custom drive explorers</a>
+      <a href="/academy/GetStarted/BuildToDoListEditor" className="path-button">Build a todo-list editor</a>
+      <a href="/academy/MasteryTrack/BuildingUserExperiences/BuildingDocumentEditors" className="path-button">Build document editors</a>
+      <a href="/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer" className="path-button">Build custom drive explorers</a>
       <a href="/academy/ComponentLibrary/DocumentEngineering" className="path-button">Component library</a>
     </div>
   </div>
@@ -98,9 +98,9 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
       </h3>
     </div>
     <div className={styles.cardContent}>
-      <a href="/academy/MasteryTrack/WorkWithData/ReadingAndWritingThroughTheAPI" className="path-button">Reading & writing through the API</a>
+      <a href="/academy/MasteryTrack/WorkWithData/ReadingAndWritingThroughTheAPI" className="path-button">Read & write through the API</a>
       <a href="/academy/MasteryTrack/WorkWithData/WorkingWithSubgraphs" className="path-button">Create your own subgraph</a>
-      <a href="/academy/MasteryTrack/WorkWithData/Analytics-Engine/intro" className="path-button">Using the analytics engine</a>
+      <a href="/academy/MasteryTrack/WorkWithData/Analytics-Engine/intro" className="path-button">Use the analytics engine</a>
     </div>
   </div>
 
@@ -116,7 +116,7 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
       <div className={styles.buttonContainer}>
         <a href="/academy/MasteryTrack/Launch/IntroductionToPackages" className="path-button">Intro to packages</a>
         <a href="/academy/MasteryTrack/Launch/PublishYourProject" className="path-button">Publish your project</a>
-        <a href="/academy/MasteryTrack/Launch/SetupEnvironment" className="path-button">Setup a cloud environment</a>
+        <a href="/academy/MasteryTrack/Launch/SetupEnvironment" className="path-button">Set-up a cloud environment</a>
       </div>
     </div>
   </div>

package/docs/academy/02-MasteryTrack/01-BuilderEnvironment/02-StandardDocumentModelWorkflow.md

@@ -1,8 +1,9 @@
 # Create Powerhouse packages
 
 :::warning
-**This tutorial is a summary for builders that are familiar with building document models**.    
-It guides you through creating a Powerhouse Document Model, from initial setup to publishing a distributable package. 
+**This tutorial is a summary for builders that are already familiar with building document models**.    
+It provides a summary from initial setup up to publishing a distributable package.    
+
 Please start with the '**Get Started**' Chapter or '**Document Model Creation**' section if you are unfamiliar with building a document model.
 :::
 

package/docs/academy/02-MasteryTrack/02-DocumentModelCreation/07-ExampleToDoListRepository.md

@@ -1,17 +1,17 @@
-# Example: Todo demo package
+# Example: Todo-demo-package
 
 :::info
 
-The ToDo Demo package is maintained by the Powerhouse Team and serves as a reference for testing and introducing new features. It will be continuously updated alongside the accompanying documentation.
+The Todo-demo-package is maintained by the Powerhouse Team and serves as a reference for testing and introducing new features. It will be continuously updated alongside the accompanying documentation.
 
 https://github.com/powerhouse-inc/todo-demo-package
 :::
 
 There are several ways to explore this package:
 
-### Option 1: Rebuild the todo demo package
+### Option 1: Rebuild the Todo-demo-package
 
-The ToDo Demo package and repository are your main reference points during the Mastery Track.  
+The Todo-demo-package and repository are your main reference points during the Mastery Track.  
 Follow the steps in the "Mastery Track – Document Model Creation" chapters to build along with the examples.
 
 ### Option 2: Clone and run the code locally

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

@@ -24,7 +24,7 @@ Powerhouse aims to keep your developer experience clean, familiar, and focused:
 To kickstart your editor development, Powerhouse provides a command to generate a basic editor template. This command reads your document model specifications and creates the initial `editor.tsx` file.
 If you want a refresher on how to define your document model specification please read the chapter on [specifying the State Schema](/academy/MasteryTrack/DocumentModelCreation/SpecifyTheStateSchema)
 
-For example, to generate an editor for a `To-do List` document model with a document type `powerhouse/todolist`:
+For example, to generate an editor for a To-do List document model with a document type `powerhouse/todolist`:
 ```bash
 ph generate --editor ToDoList --document-types powerhouse/todolist
 ```
@@ -40,7 +40,7 @@ You have several options for styling your editor components:
     *Example (from the ToDoList Editor):*
     ```typescript
     <div className="container mx-auto p-4 max-w-md">
-        <h1 className="text-2xl font-bold mb-4">To-do List</h1>
+        <h1 className="text-2xl font-bold mb-4">ToDoList</h1>
         {/* ... more Tailwind styled elements */}
     </div>
     ```
@@ -114,7 +114,7 @@ The actual state modification logic resides in your document model's reducers, e
 
 ## Powerhouse component library
 
-Powerhouse provides a rich set of reusable UI components through the **`@powerhousedao/document-engineering/scalars`** package. These components are designed for consistency, efficiency, and seamless integration with the Powerhouse ecosystem, with many based on GraphQL scalar types.
+Powerhouse provides a rich set of reusable UI components through the **`@powerhousedao/document-engineering/scalars`** package. These components are designed for consistency, efficiency, and seamless integration with the Powerhouse ecosystem, with many based on GraphQL scalar types. For more information read our chapter on the [Component Library](/academy/ComponentLibrary/DocumentEngineering)
 
 ### Exploring components
 You can explore available components, see usage examples, and understand their properties (props) using our Storybook instance:
@@ -261,7 +261,7 @@ export const InputField = (props: InputFieldProps) => {
 Below is the complete code for the To-Do List editor. It primarily uses Tailwind CSS for styling and imports the local `Checkbox` and `InputField` components you created in the previous step. These local components, in turn, utilize elements from the Powerhouse Document Engineering design system.
 
 <details>
-<summary>Complete To-do List Editor Example (using Tailwind CSS)</summary>
+<summary>Complete To-do list editor example (using Tailwind CSS)</summary>
 
 ```typescript
 import { EditorProps } from 'document-model'; // Core type for editor components.
@@ -502,5 +502,6 @@ The editor will update dynamically, so you can play around with your editor styl
 Congratulations!
 If you managed to follow this tutorial until this point, you have successfully implemented the **To-do List** document model with its reducer operations and editor. 
 
+## Up Next 
 Now you can move on to creating a [custom drive explorer](/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer) for your To-do List document.    
 Imagine you have many To-do Lists 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!

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

@@ -109,8 +109,6 @@ You can also add a new remote drive to your Connect environment programmatically
    }
    ```
 
-
-
 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`