Update docs and index page with new CLI syntax

Author: kylewlacy

src/content/blog/portable-dynamically-linked-packages-on-linux.md

@@ -8,7 +8,7 @@ authorUrl: https://kyle.space
 Hey, want to see a magic trick? If you [have Brioche installed](https://brioche.dev/docs/installation/), you can run this command:
 
 ```sh
-brioche build -r curl -o ./output
+brioche build curl -o ./output
 ```
 
 ...to get a copy of curl! Like you can then run `./output/bin/curl --version` and it works!

src/content/docs/docs/contributing/packaging-guide.md

@@ -10,10 +10,10 @@ The basic workflow to add a new package is:
 2. Create a new directory for the package with a `project.bri` file, e.g. `packages/my_package/project.bri`
 3. Write the code to build the package!
 4. Test it locally:
-   - Build it: `brioche build -p packages/my_package`
-   - Run it: `brioche run -p packages/my_package -- --help`
-   - Run tests: `brioche build -p packages/my_package -e test`
-   - Test that live updates work: `brioche live-update -p packages/my_package`
+   - Build it: `brioche build ./packages/my_package`
+   - Run it: `brioche run ./packages/my_package -- --help`
+   - Run tests: `brioche build ./packages/my_package -e test`
+   - Test that live updates work: `brioche live-update ./packages/my_package`
 5. Fork the repo and push the new package as a branch
 6. Open a Pull Request to add the package
 

src/content/docs/docs/core-concepts/cache.md

@@ -20,13 +20,13 @@ By default, enabling a custom cache will act as an "overlay" on top of the defau
 
 ### Syncing
 
-With a custom cache configured, run `brioche build -p project_path --sync` to sync recipes baked during the project build. This will build the project as normal, plus it will upload some of the baked recipes to the cache (recipes that are fast to bake will generally not be uploaded). When other machines using Brioche use the same cache, they will pull the pre-baked recipes from the cache, avoiding the need to bake the recipes themselves.
+With a custom cache configured, run `brioche build ./project_path --sync` to sync recipes baked during the project build. This will build the project as normal, plus it will upload some of the baked recipes to the cache (recipes that are fast to bake will generally not be uploaded). When other machines using Brioche use the same cache, they will pull the pre-baked recipes from the cache, avoiding the need to bake the recipes themselves.
 
 You can also sync multiple different builds of a project to a cache. For example, you may want to sync multiple project exports from the same project to the cache, which could look like this:
 
 ```bash
-brioche build -p project_path -e frontend --sync
-brioche build -p project_path -e backend --sync
+brioche build ./project_path -e frontend --sync
+brioche build ./project_path -e backend --sync
 ```
 
 ## Cache vs. registry

src/content/docs/docs/core-concepts/projects.md

@@ -112,7 +112,7 @@ export const project = {
 
 `.bri` files are normal TypeScript files, so `project.bri` can export values using the JavaScript `export` keyword. These exports can be used by submodules or dependent projects.
 
-Exports also serve as the actual entrypoint to builds. Running `brioche build -p project_path` will call the default export from the root module (`project.bri`). This can be changed to a different export explicitly with the `-e` flag, which names a different exported function to call. Here's a minimal example:
+Exports also serve as the actual entrypoint to builds. Running `brioche build ./project_path` will call the default export from the root module (`project.bri`). You can also pick a different exported function to call using the `^` syntax (e.g. `brioche build ./project_path^exportName`). Here's a minimal example:
 
 ```ts
 // Project structure:
@@ -144,7 +144,7 @@ export function backend(): std.Recipe {
 }
 ```
 
-You can then run `brioche build -e frontend` or `brioche build -e backend` to call the frontend or backend functions, respectively (don't forget the `-o` flag if you want to put the output somewhere!)
+You can then run `brioche build ^frontend` or `brioche build ^backend` to call the frontend or backend functions, respectively (don't forget the `-o` flag if you want to put the output somewhere!)
 
 The export used by `brioche build` should be a function that can be called with no arguments and should return the type `std.Recipe` or a compatible subtype (it's good practice to use a more specific type if possible, such as `std.Recipe<std.Directory>` if the function returns a directory recipe).
 

src/content/docs/docs/core-concepts/registry.md

@@ -18,6 +18,6 @@ When run, the registry will allow anyone with access to pull projects, but will
 
 > **Note**: To publish projects, you'll also need to configure a [custom cache](/docs/core-concepts/cache#custom-cache)
 
-Run `brioche publish -p project_path` to publish a project to a self-hosted registry. This will save an [artifact](/docs/core-concepts/artifacts) to the custom cache containing all of the project's files, then it will create or update tags for the project in the self-hosted registry, associated with the artifact's hash.
+Run `brioche publish ./project_path` to publish a project to a self-hosted registry. This will save an [artifact](/docs/core-concepts/artifacts) to the custom cache containing all of the project's files, then it will create or update tags for the project in the self-hosted registry, associated with the artifact's hash.
 
-Then, running `brioche build -r project_name` will then call the registry to determine the artifact hash associated to `project_name`, then Brioche will retrieve the project's artifact via the cache.
+Then, running `brioche build project_name` will then call the registry to determine the artifact hash associated to `project_name`, then Brioche will retrieve the project's artifact via the cache.

src/content/docs/docs/core-concepts/runnables.md

@@ -111,4 +111,4 @@ export function container() {
 }
 ```
 
-In this example, you can run `brioche run` to run the project natively on your machine, or you can run `brioche build -e container -o container.tar` to build an easily-deployable container image.
+In this example, you can run `brioche run` to run the project natively on your machine, or you can run `brioche build ^container -o container.tar` to build an easily-deployable container image.

src/pages/index.astro

@@ -29,7 +29,7 @@ const installSnippet = indoc`
 `;
 
 const helloWorldSnippet = indoc`
-  brioche run -r hello_world
+  brioche run hello_world
 `;
 
 interface Announcement {