Completely reorganize chapter order for better flow and understanding

Author: lcharette

app/pages/6.0/04.installation/03.basic-cli/docs.md

@@ -0,0 +1,124 @@
+---
+title: Basic CLI Usage
+description: Essential Bakery commands to get started with UserFrosting development.
+---
+
+Now that you have UserFrosting installed, it's important to understand how to use **Bakery**, the command-line interface (CLI) tool. You'll rely on Bakery throughout your development workflow—from starting the development server to managing your database and clearing caches. This page covers the essential commands you'll use most frequently. For a complete reference of all available commands and how to create your own, see the [Bakery CLI](/cli/) chapter.
+
+> [!NOTE]
+> All Bakery commands are executed in your **terminal** or **command prompt**—the same one you used during installation. Make sure you're in your project's root directory before running any commands.
+
+## Running Commands
+
+All Bakery commands are run from your project's root directory using:
+
+```bash
+php bakery <command>
+```
+
+You can see a list of all available commands by running:
+
+```bash
+php bakery list
+```
+
+For help with a specific command:
+
+```bash
+php bakery help <command>
+```
+
+## Essential Commands
+
+### Starting the Development Server
+
+The `serve` command starts UserFrosting's built-in development server:
+
+```bash
+php bakery serve
+```
+
+By default, this starts the server at `http://localhost:8080`. You can specify a different host and port:
+
+```bash
+php bakery serve --host=0.0.0.0 --port=8000
+```
+
+> [!WARNING]
+> The built-in server is for **development only**. Never use it in production. See the [Going Live](/going-live/) chapter for production deployment options.
+
+### Initial Setup
+
+When setting up a new project or after pulling updates, run the `bake` command to execute all setup tasks:
+
+```bash
+php bakery bake
+```
+
+This single command runs multiple setup operations:
+- Clears the cache
+- Runs database migrations
+- Compiles frontend assets
+- Sets up configuration files (on first run)
+
+For a fresh installation, you can also use the interactive setup wizard:
+
+```bash
+php bakery setup
+```
+
+This guides you through:
+1. Environment configuration (.env file)
+2. Database connection
+3. SMTP configuration (optional)
+4. Running migrations
+5. Creating the root user account
+
+### Database Migrations
+
+Run pending database migrations without the full bake process:
+
+```bash
+php bakery migrate
+```
+
+To see which migrations have been run or are pending:
+
+```bash
+php bakery migrate:status
+```
+
+### Clearing the Cache
+
+When you make configuration changes or template updates, clear the cache:
+
+```bash
+php bakery clear-cache
+```
+
+### Debugging Information
+
+Get helpful debugging information about your UserFrosting installation:
+
+```bash
+php bakery debug
+```
+
+This shows:
+- UserFrosting version
+- PHP version and configuration
+- Database connection status
+- Loaded sprinkles
+- Environment settings
+
+## What's Next?
+
+These commands will get you through most day-to-day development work. As you build your application, you'll discover many more commands for:
+
+- Creating and managing users
+- Running database seeders
+- Testing email configuration
+- Building and watching assets
+- Creating custom commands for your own tasks
+
+For a complete reference and advanced features, see the [Bakery CLI](/cli/) chapter.

…es/6.0/06.sprinkles/01.sprinkles/docs.md …es/6.0/05.sprinkles/01.sprinkles/docs.mdapp/pages/6.0/06.sprinkles/01.sprinkles/docs.md renamed to app/pages/6.0/05.sprinkles/01.sprinkles/docs.md app/pages/6.0/06.sprinkles/01.sprinkles/docs.md renamed to app/pages/6.0/05.sprinkles/01.sprinkles/docs.md

@@ -83,7 +83,7 @@ The `locale` directory contains [translation files](/i18n) for your sprinkle. Li
 
 Just as with configuration files, UserFrosting will recursively merge translation files for the currently selected language(s) from each loaded sprinkle. This means that each subsequently loaded sprinkle can override translations from previous sprinkles, or define new ones entirely.
 
-See [Chapter 17](/i18n) for more information on UserFrosting's internationalization and localization system.
+See [Chapter 18](/i18n) for more information on UserFrosting's internationalization and localization system.
 
 ### /app/logs
 

…ages/6.0/06.sprinkles/02.content/docs.md …ages/6.0/05.sprinkles/02.content/docs.mdapp/pages/6.0/06.sprinkles/02.content/docs.md renamed to app/pages/6.0/05.sprinkles/02.content/docs.md app/pages/6.0/06.sprinkles/02.content/docs.md renamed to app/pages/6.0/05.sprinkles/02.content/docs.md

