Update all commands

Author: cezaraugusto

docs/en/docs/commands/build.mdx

@@ -110,7 +110,7 @@ In this example, the build targets all supported browsers and includes polyfills
 
 ## Best Practices
 
-- **Check Build Logs:** After the build, review the logs to ensure there are no warnings or errors. The build logs will highlight any issues with compatibility or missing assets.
+- **Check Build Logs:** After the build, review the logs to ensure there are no warnings or errors. The build logs will highlight any issues with missing assets.
 - **Optimize Your Manifest:** Ensure that your `manifest.json` is optimized and fully compatible with all targeted browsers to avoid build issues.
 - **Custom Build Artifacts:** You can define custom names for your build artifacts using the `--zip-filename` option, which is useful for organizing builds.
 

docs/en/docs/commands/create.mdx

@@ -1,21 +1,30 @@
 import { PackageManagerTabs } from "@theme";
 import { AvatarImage } from "../../../../theme/components/avatar-image";
+import {CarouselTemplates} from "../../../../theme/components/carousel-templates";
 
 <AvatarImage icon="extension" />
 
 # Create Command
 
-The `create` command is responsible for setting up a new browser extension project using Extension.js.
+The `create` command is **responsible** for setting up a new browser extension project using Extension.js.
 This command accepts flags like `--template` for initializing your extension with various templates,
 and allows you to define the directory or path where the extension will be created.
 The command is designed to simplify the setup process for developers,
 providing a streamlined way to get started with cross-browser extension development.
 
