Review of Chapter 11

Author: lcharette

app/pages/6.0/10.users/chapter.md

@@ -7,4 +7,10 @@ description: In this chapter, you'll learn about the various user account featur
 
 # Users
 
-In this chapter, you'll learn about the user and admin [account features](/users/user-accounts) that come built-in and fully implemented in UserFrosting, as well as UserFrosting's powerful [role-based access control system](/users/access-control).
+Every web application needs to know **who is using it**. User management covers fundamental questions: Who can access this? What can they do? How do we secure their credentials?
+
+Building user management from scratch is complex—you need authentication, secure password storage, sessions, password recovery, permissions, activity tracking, and privacy compliance. Getting it wrong creates security vulnerabilities.
+
+UserFrosting handles all this for you with a **complete built-in user management system**: user accounts, authentication, registration, password reset, email verification, and role-based access control (RBAC). Focus on your app's unique features while relying on UserFrosting's battle-tested foundation.
+
+This chapter covers [user and admin account features](/users/user-accounts) and UserFrosting's powerful [role-based access control system](/users/access-control) for defining who can do what.

app/pages/6.0/11.cli/01.commands/docs.md

@@ -1,7 +1,6 @@
 ---
 title: Built-in Commands
 description: An overview of the commands available in Bakery, UserFrosting's powerful CLI tool.
-wip: true
 ---
 
 Web applications need more than just a web interface. You need to run database migrations, clear caches, seed test data, build assets, and perform maintenance tasks. Doing these through a browser is awkward at best. Command-line tools are perfect for these tasks—fast, automatable, and scriptable.
@@ -79,6 +78,27 @@ The `assets:webpack` command is an alias for the **Webpack Encore** scripts used
 
 See the [Asset Management](/asset-management) chapter for more information about asset bundles and these options.
 
+### assets:vite
+
+The `assets:vite` command is an alias for the **Vite** scripts used to compile frontend dependencies to `/public/assets` or run the Vite development server. Behind the scenes, it's an alias for the npm commands `npm run vite:dev` and `npm run vite:build`. 
+
+```bash
+$ php bakery assets:vite [options]
+```
+
+| Option           | Description                                             | Alias of              |
+|------------------|---------------------------------------------------------|-----------------------|
+| _no options_     | Run Vite development server (when `assets.vite.dev` is `true`) or compile the assets for production (when `assets.vite.dev` is `false`)        | `npm run vite:dev` or `npm run vite:build` |
+| -p, --production | Force the creation of a production build                | `npm run vite:build`  |
+
+> [!NOTE]
+> The `assets.vite.dev` config value (default `true`) determines whether the Vite development server runs or a production build is created. In production mode, this defaults to `false`.
+
+> [!NOTE]  
+> This command will skip execution if no `vite.config.js` or `vite.config.ts` file is found in the current directory.
+
+See the [Asset Management](/asset-management) chapter for more information about Vite and asset bundles.
+
 ### bake
 
 Bake is the general installation command. It combines `setup:db`, `setup:mail`, `debug`, `migrate`, `create:admin-user`, `assets:build` and `clear-cache` into a single command:
@@ -355,6 +375,24 @@ $ php bakery migrate:status [options]
 | -d, --database=DATABASE | The database connection to use |
 
 
+### migrate:clean
+
+The `migrate:clean` command removes stale migrations from the migration repository (database). A migration becomes "stale" when it was previously run but its migration class file no longer exists in the codebase.
+
+> [!CAUTION]
+> This command should be used as a **last resort**. If a stale migration is a dependency of another migration, you should try restoring the migration files instead of running this command, to avoid further issues.
+
+```bash
+$ php bakery migrate:clean [options]
+```
+
+| Option                  | Description                            |
+| ----------------------- | -------------------------------------- |
+| -d, --database=DATABASE | The database connection to use         |
+| -f, --force             | Do not prompt for confirmation         |
+
+Common use case: If you ran a migration and then deleted the migration class file before running `down()` for that migration, the migration entry will remain in the database but cannot be rolled back. This command will remove such stale entries from the migration repository.
+
 ### route:list
 
 Display the list of all registered [routes](/routes-and-controllers/front-controller).

app/pages/6.0/11.cli/02.custom-commands/docs.md

@@ -1,7 +1,6 @@
 ---
 title: Custom Commands
 description: You may extend the UserFrosting\System\Bakery\BaseCommand class to implement your own CLI commands that can be run through Bakery.
-wip: true
 ---
 
 While the Bakery CLI tool comes with great built-in commands, your sprinkles can also take advantage of the Bakery by adding their own cli commands.

app/pages/6.0/11.cli/03.extending-commands/docs.md

@@ -1,14 +1,14 @@
 ---
 title: Extending Aggregator Commands
 description: You may add custom sub-commands to the bake, setup, and debug commands through events.
-wip: true
 ---
 
-*Aggregator commands* is a fancy term to identify core bakery commands that just run multiple sub-commands in one operation. UserFrosting uses 3 of those special commands:
+*Aggregator commands* is a fancy term to identify core bakery commands that just run multiple sub-commands in one operation. UserFrosting uses 4 of those special commands:
 
-1. [bake](/cli/commands#bake)
-2. [setup](/cli/commands#setup)
-3. [debug](/cli/commands#debug)
+1. [assets:build](/cli/commands#assetsbuild)
+2. [bake](/cli/commands#bake)
+3. [setup](/cli/commands#setup)
+4. [debug](/cli/commands#debug)
 
 Those commands are typically used as "installation" steps. It this situation, it's much more simpler to run one command than multiple ones. You can easily add your own command(s) to any of these aggregators using [event listeners](/advanced/events#listener).
 
@@ -89,6 +89,12 @@ If you need to place your command at a specific place in the stack, you can use
 > [!NOTE]
 > You can learn more about Event Listening in [Chapter 18](/advanced/events).
 
+## Adding Custom Commands to the `assets:build` command
+
+To add custom sub-commands to the `assets:build` aggregator, the same process as for the "bake" command can be used, but instead of listening to the `BakeCommandEvent` in the recipe, the listener is matched to the `AssetsBuildCommandEvent`.
+
+This is particularly useful if you want to add custom asset compilation steps. For example, you might want to run additional build tools or post-processing steps after the default asset build commands.
+
 ## Adding Custom Commands to the `setup` command
 
 To add custom sub-commands to the `setup` aggregator, the same process as for the "bake" command can be used, but instead of listening to the `BakeCommandEvent` in the recipe, the listener is matched to the `SetupCommandEvent`.

app/pages/6.0/11.cli/chapter.md

@@ -1,13 +1,14 @@
 ---
 title: Bakery CLI
 description: Bakery is UserFrosting's very own command line interface (CLI) tool.
-wip: true
 ---
 
 #### Chapter 11
 
 # Bakery CLI
 
-UserFrosting provides its own Command-line Interface tool, or CLI, called the **Bakery**.
+Many critical tasks need to happen outside the web request cycle—database migrations, asset compilation, cache clearing, and deployment automation can't wait for a page load or be safely exposed through a web interface.
 
-This tool allows you to run administrative commands like setting up your database, running tests, or debugging an existing installation.
+UserFrosting provides **Bakery**, a powerful command-line interface (CLI) built on the Symfony Console component. Bakery gives you pre-built commands for database migrations, user management, asset compilation, and debugging. You can also create custom commands and extend existing ones using UserFrosting's event system.
+
+This chapter covers [built-in commands](/cli/commands), [creating custom commands](/cli/custom-commands), and [extending commands](/cli/extending-commands).