@@ -198,7 +198,7 @@ The available sub-recipes includes:
 | [SeedRecipe](#seedrecipe)                   | Registering [Seeds](/database/seeding)                                                               |
 | [MiddlewareRecipe](#middlewarerecipe)       | Registering [Middlewares](/advanced/middlewares)                                                     |
 | [EventListenerRecipe](#eventlistenerrecipe) | Registering [Event Listeners](/advanced/events)                                                     |
-| [TwigExtensionRecipe](#twigextensionrecipe) | Registering [Twig Extension](/templating-with-twig/filters-and-functions#extending-twig-extensions) |
+| [TwigExtensionRecipe](#twigextensionrecipe) | Registering [Twig Extension](/pages-and-layout/filters-and-functions#extending-twig-extensions) |
 
 Your recipe simply needs to implement the corresponding interface. Classes may implement more than one interface if desired by separating each interface with a comma. For example :
 
@@ -316,7 +316,7 @@ Methods to implement :
 Interface : `UserFrosting\Sprinkle\Core\Sprinkle\Recipe\TwigExtensionRecipe`
 
 Methods to implement :
-- `getTwigExtensions` : Return a list of [Twig Extension](/templating-with-twig/filters-and-functions#extending-twig-extensions) classes
+- `getTwigExtensions` : Return a list of [Twig Extension](/pages-and-layout/filters-and-functions#extending-twig-extensions) classes
 
     **Example:**
     ```php

…pages/6.0/06.sprinkles/03.recipe/docs.md …pages/6.0/05.sprinkles/03.recipe/docs.mdapp/pages/6.0/06.sprinkles/03.recipe/docs.md renamed to app/pages/6.0/05.sprinkles/03.recipe/docs.md app/pages/6.0/06.sprinkles/03.recipe/docs.md renamed to app/pages/6.0/05.sprinkles/03.recipe/docs.md

@@ -48,7 +48,7 @@ If the sprinkle includes frontend assets like JavaScript, TypeScript, or Vue com
     },
 ```
 
-You may also need to configure Vite to properly handle the sprinkle's assets. See [Chapter 13](/asset-management) for more information about managing assets with Vite.
+You may also need to configure Vite to properly handle the sprinkle's assets. See [Chapter 14](/assets-vite) for more information about managing assets with Vite.
 
 > [!TIP]
 > In the `package.json` example above, we're loading the Userfrosting core sprinkles from npm, and the Owlery sprinkle from Github. Each community sprinkle decides where it is published, and should include this in their README.

…es/6.0/06.sprinkles/04.customize/docs.md …es/6.0/05.sprinkles/04.customize/docs.mdapp/pages/6.0/06.sprinkles/04.customize/docs.md renamed to app/pages/6.0/05.sprinkles/04.customize/docs.md app/pages/6.0/06.sprinkles/04.customize/docs.md renamed to app/pages/6.0/05.sprinkles/04.customize/docs.md

@@ -3,7 +3,7 @@ title: Sprinkles
 description: Sprinkles are modular units of code and content that implement some feature or override some default behavior of UserFrosting.
 ---
 
-#### Chapter 6
+#### Chapter 5
 
 # Sprinkles
 

…es/6.0/06.sprinkles/05.community/docs.md …es/6.0/05.sprinkles/05.community/docs.mdapp/pages/6.0/06.sprinkles/05.community/docs.md renamed to app/pages/6.0/05.sprinkles/05.community/docs.md app/pages/6.0/06.sprinkles/05.community/docs.md renamed to app/pages/6.0/05.sprinkles/05.community/docs.md

@@ -15,11 +15,11 @@ Third party services are also used directly throughout the code. They can be inj
 
 ### `UserFrosting\Alert\AlertStream`
 
-This service handles the [alert message stream](/advanced/alert-stream), sometimes known as "flash messages". (See Chapter 18 for more information.)
+This service handles the [alert message stream](/advanced/alert-stream), sometimes known as "flash messages". (See Chapter 19 for more information.)
 
 ### `Illuminate\Cache\Repository as Cache`
 
-Creates an instance of a Laravel [Cache](https://laravel.com/docs/8.x/cache). See [Chapter 17](/advanced/caching) for more information.
+Creates an instance of a Laravel [Cache](https://laravel.com/docs/8.x/cache). See [Chapter 19](/advanced/caching) for more information.
 
 ### `UserFrosting\Config\Config`
 
@@ -61,7 +61,7 @@ Monolog `Logger` object for logging successfully completed database queries to `
 
 ### `UserFrosting\Sprinkle\Core\Mail\Mailer`
 
-Creates an instance of `Mailer`, which serves as a UF-compatible wrapper for a [PHPMailer](https://github.com/PHPMailer/PHPMailer) object. See [Chapter 14](/mail) for more information.
+Creates an instance of `Mailer`, which serves as a UF-compatible wrapper for a [PHPMailer](https://github.com/PHPMailer/PHPMailer) object. See [Chapter 17](/mail) for more information.
 
 ### `League\CommonMark\ConverterInterface`
 
@@ -98,7 +98,7 @@ See [Templating with Twig](/templating-with-twig) for more information about Twi
 
 ### `UserFrosting\ViteTwig\ViteManifestInterface`
 
-Provides integration with Vite for frontend asset management. This service reads the Vite manifest file and provides methods to generate asset URLs with proper cache busting. See [Chapter 13](/asset-management) for more information.
+Provides integration with Vite for frontend asset management. This service reads the Vite manifest file and provides methods to generate asset URLs with proper cache busting. See [Chapter 14](/assets-vite) for more information.
 
 ### `Symfony\WebpackEncoreBundle\Asset\EntrypointLookupInterface`