+## How it Works?
+
+![Create Command](https://github.com/user-attachments/assets/666c4f07-7303-4bdc-971f-9c3684adb06f)
+
+Given a folder or template URL, the `create` command initializes a new extension project in the specified directory applying the chosen template and relevant metadata to the project.
+
 ## Usage
 
 You can run the `create` command using the following syntax.
 Replace `<extension-name|extension-path>` with your project name or path and set any required options:
 
+![Demo Video](https://placehold.co/600x400)
+
 <PackageManagerTabs
   command={{
     npm: "npx extension@latest create <extension-name|extension-path> [options]",
@@ -26,6 +35,8 @@ Replace `<extension-name|extension-path>` with your project name or path and set
 
 **Example Usage with Templates**
 
+![Demo Video](https://placehold.co/600x400)
+
 <PackageManagerTabs
   command={{
     npm: "npx extension@latest create my-extension --template=react",
@@ -44,9 +55,9 @@ If no path is provided, it defaults to the current working directory.
 
 <PackageManagerTabs
   command={{
-    npm: "npx extension@latest create path/to/my-extension --template=react",
-    pnpm: "pnpx extension@latest create path/to/my-extension --template=react",
-    yarn: "yarn dlx extension@latest create path/to/my-extension --template=react",
+    npm: "extension create path/to/my-extension --template=react",
+    pnpm: "extension create path/to/my-extension --template=react",
+    yarn: "extension create path/to/my-extension --template=react",
   }}
 />
 
@@ -60,6 +71,7 @@ The `create` command accepts several arguments and flags to customize the behavi
 | ---------------- | ----------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ |
 | `[path or name]` | The extension path or name                            | If a path is defined, loads the local extension. If a name is provided, loads the extension in the current working directory. | `process.cwd()`                                  |
 | -t, --template   | Name of the template used to bootstrap your extension | Bootstrap your extension using a template                                                                                     | [new](../getting-started/templates#template-new) |
+| --install   | Whether or not to auto install the template dependencies   | Install dependencies and devDependencies during creation time                                                                 | `true`                                           |
 
 - **Path or Name:** If a path is provided, the extension is created at that location. If a name is provided, it is created in the current working directory.
 - **`--template`:** Specifies the template to use when bootstrapping the extension (e.g., `react`, `typescript`).
@@ -78,18 +90,14 @@ This command creates a new extension named my-new-extension using the React temp
 
 ## Available Templates
 
-Users can choose from a variety of templates when creating their extension projects, including:
+<CarouselTemplates />
 
-- React: For building new tab or content scripts using React.
-- TypeScript: Initializes an extension with TypeScript support.
-- Custom: You can also specify external templates by providing a URL to a GitHub repo or any npm package.
 
 ## Best Practices
 
-- Use meaningful names: When naming your extension or path, use meaningful names that reflect the project's purpose.
-- Customizing Templates: You can always customize your extension after it's created. For example, if you want to add TypeScript support to a React template, it's easy to do so afterward.
 - Starting from a Template: Using a template is the fastest way to get started with browser extension development in Extension.js.
 
 ## Next Steps
 
-Once your extension is created, you can start developing by running extension dev. For more details on development workflows, check out the Development Guide.
+- Learn how to [develop](/docs/commands/dev) your extension.
+- Use the `extension.config.js` file to [configure your extension](../features/config.mdx).

docs/en/docs/commands/dev.mdx

@@ -7,12 +7,11 @@ import { AvatarImage } from "../../../../theme/components/avatar-image";
 
 > **Warning**: This feature is a work in progress and may be incomplete or subject to change. If you see an error or something that could be improved, please make a pull-request. The link that documents this feature can be found at the bottom of the page.
 
-
-The `dev` command watches for changes in your extension's files, recompiles them, and reloads the extension in real time. If you provide a URL, Extension.js will download and run the extension as if it were local.
+The `dev` command watches for changes in your extension's files, recompiles them, and reloads the extension in real-time. If you provide a URL, Extension.js will download and run the extension as if it were local.
 
 ## How it Works?
 
-For development frameworks, it's an industry-standard practice to have a development server that watches for changes in your files and recompiles them in real-time. Given the complex nature of browser extensions, the `dev` command in Extension.js handles the watch and recompile process for all the different contexts (HTML or not) of your extension.
+For development frameworks, it's an industry-standard practice to have a development server that watches for changes in your files and recompiles them in real time. Given the complex nature of browser extensions, the `dev` command in Extension.js handles the watch and recompile process for all the different contexts (HTML or not) of your extension.
 
 The `dev` command also provides a way to run remote extensions by providing a URL. This is useful when you want to test an extension from source without having to clone the repository.
 
@@ -47,14 +46,16 @@ In this example, the extension is developed in the `path/to/my-extension` direct
 
 Below is a breakdown of the available flags for the `dev` command:
 
-| Flag          | Argument                                       | What it does                                                                                                                                            | Defaults to     |
-| ------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- |
-| [path or url] | The extension path or the remote extension URL | If a path is defined, it loads the local extension. If a URL is provided, it pulls the extension from a remote source and loads it as a local extension | `process.cwd()` |
-| -b, --browser | The browser that will run the extension        | Changes the browser (`chrome`, `edge`, `firefox`, `all`)                                                                                                           | `"chrome"`      |
-| --chromium-binary | The path to the Chromium binary | The path to the Chromium binary. This is useful when you want to run the extension with Chromium-based browsers not supported by Extension.js. [Read how](../browsers/unsupported.mdx) | `undefined` |
-| --gecko-binary | The path to the Gecko binary | The path to the Gecko binary. This is useful when you want to run the extension with Firefox-based browsers not supported by Extension.js. . [Read how](../browsers/unsupported.mdx) | `undefined` |
-| -o, --open    | True or false                                  | Opens the browser when the extension is ready                                                                                                           | `true`          |
-| --polyfill    | True or false     | Allow the `browser.*` API namespace to run with all Chromium-based browsers**.** | `false` |
+| Flag              | Argument                          | What it does                                                                                                                                            | Defaults to        |
+| ----------------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ |
+| `[path or url]`   | Extension path or remote URL      | If a path is defined, it loads the local extension. If a URL is provided, it pulls the extension from a remote source and loads it as a local extension | `process.cwd()`    |
+| `--polyfill`      | Boolean                           | Enables compatibility for the `browser.*` API in Chromium-based browsers                                                                               | `false`            |
+| `--profile`       | Profile path                      | Specifies a path to a browser profile for testing                                                                                                       | `default`          |
+| `-b, --browser`   | Browser to run the extension      | Specifies the browser to run (`chrome`, `edge`, `firefox`, `all`)                                                                                       | `"chrome"`         |
+| `--chromium-binary` | Path to the Chromium binary    | Provides the path to a custom Chromium-based browser binary [Read more](../browsers/unsupported.mdx)                                                   | `undefined`        |
+| `--gecko-binary`  | Path to the Gecko binary          | Provides the path to a custom Gecko-based browser binary [Read more](../browsers/unsupported.mdx)                                                       | `undefined`        |
+| `--starting-url`   | URL                               | Starting URL for testing with the extension                                                                                                            | `chrome://newtab`  |
+| `--open`        | Boolean                           | Whether or not to automatically open the browser upon starting dev                                                                                             | `true`            |
 
 ## Examples
 
@@ -120,8 +121,8 @@ Below is a breakdown of the available flags for the `dev` command:
 
 ## Best Practices
 
-- **Browser Specific Configurations:** You can use the `--browser` flag to run your extension in different browsers during the development process.
-- **Remote Extensions:** Test them with the `--browser` flag to test your extension in different browsers without having to clone the repository.
+- **Browser Compatibility:** Test your extension in different browsers to ensure compatibility with the target audience.
+- **Polyfilling:** If Firefox or a Gecko-based browser is also a target, use the `--polyfill` flag to enable compatibility for the `browser.*` API in Chromium-based browsers.
 
 ## Next Steps
 

docs/en/docs/commands/preview.mdx

@@ -43,7 +43,11 @@ In this example, the extension is created in the `path/to/my-extension` director
 | Flag          | Argument                                       | What it does                                                                                                                                          | Defaults to     |
 | ------------- | ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- |
 | [path or url] | The extension path or the remote extension URL | If a path is defined, previews the local extension. If a URL is provided, pulls the extension from remote source and previews it as a local extension | `process.cwd()` |
-| -b, --browser | The browser that will run the extension        | Specifies the browser (`chrome`, `edge`, `all`)                                                                                                       | `"chrome"`      |
+| `--profile`       | Profile path                      | Specifies a path to a browser profile for testing                                                                                                       | `default`          |
+| `-b, --browser`   | Browser to run the extension      | Specifies the browser to run (`chrome`, `edge`, `firefox`, `all`)                                                                                       | `"chrome"`         |
+| `--chromium-binary` | Path to the Chromium binary    | Provides the path to a custom Chromium-based browser binary [Read more](../browsers/unsupported.mdx)                                                   | `undefined`        |
+| `--gecko-binary`  | Path to the Gecko binary          | Provides the path to a custom Gecko-based browser binary [Read more](../browsers/unsupported.mdx)                                                       | `undefined`        |
+| `--starting-url`   | URL                               | Starting URL for testing with the extension                                                                                                            | `chrome://newtab`  |
 
 ## Examples