diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml
new file mode 100644
index 0000000000..2e2e1ccd42
--- /dev/null
+++ b/.github/workflows/docs.yml
@@ -0,0 +1,42 @@
+name: mise-docs
+
+on:
+  push:
+    paths:
+      - "docs/**"
+    branches:
+      - main
+  pull_request:
+    paths:
+      - "docs/**"
+    branches:
+      - main
+
+concurrency:
+  group: mise-docs-release-${{ github.head_ref }}
+  cancel-in-progress: true
+
+env:
+  MISE_EXPERIMENTAL: 1
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0 # for lastUpdated
+      - uses: jdx/mise-action@v2
+        with:
+          install_args: bun
+          working_directory: docs
+      - run: bun install
+        working-directory: docs
+      - run: bun run docs:build
+        working-directory: docs
+      - if: github.event_name == 'push' && github.ref == 'refs/heads/main'
+        run: mise run release-docs
+        working-directory: docs
+        env:
+          AWS_ACCESS_KEY_ID: ${{ secrets.CLOUDFLARE_ACCESS_KEY_ID }}
+          AWS_SECRET_ACCESS_KEY: ${{ secrets.CLOUDFLARE_SECRET_ACCESS_KEY }}
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index dad6c35ab4..b8178cfe42 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -3,7 +3,7 @@ name: release
 on:
   push:
     tags: ["v*"]
-    branches: ["release", "win"]
+    branches: ["release", "win", "docs"]
   workflow_dispatch:
 
 concurrency:
@@ -250,20 +250,13 @@ jobs:
       - build-tarball-win
     steps:
       - uses: actions/checkout@v4
-        with:
-          path: mise
-      - uses: actions/checkout@v4
-        with:
-          repository: jdx/mise-docs
-          path: mise-docs
-          token: ${{ secrets.RTX_GITHUB_BOT_TOKEN }}
       - name: cache zipsign
         id: cache-zipsign
         uses: actions/cache@v4
         with:
           path: ~/.cargo/bin/zipsign
           key: cargo-zipsign
-      - run: ./mise/scripts/setup-zipsign.sh
+      - run: ./scripts/setup-zipsign.sh
         env:
           ZIPSIGN: ${{ secrets.ZIPSIGN }}
       - name: Install fd-find
@@ -281,12 +274,6 @@ jobs:
         with:
           key: ${{ secrets.RTX_SSH_KEY }}
           known_hosts: ${{ secrets.RTX_KNOWN_HOSTS_AUR }}
-      - uses: crazy-max/ghaction-import-gpg@v6
-        with:
-          gpg_private_key: ${{ secrets.MISE_GPG_KEY }}
-          git_user_signingkey: true
-          git_commit_gpgsign: true
-          workdir: mise-docs
       - uses: actions/download-artifact@v4
         with: { path: artifacts }
       - run: ls -R artifacts
@@ -299,16 +286,12 @@ jobs:
             mise-v*.zip
           merge-multiple: true
       - run: ls -R artifacts
-      - run: mise/scripts/release.sh
+      - run: scripts/release.sh
         env:
           CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_TOKEN }}
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
           CLOUDFLARE_ACCESS_KEY_ID: ${{ secrets.CLOUDFLARE_ACCESS_KEY_ID }}
           CLOUDFLARE_SECRET_ACCESS_KEY: ${{ secrets.CLOUDFLARE_SECRET_ACCESS_KEY }}
-      - name: mise-docs push
-        if: startsWith(github.event.ref, 'refs/tags/v')
-        run: git push
-        working-directory: mise-docs
       - name: GitHub Release Assets
         uses: softprops/action-gh-release@v2
         if: startsWith(github.event.ref, 'refs/tags/v')
diff --git a/.idea/mise.iml b/.idea/mise.iml
index 26265d4cb4..ff4628d837 100644
--- a/.idea/mise.iml
+++ b/.idea/mise.iml
@@ -26,17 +26,17 @@
       <excludeFolder url="file://$MODULE_DIR$/asdf-plugins" />
       <excludeFolder url="file://$MODULE_DIR$/megalinter-reports" />
       <excludeFolder url="file://$MODULE_DIR$/e2e/.venv" />
-      <excludeFolder url="file://$MODULE_DIR$/mise-docs/.vitepress/cache" />
-      <excludeFolder url="file://$MODULE_DIR$/mise-docs/.vitepress/dist" />
+      <excludeFolder url="file://$MODULE_DIR$/docs/.vitepress/cache" />
+      <excludeFolder url="file://$MODULE_DIR$/docs/.vitepress/dist" />
       <excludeFolder url="file://$MODULE_DIR$/usage/target" />
       <excludeFolder url="file://$MODULE_DIR$/usage/xx" />
       <excludeFolder url="file://$MODULE_DIR$/usage/docs/.vitepress/cache" />
       <excludeFolder url="file://$MODULE_DIR$/usage/docs/.vitepress/dist" />
       <excludeFolder url="file://$MODULE_DIR$/.dev" />
-      <excludeFolder url="file://$MODULE_DIR$/mise-docs/node_modules" />
+      <excludeFolder url="file://$MODULE_DIR$/docs/node_modules" />
       <excludePattern pattern="*.log" />
     </content>
     <orderEntry type="inheritedJdk" />
     <orderEntry type="sourceFolder" forTests="false" />
   </component>
-</module>
\ No newline at end of file
+</module>
diff --git a/.markdownlint.json b/.markdownlint.json
index a36edfc88f..a69775f0a1 100644
--- a/.markdownlint.json
+++ b/.markdownlint.json
@@ -1,6 +1,7 @@
 {
   "MD004": false,
   "MD013": false,
+  "MD029": false,
   "MD033": false,
   "MD040": false,
   "MD041": false
diff --git a/docs/.mise/tasks/release b/.mise/tasks/release-docs
similarity index 100%
rename from docs/.mise/tasks/release
rename to .mise/tasks/release-docs
diff --git a/docs/.github/renovate.json b/docs/.github/renovate.json
deleted file mode 100644
index dc8886a165..0000000000
--- a/docs/.github/renovate.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
-  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
-  "extends": [ "github>jdx/renovate-config" ]
-}
diff --git a/docs/.github/workflows/build.yml b/docs/.github/workflows/build.yml
deleted file mode 100644
index 648764c282..0000000000
--- a/docs/.github/workflows/build.yml
+++ /dev/null
@@ -1,23 +0,0 @@
-on:
-  pull_request:
-    branches:
-      - main
-
-concurrency:
-  group: mise-docs-build-${{ github.head_ref }}
-  cancel-in-progress: true
-
-env:
-  MISE_EXPERIMENTAL: 1
-
-jobs:
-  build:
-    name: Build
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0 # for lastUpdated
-      - uses: jdx/mise-action@v2
-      - run: bun install
-      - run: bun run docs:build
diff --git a/docs/.github/workflows/release.yml b/docs/.github/workflows/release.yml
deleted file mode 100644
index af9f72d18b..0000000000
--- a/docs/.github/workflows/release.yml
+++ /dev/null
@@ -1,28 +0,0 @@
-name: mise-docs
-
-on:
-  push:
-    branches:
-      - main
-
-concurrency:
-  group: mise-docs-release-${{ github.head_ref }}
-  cancel-in-progress: true
-
-env:
-  MISE_EXPERIMENTAL: 1
-
-jobs:
-  release:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0 # for lastUpdated
-      - uses: jdx/mise-action@v2
-      - run: bun install
-      - run: bun run docs:build
-      - run: mise run release
-        env:
-          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
-          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
diff --git a/docs/.vitepress/config.ts b/docs/.vitepress/config.ts
index 2eb8ba0b6a..aa3b251df1 100644
--- a/docs/.vitepress/config.ts
+++ b/docs/.vitepress/config.ts
@@ -109,7 +109,7 @@ export default defineConfig({
     ],
 
     editLink: {
-      pattern: 'https://github.com/jdx/mise-docs/edit/main/:path',
+      pattern: 'https://github.com/jdx/mise/edit/main/docs/:path',
     },
     search: {
       provider: 'algolia',
diff --git a/docs/configuration.md b/docs/configuration.md
index 16560b0628..1bdd724fc1 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -3,10 +3,12 @@
 ## `.mise.toml`
 
 `.mise.toml` is a new config file that replaces asdf-style `.tool-versions` files with a file
-that has lot more flexibility. It supports functionality that is not possible with `.tool-versions`, such as:
+that has lot more flexibility. It supports functionality that is not possible with `.tool-versions`,
+such as:
 
 - setting arbitrary env vars while inside the directory
-- passing options to plugins like `virtualenv=".venv"` for [python](https://github.com/jdx/mise/blob/main/docs/python.md#experimental-automatic-virtualenv-creationactivation).
+- passing options to plugins like `virtualenv=".venv"`
+  for [python](https://github.com/jdx/mise/blob/main/docs/python.md#experimental-automatic-virtualenv-creationactivation).
 - specifying custom plugin URLs
 
 They can use any of the following file locations (in order of precedence, top is highest):
@@ -23,7 +25,8 @@ They can use any of the following file locations (in order of precedence, top is
 - `.config/mise/config.toml`
 
 See [Profiles](/profiles) for more information about `.mise.$MISE_ENV.toml` files.
-These files recurse upwards, so if you have a `~/src/work/myproj/.mise.toml` file, what is defined there will override anything set in
+These files recurse upwards, so if you have a `~/src/work/myproj/.mise.toml` file, what is defined
+there will override anything set in
 `~/src/work/.mise.toml` or `~/.config/mise.toml`. The config contents are merged together.
 
 :::tip
@@ -47,7 +50,7 @@ node = ['16', 'prefix:20', 'ref:master', 'path:~/.nodes/14']
 
 # send arbitrary options to the plugin, passed as:
 # MISE_TOOL_OPTS__VENV=.venv
-python = {version='3.10', virtualenv='.venv'}
+python = { version = '3.10', virtualenv = '.venv' }
 
 [plugins]
 # specify a custom repo url
@@ -101,7 +104,8 @@ If you simply want to install a plugin from a specific URL once, it's better to
 `mise plugin install plugin <GIT_URL>`. Add this section to `.mise.toml` if you want
 to share the plugin location/revision with other developers in your project.
 
-This is similar to [`MISE_SHORTHANDS`](https://github.com/jdx/mise#mise_shorthands_fileconfigmiseshorthandstoml)
+This is similar
+to [`MISE_SHORTHANDS`](https://github.com/jdx/mise#mise_shorthands_fileconfigmiseshorthandstoml)
 but doesn't require a separate file.
 
 ### `[aliases]` - Tool version aliases
@@ -110,7 +114,9 @@ The following makes `mise install node@my_custom_node` install node-20.x
 this can also be specified in a [plugin](/dev-tools/aliases.md).
 note adding an alias will also add a symlink, in this case:
 
-    ~/.local/share/mise/installs/node/20 -> ./20.x.x
+```sh
+~/.local/share/mise/installs/node/20 -> ./20.x.x
+```
 
 ```toml
 my_custom_node = '20'
@@ -118,7 +124,8 @@ my_custom_node = '20'
 
 ## Global config: `~/.config/mise/config.toml`
 
-mise can be configured in `~/.config/mise/config.toml`. It's like local `.mise.toml` files except that
+mise can be configured in `~/.config/mise/config.toml`. It's like local `.mise.toml` files except
+that
 it is used for all directories.
 
 ```toml
@@ -168,7 +175,7 @@ env_file = '.env' # load env vars from a dotenv file, see `MISE_ENV_FILE`
 experimental = true # enable experimental features
 
 # configure messages displayed when entering directories with config files
-status = {missing_tools = "if_other_versions_installed", show_env = false, show_tools = false}
+status = { missing_tools = "if_other_versions_installed", show_env = false, show_tools = false }
 ```
 
 ## System config: `/etc/mise/config.toml`
@@ -198,7 +205,8 @@ node        sub-2:lts      # install 2 versions behind the latest lts (e.g.: 18
 python      sub-0.1:latest # install python-3.10 if the latest is 3.11
 ```
 
-See [the asdf docs](https://asdf-vm.com/manage/configuration.html#tool-versions) for more info on this file format.
+See [the asdf docs](https://asdf-vm.com/manage/configuration.html#tool-versions) for more info on
+this file format.
 
 ## Scopes
 
@@ -215,7 +223,8 @@ Both `.mise.toml` and `.tool-versions` support "scopes" which modify the behavio
 
 ## Legacy version files
 
-mise supports "legacy version files" just like asdf. They're language-specific files like `.node-version`
+mise supports "legacy version files" just like asdf. They're language-specific files
+like `.node-version`
 and `.python-version`. These are ideal for setting the runtime version of a project without forcing
 other developers to use a specific tool like mise/asdf.
 
@@ -234,7 +243,8 @@ in mise and nvm. Here are some of the supported legacy version files:
 | terraform | `.terraform-version`, `.packer-version`, `main.tf` |
 | yarn      | `.yarnrc`                                          |
 
-In mise these are enabled by default. You can disable them with `mise settings set legacy_version_file false`.
+In mise these are enabled by default. You can disable them
+with `mise settings set legacy_version_file false`.
 There is a performance cost to having these when they're parsed as it's performed by the plugin in
 `bin/parse-version-file`. However these are [cached](/cache-behavior) so it's not a huge deal.
 You may not even notice.
@@ -259,7 +269,8 @@ Some of them also can be set via global CLI flags.
 * Env: `MISE_ACTIVATE_AGGRESSIVE`
 * Default: `false`
 
-Pushes tools' bin-paths to the front of PATH instead of allowing modifications of PATH after activation to take precedence.
+Pushes tools' bin-paths to the front of PATH instead of allowing modifications of PATH after
+activation to take precedence.
 
 For example, if you have the following in your `.mise.toml`:
 
@@ -276,10 +287,12 @@ eval "$(mise activate zsh)"
 PATH="/some/other/python:$PATH"
 ```
 
-What will happen is `/some/other/python` will be used instead of the python installed by mise. This means
+What will happen is `/some/other/python` will be used instead of the python installed by mise. This
+means
 you typically want to put `mise activate` at the end of your shell config so nothing overrides it.
 
-If you want to always use the mise versions of tools despite what is in your shell config, set this to `true`.
+If you want to always use the mise versions of tools despite what is in your shell config, set this
+to `true`.
 In that case, using this example again, `/some/other/python` will be after mise's python in PATH.
 
 ### `asdf_compat`
@@ -289,9 +302,11 @@ In that case, using this example again, `/some/other/python` will be after mise'
 * Default: `false`
 
 Only output `.tool-versions` files in `mise local|global` which will be usable by asdf.
-This disables mise functionality that would otherwise make these files incompatible with asdf such as non-pinned versions.
+This disables mise functionality that would otherwise make these files incompatible with asdf such
+as non-pinned versions.
 
-This will also change the default global tool config to be `~/.tool-versions` instead of `~/.config/mise/config.toml`.
+This will also change the default global tool config to be `~/.tool-versions` instead
+of `~/.config/mise/config.toml`.
 
 ### `disable_tools`
 
@@ -299,7 +314,8 @@ This will also change the default global tool config to be `~/.tool-versions` in
 * Env: `MISE_DISABLE_TOOLS`
 * Default: `[]`
 
-Disables the specified tools. Separate with `,`. Generally used for core plugins but works with any tool.
+Disables the specified tools. Separate with `,`. Generally used for core plugins but works with any
+tool.
 
 ### `status.missing_tools`
 
@@ -343,7 +359,8 @@ mise can also be configured via environment variables. The following options are
 
 Default: `~/.local/share/mise` or `$XDG_DATA_HOME/mise`
 
-This is the directory where mise stores plugins and tool installs. These are not supposed to be shared
+This is the directory where mise stores plugins and tool installs. These are not supposed to be
+shared
 across machines.
 
 ### `MISE_CACHE_DIR`
@@ -356,7 +373,8 @@ across machines. It may be deleted at any time mise is not running.
 
 ### `MISE_TMP_DIR`
 
-Default: [`std::env::temp_dir()`](https://doc.rust-lang.org/std/env/fn.temp_dir.html) implementation in rust
+Default: [`std::env::temp_dir()`](https://doc.rust-lang.org/std/env/fn.temp_dir.html) implementation
+in rust
 
 This is used for temporary storage such as when installing tools.
 
@@ -379,7 +397,8 @@ a different name.
 
 ### `MISE_DEFAULT_CONFIG_FILENAME`
 
-Set to something other than `.mise.toml` to have mise look for `.mise.toml` config files with a different name.
+Set to something other than `.mise.toml` to have mise look for `.mise.toml` config files with a
+different name.
 
 ### `MISE_ENV`
 
@@ -413,7 +432,8 @@ of what is set in `.tool-versions`/`.mise.toml`.
 ### `MISE_LEGACY_VERSION_FILE=1`
 
 Plugins can read the versions files used by other version managers (if enabled by the plugin)
-for example, `.nvmrc` in the case of node's nvm. See [legacy version files](#legacy-version-files) for more
+for example, `.nvmrc` in the case of node's nvm. See [legacy version files](#legacy-version-files)
+for more
 information.
 
 Set to "0" to disable legacy version file parsing.
@@ -427,7 +447,8 @@ Disable legacy version file parsing for specific tools. Separate with `,`.
 Set to `1` to default to using `.mise.toml` in `mise local` instead of `.tool-versions` for
 configuration.
 
-For now this is not used by `mise use` which will only use `.mise.toml` unless `--path` is specified.
+For now this is not used by `mise use` which will only use `.mise.toml` unless `--path` is
+specified.
 
 ### `MISE_TRUSTED_CONFIG_PATHS`
 
@@ -518,8 +539,10 @@ This will automatically answer yes or no to prompts. This is useful for scriptin
 
 ### `MISE_NOT_FOUND_AUTO_INSTALL=true`
 
-Set to false to disable the "command not found" handler to autoinstall missing tool versions. Disable this
-if experiencing strange behavior in your shell when a command is not found—but please submit a ticket to
+Set to false to disable the "command not found" handler to autoinstall missing tool versions.
+Disable this
+if experiencing strange behavior in your shell when a command is not found—but please submit a
+ticket to
 help diagnose problems.
 
 ### `MISE_TASK_OUTPUT=prefix`
@@ -555,7 +578,8 @@ Default: false unless running NixOS or Alpine (let me know if others should be a
 Do not use precompiled binaries for all languages. Useful if running on a Linux distribution
 like Alpine that does not use glibc and therefore likely won't be able to run precompiled binaries.
 
-Note that this needs to be setup for each language. File a ticket if you notice a language that is not
+Note that this needs to be setup for each language. File a ticket if you notice a language that is
+not
 working with this config.
 
 ### `MISE_FISH_AUTO_ACTIVATE=1`
diff --git a/docs/contact.md b/docs/contact.md
index f026efccc3..e7b1815e7e 100644
--- a/docs/contact.md
+++ b/docs/contact.md
@@ -15,5 +15,3 @@ driver for me. If you have anything positive or negative to say-even if it's jus
 to say hi-please reach out to me either on [Twitter](https://twitter.com/jdxcode),
 [Mastodon](https://fosstodon.org/@jdx), [Discord](https://discord.gg/UBa7pJUN7Z),
 or `jdx at this domain`.
-
-
diff --git a/docs/contributing.md b/docs/contributing.md
index f214553fc6..2ca3da2b28 100644
--- a/docs/contributing.md
+++ b/docs/contributing.md
@@ -9,11 +9,11 @@ There is a docker setup that makes development with mise easier. It is especiall
 Here's some example ways to use it:
 
 ```sh
-$ mise run docker:cargo build
-$ mise run docker:cargo test
-$ mise run docker:mise --help # run `mise --help` in the dev container
-$ mise run docker:mise run test:e2e # run the e2e tests inside of the docker container
-$ mise run docker:e2e # shortcut for `mise run docker:mise run test:e2e`
+mise run docker:cargo build
+mise run docker:cargo test
+mise run docker:mise --help # run `mise --help` in the dev container
+mise run docker:mise run test:e2e # run the e2e tests inside of the docker container
+mise run docker:e2e # shortcut for `mise run docker:mise run test:e2e`
 ```
 
 ## Testing
@@ -26,12 +26,15 @@ for executing since it does not require having a proper local setup.
 To run locally you will need to first disable mise if you are using it.
 
 :::code-group
+
 ```sh [dev container]
-$ mise run docker:cargo test
+mise run docker:cargo test
 ```
+
 ```sh [local]
-$ cargo test
+cargo test
 ```
+
 :::
 
 ### E2E Tests
@@ -39,12 +42,15 @@ $ cargo test
 Like unit tests, the e2e tests should be run either in the dev container (recommended) or with mise disabled locally.
 
 :::code-group
+
 ```sh [dev container]
-$ mise run docker:e2e
+mise run docker:e2e
 ```
+
 ```sh [local]
-$ mise run test:e2e
+mise run test:e2e
 ```
+
 :::
 
 Slow tests do not run by default or on PRs. They can be manually enabled with `TEST_ALL=1`.
@@ -106,10 +112,10 @@ Don't forget to change the manifest path to the correct path for your setup.
 Then if that is in PATH just use `@mise` to run mise by compiling it on the fly.
 
 ```sh
-$ @mise --help
-$ @mise run docker:e2e
-$ eval "$(@mise activate zsh)"
-$ @mise activate fish | source
+@mise --help
+@mise run docker:e2e
+eval "$(@mise activate zsh)"
+@mise activate fish | source
 ```
 
 ## Releasing
diff --git a/docs/demo.gif b/docs/demo.gif
new file mode 100644
index 0000000000..7e11432bed
Binary files /dev/null and b/docs/demo.gif differ
diff --git a/docs/demo.sh b/docs/demo.sh
new file mode 100755
index 0000000000..f60cbf288d
--- /dev/null
+++ b/docs/demo.sh
@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -e
+
+cd
+mkdir -p ~/myproj
+rm -rf ~/myproj/.* ~/.mise/installs ~/.config/mise
+PATH="$HOME/.cargo/bin:$PATH" vhs <~/src/mise/docs/demo.tape
+rm -rf ~/myproj
diff --git a/docs/demo.tape b/docs/demo.tape
new file mode 100644
index 0000000000..521b76f58c
--- /dev/null
+++ b/docs/demo.tape
@@ -0,0 +1,87 @@
+# VHS documentation
+#
+# Output:
+#   Output <path>.gif               Create a GIF output at the given <path>
+#   Output <path>.mp4               Create an MP4 output at the given <path>
+#   Output <path>.webm              Create a WebM output at the given <path>
+#
+# Require:
+#   Require <string>                Ensure a program is on the $PATH to proceed
+#
+# Settings:
+#   Set FontSize <number>           Set the font size of the terminal
+#   Set FontFamily <string>         Set the font family of the terminal
+#   Set Height <number>             Set the height of the terminal
+#   Set Width <number>              Set the width of the terminal
+#   Set LetterSpacing <float>       Set the font letter spacing (tracking)
+#   Set LineHeight <float>          Set the font line height
+#   Set LoopOffset <float>%         Set the starting frame offset for the GIF loop
+#   Set Theme <json|string>         Set the theme of the terminal
+#   Set Padding <number>            Set the padding of the terminal
+#   Set Framerate <number>          Set the framerate of the recording
+#   Set PlaybackSpeed <float>       Set the playback speed of the recording
+#
+# Sleep:
+#   Sleep <time>                    Sleep for a set amount of <time> in seconds
+#
+# Type:
+#   Type[@<time>] "<characters>"    Type <characters> into the terminal with a
+#                                   <time> delay between each character
+#
+# Keys:
+#   Backspace[@<time>] [number]     Press the Backspace key
+#   Down[@<time>] [number]          Press the Down key
+#   Enter[@<time>] [number]         Press the Enter key
+#   Space[@<time>] [number]         Press the Space key
+#   Tab[@<time>] [number]           Press the Tab key
+#   Left[@<time>] [number]          Press the Left Arrow key
+#   Right[@<time>] [number]         Press the Right Arrow key
+#   Up[@<time>] [number]            Press the Up Arrow key
+#   Down[@<time>] [number]          Press the Down Arrow key
+#   PageUp[@<time>] [number]        Press the Page Up key
+#   PageDown[@<time>] [number]      Press the Page Down key
+#   Ctrl+<key>                      Press the Control key + <key> (e.g. Ctrl+C)
+#
+# Display:
+#   Hide                            Hide the subsequent commands from the output
+#   Show                            Show the subsequent commands in the output
+
+Output src/mise/docs/demo.gif
+#Output src/mise/docs/demo.webm
+
+Require echo
+
+Set Shell "zsh"
+Set FontFamily "Berkeley Mono"
+Set FontSize 24
+Set Width 1200
+Set Height 600
+Set Padding 10
+Set WindowBar Colorful
+#Set Theme "Catppuccin Macchiato"
+
+Sleep 50ms
+Type 'echo "First, we will download/setup mise"' Enter Sleep 2s
+Type "http https://mise.jdx.dev/mise-latest-macos-arm64 > ~/bin/mise" Enter Sleep 2s
+Type "chmod +x ~/bin/mise" Sleep 1s Enter Sleep 1s
+Type "mise -v" Sleep 1s Enter Sleep 1s
+Type 'eval "$(mise activate zsh)"' Sleep 1s Enter Sleep 2s
+Type 'echo "Ok, mise is ready to go now"' Enter Sleep 2s
+
+Type 'echo "Now, we will install node@lts and make it the global default"' Enter Sleep 2s
+Type "mise use --global node@lts" Sleep 2s Enter Sleep 3s
+Type "node -v" Sleep 1s Enter Sleep 3s
+Type "which node" Sleep 1s Enter Sleep 5s
+Type 'echo "Note that we get back the path to the real node here, not a shim"' Enter Sleep 2s
+
+Type 'echo "Lets enter a project directory we will setup to use node@21"' Enter Sleep 2s
+Type "cd ~/myproj" Sleep 1s Enter Sleep 1s
+Type "mise use node@21" Sleep 2s Enter Sleep 2s
+Type "node -v" Sleep 1s Enter Sleep 3s
+Type 'echo "As expected, now `node -v` is v21.x"' Enter Sleep 2s
+
+Type 'echo "We will leave this directory and the node version will revert to the global LTS version"' Enter Sleep 2s
+Type "cd .." Sleep 1s Enter Sleep 2s
+Type "node -v" Sleep 1s Enter Sleep 3s
+
+Sleep 5s
diff --git a/docs/dev-tools/backends/pipx.md b/docs/dev-tools/backends/pipx.md
index 59932ed849..6e0c7a5d36 100644
--- a/docs/dev-tools/backends/pipx.md
+++ b/docs/dev-tools/backends/pipx.md
@@ -1,6 +1,7 @@
 # pipx Backend <Badge type="warning" text="experimental" />
 
 You may install python packages directly from:
+
 - PyPI
 - Git
 - Github
diff --git a/docs/dev-tools/comparison-to-asdf.md b/docs/dev-tools/comparison-to-asdf.md
index 8f9ccc8fbc..d2bc68bfa3 100644
--- a/docs/dev-tools/comparison-to-asdf.md
+++ b/docs/dev-tools/comparison-to-asdf.md
@@ -101,6 +101,6 @@ mise has support for backends other than asdf plugins. For example you can insta
 directly from cargo and npm:
 
 ```sh
-$ mise use -g cargo:ripgrep@14
-$ mise use -g npm:prettier@3
+mise use -g cargo:ripgrep@14
+mise use -g npm:prettier@3
 ```
diff --git a/docs/dev-tools/index.md b/docs/dev-tools/index.md
index a568469a3d..73de097bf3 100644
--- a/docs/dev-tools/index.md
+++ b/docs/dev-tools/index.md
@@ -97,7 +97,7 @@ not already exists.
 `mise x` can be used for one-off commands using specific tools. e.g.: if you want to run a script with python3.12:
 
 ```sh
-$ mise x python@3.12 -- ./myscript.py
+mise x python@3.12 -- ./myscript.py
 ```
 
 Python will be installed if it is not already. `mise x` will read local/global `.tool-versions`/`.mise-toml` files
@@ -114,8 +114,9 @@ $ mise x -- node -v
 If you use this a lot, an alias can be helpful:
 
 ```sh
-$ alias mx="mise x --"
+alias mx="mise x --"
 ```
+
 :::
 
 Similarly, `mise run` can be used to [execute tasks](/tasks/) which will also activate the mise environment with all of your tools.
diff --git a/docs/dev-tools/shims.md b/docs/dev-tools/shims.md
index e870c46825..843bee69a4 100644
--- a/docs/dev-tools/shims.md
+++ b/docs/dev-tools/shims.md
@@ -44,8 +44,8 @@ the env vars.
 Also, if you run a set of commands in a single line like the following:
 
 ```sh
-$ cd ~
-$ cd ~/src/proj1 && node -v && cd ~/src/proj2 && node -v
+cd ~
+cd ~/src/proj1 && node -v && cd ~/src/proj2 && node -v
 ```
 
 Using `mise activate`, this will use the tools from `~`, not from `~/src/proj1` or `~/src/proj2` even
@@ -124,16 +124,19 @@ rc files like `.zshrc` are unusual. It's a script but also runs only for interac
 to access tools provided by mise inside of an rc file you have 2 options:
 
 ::: code-group
+
 ```sh [hook-env]
 eval "$(mise activate zsh)"
 eval "$(mise hook-env -s zsh)"
 node some_script.js
 ```
+
 ```sh [shims]
 eval "$(mise activate zsh --shims)" # should be first
 eval "$(mise activate zsh)"
 node some_script.js
 ```
+
 :::
 
 The `hook-env` option is the one I would go with. It's a bit cleaner since you won't have the shims
diff --git a/docs/direnv.md b/docs/direnv.md
index c2046a7caa..bb71a12f63 100644
--- a/docs/direnv.md
+++ b/docs/direnv.md
@@ -1,17 +1,22 @@
 # direnv
 
-[direnv](https://direnv.net) and mise both manage environment variables based on directory. Because they both analyze
-the current environment variables before and after their respective "hook" commands are run, they can sometimes conflict with each other.
+[direnv](https://direnv.net) and mise both manage environment variables based on directory. Because
+they both analyze
+the current environment variables before and after their respective "hook" commands are run, they
+can sometimes conflict with each other.
 
 If you have an issue, it's likely to do with the ordering of PATH. This means it would
-really only be a problem if you were trying to manage the same tool with direnv and mise. For example,
-you may use `layout python` in an `.envrc` but also be maintaining a `.tool-versions` file with python
+really only be a problem if you were trying to manage the same tool with direnv and mise. For
+example,
+you may use `layout python` in an `.envrc` but also be maintaining a `.tool-versions` file with
+python
 in it as well.
 
-A more typical usage of direnv would be to set some arbitrary environment variables, or add unrelated
+A more typical usage of direnv would be to set some arbitrary environment variables, or add
+unrelated
 binaries to PATH. In these cases, mise will not interfere with direnv.
 
-### mise inside of direnv (`use mise` in `.envrc`)
+## mise inside of direnv (`use mise` in `.envrc`)
 
 ::: warning
 Update 2024-01-21: after `use mise` has been out for a while, the general impression I have is that
@@ -21,7 +26,8 @@ or using `mise activate` alongside direnv.
 
 The project direction of mise has changed since this was written and the new direction is for it
 to be capable of replacing direnv completely for any use-case. This likely won't end up as a drop-in
-replacement for direnv like with asdf, but solving the same problems in different ways. See [environments](/environments.html)
+replacement for direnv like with asdf, but solving the same problems in different ways.
+See [environments](/environments.html)
 for more details.
 
 I have had virtually no reports of problems with `use mise` in the year it has been out.
@@ -29,7 +35,8 @@ This could be because virtually is using it, or it has been surprisingly stable.
 don't know which. If you try it or use it regularly let me know.
 
 While I have no immediate plans or reasons to do this now, I could see this functionality being
-the target of a future deprecation. Not because it's a maintenance burden, but because it just hasn't
+the target of a future deprecation. Not because it's a maintenance burden, but because it just
+hasn't
 seemed like a particularly useful solution and it may help focus mise on the functionality that does
 work for users.
 :::
@@ -38,7 +45,8 @@ If you do encounter issues with `mise activate`, or just want to use direnv in a
 this is a simpler setup that's less likely to cause issues—at the cost of functionality.
 
 This may be required if you want to use direnv's `layout python` with mise. Otherwise there are
-situations where mise will override direnv's PATH. `use mise` ensures that direnv always has control.
+situations where mise will override direnv's PATH. `use mise` ensures that direnv always has
+control.
 
 To do this, first use `mise` to build a `use_mise` function that you can use in `.envrc` files:
 
@@ -52,8 +60,10 @@ Now in your `.envrc` file add the following:
 use mise
 ```
 
-direnv will now call mise to export its environment variables. You'll need to make sure to add `use_mise`
-to all projects that use mise (or use direnv's `source_up` to load it from a subdirectory). You can also add `use mise` to `~/.config/direnv/direnvrc`.
+direnv will now call mise to export its environment variables. You'll need to make sure to
+add `use_mise`
+to all projects that use mise (or use direnv's `source_up` to load it from a subdirectory). You can
+also add `use mise` to `~/.config/direnv/direnvrc`.
 
 Note that in this method direnv typically won't know to refresh `.tool-versions` files
 unless they're at the same level as a `.envrc` file. You'll likely always want to have
@@ -66,7 +76,8 @@ export MISE_NODE_VERSION=20.0.0
 export MISE_PYTHON_VERSION=3.11
 ```
 
-Of course if you use `mise activate`, then these steps won't have been necessary and you can use mise
+Of course if you use `mise activate`, then these steps won't have been necessary and you can use
+mise
 as if direnv was not used.
 
 If you continue to struggle, you can also try using the [shims method](dev-tools/shims.md).
@@ -74,6 +85,7 @@ If you continue to struggle, you can also try using the [shims method](dev-tools
 ### Do you need direnv?
 
 While making mise compatible with direnv is, and will always be a major goal of this project, I also
-want mise to be capable of replacing direnv if needed. This is why mise includes support for managing
+want mise to be capable of replacing direnv if needed. This is why mise includes support for
+managing
 env vars and [virtualenv](lang/python.md#automatic-virtualenv-activation)
 for python using `.mise.toml`.
diff --git a/docs/faq.md b/docs/faq.md
index 3a73de7861..5b35c537fc 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -1,14 +1,18 @@
 # FAQs
 
-### I don't want to put a `.tool-versions` file into my project since git shows it as an untracked file
+## I don't want to put a `.tool-versions` file into my project since git shows it as an untracked file
 
 You can make git ignore these files in 3 different ways:
 
-- Adding `.tool-versions` to project's `.gitignore` file. This has the downside that you need to commit the change to the ignore file.
-- Adding `.tool-versions` to project's `.git/info/exclude`. This file is local to your project so there is no need to commit it.
-- Adding `.tool-versions` to global gitignore (`core.excludesFile`). This will cause git to ignore `.tool-versions` files in all projects. You can explicitly add one to a project if needed with `git add --force .tool-versions`.
+- Adding `.tool-versions` to project's `.gitignore` file. This has the downside that you need to
+  commit the change to the ignore file.
+- Adding `.tool-versions` to project's `.git/info/exclude`. This file is local to your project so
+  there is no need to commit it.
+- Adding `.tool-versions` to global gitignore (`core.excludesFile`). This will cause git to
+  ignore `.tool-versions` files in all projects. You can explicitly add one to a project if needed
+  with `git add --force .tool-versions`.
 
-### What is the difference between "nodejs" and "node" (or "golang" and "go")?
+## What is the difference between "nodejs" and "node" (or "golang" and "go")?
 
 These are aliased. For example, `mise use nodejs@14.0` is the same as `mise install node@14.0`. This
 means it is not possible to have these be different plugins.
@@ -21,11 +25,12 @@ Under the hood, when mise reads a config file or takes CLI input it will swap ou
 While this change is rolling out, there is some migration code that will move installs/plugins from
 the "nodejs" and "golang" directories to the new names. If this runs for you you'll see a message
 but it should not run again unless there is some kind of problem. In this case, it's probably
-easiest to just run `rm -rf ~/.local/share/mise/installs/{golang,nodejs} ~/.local/share/mise/plugins/{golang,nodejs}`.
+easiest to just
+run `rm -rf ~/.local/share/mise/installs/{golang,nodejs} ~/.local/share/mise/plugins/{golang,nodejs}`.
 
 Once most users have migrated over this migration code will be removed.
 
-### What does `mise activate` do?
+## What does `mise activate` do?
 
 It registers a shell hook to run `mise hook-env` every time the shell prompt is displayed.
 `mise hook-env` checks the current env vars (most importantly `PATH` but there are others like
@@ -51,20 +56,23 @@ situations where it needs to run without the directory changing, for example if
 Because it runs on prompt display, if you attempt to use `mise activate` in a
 non-interactive session (like a bash script), it will never call `mise hook-env` and in effect will
 never modify PATH because it never displays a prompt. For this type of setup, you can either call
-`mise hook-env` manually every time you wish to update PATH, or use [shims](/dev-tools/shims.md) instead (preferred).
+`mise hook-env` manually every time you wish to update PATH, or use [shims](/dev-tools/shims.md)
+instead (preferred).
 Or if you only need to use mise for certain commands, just prefix the commands with
 [`mise x --`](./cli/#mise-exec-options-tool-version-command).
 For example, `mise x -- npm test` or `mise x -- ./my_script.sh`.
 
 `mise hook-env` will exit early in different situations if no changes have been made. This prevents
-adding latency to your shell prompt every time you run a command. You can run `mise hook-env` yourself
-to see what it outputs, however it is likely nothing if you're in a shell that has already been activated.
+adding latency to your shell prompt every time you run a command. You can run `mise hook-env`
+yourself
+to see what it outputs, however it is likely nothing if you're in a shell that has already been
+activated.
 
 `mise activate` also creates a shell function (in most shells) called `mise`.
 This is a trick that makes it possible for `mise shell`
 and `mise deactivate` to work without wrapping them in `eval "$(mise shell)"`.
 
-### `mise activate` doesn't work in `~/.profile`, `~/.bash_profile`, `~/.zprofile`
+## `mise activate` doesn't work in `~/.profile`, `~/.bash_profile`, `~/.zprofile`
 
 `mise activate` should only be used in `rc` files. These are the interactive ones used when
 a real user is using the terminal. (As opposed to being executed by an IDE or something). The prompt
@@ -72,74 +80,89 @@ isn't displayed in non-interactive environments so PATH won't be modified.
 
 For non-interactive setups, consider using shims instead which will route calls to the correct
 directory by looking at `PWD` every time they're executed. You can also call `mise exec` instead of
-expecting things to be directly on PATH. You can also run `mise env` in a non-interactive shell, however that
+expecting things to be directly on PATH. You can also run `mise env` in a non-interactive shell,
+however that
 will only setup the global tools. It won't modify the environment variables when entering into a
 different project.
 
-Also see the [shebang](/tips-and-tricks#shebang) example for a way to make scripts call mise to get the runtime.
+Also see the [shebang](/tips-and-tricks#shebang) example for a way to make scripts call mise to get
+the runtime.
 That is another way to use mise without activation.
 
-### mise is failing or not working right
+## mise is failing or not working right
 
 First try setting `MISE_DEBUG=1` or `MISE_TRACE=1` and see if that gives you more information.
 You can also set `MISE_LOG_FILE_LEVEL=debug MISE_LOG_FILE=/path/to/logfile` to write logs to a file.
 
-If something is happening with the activate hook, you can try disabling it and calling `eval "$(mise hook-env)"` manually.
-It can also be helpful to use `mise env` which will just output environment variables that would be set.
+If something is happening with the activate hook, you can try disabling it and
+calling `eval "$(mise hook-env)"` manually.
+It can also be helpful to use `mise env` which will just output environment variables that would be
+set.
 Also consider using [shims](/dev-tools/shims.md) which can be more compatible.
 
 If runtime installation isn't working right, try using the `--raw` flag which will install things in
 series and connect stdin/stdout/stderr directly to the terminal. If a plugin is trying to interact
 with you for some reason this will make it work.
 
-Of course check the version of mise with `mise --version` and make sure it is the latest. Use `mise self-update`
-to update it. `mise cache clean` can be used to wipe the internal cache and `mise implode` can be used
+Of course check the version of mise with `mise --version` and make sure it is the latest.
+Use `mise self-update`
+to update it. `mise cache clean` can be used to wipe the internal cache and `mise implode` can be
+used
 to remove everything except config.
 
-Before submitting a ticket, it's a good idea to test what you were doing with asdf. That way we can rule
-out if the issue is with mise or if it's with a particular plugin. For example, if `mise install python@latest`
+Before submitting a ticket, it's a good idea to test what you were doing with asdf. That way we can
+rule
+out if the issue is with mise or if it's with a particular plugin. For example,
+if `mise install python@latest`
 doesn't work, try running `asdf install python latest` to see if it's an issue with asdf-python.
 
 Lastly, there is `mise doctor` which will show diagnostic information and any warnings about issues
 detected with your setup. If you submit a bug report, please include the output of `mise doctor`.
 
-### New version of a tool is not available
+## New version of a tool is not available
 
 There are 2 places that versions are cached so a brand new release might not appear right away.
 
-The first is that the mise CLI caches versions for 24 hours. This can be cleared with `mise cache clear`.
+The first is that the mise CLI caches versions for 24 hours. This can be cleared
+with `mise cache clear`.
 
 The second uses the mise-versions.jdx.dev host as a centralized
 place to list all of the versions of most plugins. This is intended to speed up mise and also
 get around GitHub rate limits when querying for new versions. Check that repo for your plugin to
-see if it has an updated version. This service can be disabled by setting `MISE_USE_VERSIONS_HOST=0`.
+see if it has an updated version. This service can be disabled by
+setting `MISE_USE_VERSIONS_HOST=0`.
 
-### Windows support?
+## Windows support?
 
 This is something we'd like to add! <https://github.com/jdx/mise/discussions/66>
 
 It's not a near-term goal and it would require plugin modifications, but it should be feasible.
 
-### How do I use mise with http proxies?
+## How do I use mise with http proxies?
 
-Short answer: just set `http_proxy` and `https_proxy` environment variables. These should be lowercase.
+Short answer: just set `http_proxy` and `https_proxy` environment variables. These should be
+lowercase.
 
 This may not work with all plugins if they are not configured to use these env vars.
-If you're having a proxy-related issue installing something specific you should post an issue on the plugin's repository.
+If you're having a proxy-related issue installing something specific you should post an issue on the
+plugin's repository.
 
-### How do the shorthand plugin names map to repositories?
+## How do the shorthand plugin names map to repositories?
 
 e.g.: how does `mise plugin install elixir` know to fetch <https://github.com/asdf-vm/asdf-elixir>?
 
-We maintain [an index](https://github.com/rtx-plugins/registry) of shorthands that mise uses as a base.
-This is regularly updated every time that mise has a release. This repository is stored directly into
+We maintain [an index](https://github.com/rtx-plugins/registry) of shorthands that mise uses as a
+base.
+This is regularly updated every time that mise has a release. This repository is stored directly
+into
 the codebase [here](https://github.com/jdx/mise/blob/main/src/default_shorthands.rs).
 
-### Does "node@20" mean the newest available version of node?
+## Does "node@20" mean the newest available version of node?
 
 It depends on the command. Normally, for most commands and inside of config files, "node@20" will
 point to the latest _installed_ version of node-20.x. You can find this version by running
-`mise latest --installed node@20` or by seeing what the `~/.local/share/mise/installs/node/20` symlink
+`mise latest --installed node@20` or by seeing what the `~/.local/share/mise/installs/node/20`
+symlink
 points to:
 
 ```sh
@@ -156,18 +179,22 @@ There are some exceptions to this, such as the following:
 These will use the latest _available_ version of node-20.x. This generally makes sense because you
 wouldn't want to install a version that is already installed.
 
-### How do I migrate from asdf?
+## How do I migrate from asdf?
 
-First, just install mise with `mise activate` like in the getting started guide and remove asdf from your
+First, just install mise with `mise activate` like in the getting started guide and remove asdf from
+your
 shell rc file.
 
 Then you can just run `mise install` in a directory with an asdf `.tool-versions` file and it will
-install the runtimes. You could attempt to avoid this by copying the internal directory from asdf over
-to mise with `cp -r ~/.asdf ~/.local/share/mise`. That _should_ work because they use the same structure,
-however this isn't officially supported or regularly tested. Alternatively you can set `MISE_DATA_DIR=~/.asdf`
+install the runtimes. You could attempt to avoid this by copying the internal directory from asdf
+over
+to mise with `cp -r ~/.asdf ~/.local/share/mise`. That _should_ work because they use the same
+structure,
+however this isn't officially supported or regularly tested. Alternatively you can
+set `MISE_DATA_DIR=~/.asdf`
 and see what happens.
 
-### How compatible is mise with asdf?
+## How compatible is mise with asdf?
 
 mise should be able to read/install any `.tool-versions` file used by asdf. Any asdf plugin
 should be usable in mise. The commands in mise are slightly
@@ -186,9 +213,10 @@ call asdf commands.
 If you need to switch to/from asdf or work in a project with asdf users, you can set
 [`MISE_ASDF_COMPAT=1`](/configuration#mise_asdf_compat1). That prevents
 mise from writing `.tool-versions` files that will not be
-compatible with asdf. Also consider using `.mise.toml` instead which won't conflict with asdf setups.
+compatible with asdf. Also consider using `.mise.toml` instead which won't conflict with asdf
+setups.
 
-### mise isn't working when calling from tmux or another shell initialization script
+## mise isn't working when calling from tmux or another shell initialization script
 
 `mise activate` will not update PATH until the shell prompt is displayed. So if you need to access a
 tool provided by mise before the prompt is displayed you can either
@@ -209,7 +237,7 @@ python --version # will work only after calling hook-env explicitly
 
 For more information, see [What does `mise activate` do?](#what-does-mise-activate-do)
 
-### How do I disable/force CLI color output?
+## How do I disable/force CLI color output?
 
 mise uses [console.rs](https://docs.rs/console/latest/console/fn.colors_enabled.html) which
 honors the [clicolors spec](https://bixense.com/clicolors/):
@@ -218,7 +246,7 @@ honors the [clicolors spec](https://bixense.com/clicolors/):
 - `CLICOLOR == 0`: Don’t output ANSI color escape codes.
 - `CLICOLOR_FORCE != 0`: ANSI colors should be enabled no matter what.
 
-### Is mise secure?
+## Is mise secure?
 
 Providing a secure supply chain is incredibly important. mise already provides a more secure
 experience when compared to asdf. Security-oriented evaluations and contributions are welcome.
diff --git a/docs/getting-started.md b/docs/getting-started.md
index e960dc9a4c..2bda2255a3 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -22,29 +22,38 @@ mise 2024.x.x
 ```
 
 ::: tip
-"~/.local/bin" does not need to be in PATH. mise will automatically add its own directory to PATH when activated.
+"~/.local/bin" does not need to be in PATH. mise will automatically add its own directory to PATH
+when activated.
 :::
 
 ### 2a. Activate mise
 
-`mise activate` is one way to setup mise but alternatively you can use [shims](dev-tools/shims.md), [direnv](./direnv), or skip
-this step entirely. If you skip it, then tools like `npm` and `node` will not be in PATH. You'll need to prefix
+`mise activate` is one way to setup mise but alternatively you can
+use [shims](dev-tools/shims.md), [direnv](./direnv), or skip
+this step entirely. If you skip it, then tools like `npm` and `node` will not be in PATH. You'll
+need to prefix
 commands with `mise exec` or run tasks with `mise run` in order to use tools managed with mise.
 
-Make sure you restart your shell session after modifying your rc file in order for it to take effect. Also note that
-this uses `~/.local/bin/mise` as the binary location since that's what https://mise.run uses by default. If you've
+Make sure you restart your shell session after modifying your rc file in order for it to take
+effect. Also note that
+this uses `~/.local/bin/mise` as the binary location since that's what <https://mise.run> uses by
+default. If you've
 installed mise by some other means it may be on PATH or somewhere different.
 
 ::: code-group
+
 ```sh [bash]
 echo 'eval "$(~/.local/bin/mise activate bash)"' >> ~/.bashrc
 ```
+
 ```sh [zsh]
 echo 'eval "$(~/.local/bin/mise activate zsh)"' >> ~/.zshrc
 ```
+
 ```sh [fish]
 echo '~/.local/bin/mise activate fish | source' >> ~/.config/fish/config.fish
 ```
+
 :::
 
 ### 2b. Alternative: Add mise shims to PATH
@@ -55,14 +64,17 @@ mise in interactive sessions (.bash_profile/.zprofile will work in non-interacti
 like scripts or IDEs).
 
 ::: code-group
+
 ```sh [bash]
 # note that bash will read from ~/.profile or ~/.bash_profile if the latter exists
 # ergo, you may want to check to see which is defined on your system and only append to the existing file
 echo 'export PATH="$HOME/.local/share/mise/shims:$PATH"' >> ~/.bash_profile
 ```
+
 ```sh [zsh]
 echo 'export PATH="$HOME/.local/share/mise/shims:$PATH"' >> ~/.zprofile
 ```
+
 ```sh [fish]
 fish_add_path ~/.local/share/mise/shims
 ```
@@ -72,13 +84,15 @@ You can also run `mise activate --shims` which will do the above for you.
 :::
 
 :::info
-mise respects [`MISE_DATA_DIR`](/configuration) and [`XDG_DATA_HOME`](/configuration) if you'd like to change these locations.
+mise respects [`MISE_DATA_DIR`](/configuration) and [`XDG_DATA_HOME`](/configuration) if you'd like
+to change these locations.
 :::
 
 ### 3. Adding tools to mise <Badge type="tip" text="optional" />
 
 :::info
-Of course, if using mise solely for [environment management](/environments) or [running tasks](/tasks/)
+Of course, if using mise solely for [environment management](/environments)
+or [running tasks](/tasks/)
 this step is not necessary.
 :::
 
@@ -99,14 +113,16 @@ v20.x.x
 ```
 
 :::tip
-Use `mise x -- node -v` or set a shell alias in your shell's rc file like `alias x="mise x --"` to save some keystrokes.
+Use `mise x -- node -v` or set a shell alias in your shell's rc file like `alias x="mise x --"` to
+save some keystrokes.
 :::
 
 ## Alternate Installation Methods
 
-### https://mise.run
+### <https://mise.run>
 
-Note that it isn't necessary for `mise` to be on `PATH`. If you run the activate script in your shell's rc
+Note that it isn't necessary for `mise` to be on `PATH`. If you run the activate script in your
+shell's rc
 file, mise will automatically add itself to `PATH`.
 
 ```sh
@@ -114,6 +130,7 @@ curl https://mise.run | sh
 ```
 
 Options:
+
 - `MISE_DEBUG=1` – enable debug logging
 - `MISE_QUIET=1` – disable non-error output
 - `MISE_INSTALL_PATH=/some/path` – change the binary path (default: `~/.local/bin/mise`)
@@ -131,18 +148,23 @@ sh ./install.sh
 or if you're allergic to `| sh`:
 
 ::: code-group
+
 ```sh [macos-arm64]
 curl https://mise.jdx.dev/mise-latest-macos-arm64 > ~/.local/bin/mise
 ```
+
 ```sh [macos-x64]
 curl https://mise.jdx.dev/mise-latest-macos-x64 > ~/.local/bin/mise
 ```
+
 ```sh [linux-x64]
 curl https://mise.jdx.dev/mise-latest-linux-x64 > ~/.local/bin/mise
 ```
+
 ```sh [linux-arm64]
 curl https://mise.jdx.dev/mise-latest-linux-arm64 > ~/.local/bin/mise
 ```
+
 :::
 
 It doesn't matter where you put it. So use `~/bin`, `/usr/local/bin`, `~/.local/bin` or whatever.
@@ -171,13 +193,15 @@ For Alpine Linux:
 apk add mise
 ```
 
-_mise lives in the [community repository](https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/community/mise/APKBUILD)._
+_mise lives in
+the [community repository](https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/community/mise/APKBUILD)._
 
 ### apt
 
 For installation on Ubuntu/Debian:
 
 ::: code-group
+
 ```sh [amd64]
 apt update -y && apt install -y gpg sudo wget curl
 sudo install -dm 755 /etc/apt/keyrings
@@ -195,6 +219,7 @@ echo "deb [signed-by=/etc/apt/keyrings/mise-archive-keyring.gpg arch=arm64] http
 sudo apt update
 sudo apt install -y mise
 ```
+
 :::
 
 ### aur
@@ -302,19 +327,19 @@ yum install -y mise
 
 ## Shells
 
-#### Bash
+### Bash
 
 ```sh
 echo 'eval "$(mise activate bash)"' >> ~/.bashrc
 ```
 
-#### Zsh
+### Zsh
 
 ```sh
 echo 'eval "$(mise activate zsh)"' >> "${ZDOTDIR-$HOME}/.zshrc"
 ```
 
-#### Fish
+### Fish
 
 ```sh
 echo 'mise activate fish | source' >> ~/.config/fish/config.fish
@@ -327,9 +352,11 @@ this is not necessary.
 See [`MISE_FISH_AUTO_ACTIVATE=1`](/configuration#mise_fish_auto_activate1) for more information.
 :::
 
-#### Nushell
+### Nushell
 
-Since Nu does [not support `eval`](https://www.nushell.sh/book/how_nushell_code_gets_run.html#eval-function) the initialization script is saved in `env.nu`:
+Since Nu
+does [not support `eval`](https://www.nushell.sh/book/how_nushell_code_gets_run.html#eval-function)
+the initialization script is saved in `env.nu`:
 
 ```nushell
 '
@@ -339,15 +366,18 @@ let mise_path = $nu.default-config-dir | path join scripts mise.nu
 "\nuse mise.nu" | save $nu.config-path --append
 ```
 
-If you prefer to keep your dotfiles clean you can save it to a different directory then update `$env.NU_LIB_DIRS`:
+If you prefer to keep your dotfiles clean you can save it to a different directory then
+update `$env.NU_LIB_DIRS`:
 
 ```nushell
 "\n$env.NU_LIB_DIRS ++= ($mise_path | path dirname | to nuon)" | save $nu.env-path --append
 ```
 
-#### Xonsh
+### Xonsh
 
-Since `.xsh` files are [not compiled](https://github.com/xonsh/xonsh/issues/3953) you may shave a bit off startup time by using a pure Python import: add the code below to, for example, `~/.config/xonsh/mise.py` config file and `import mise` it in `~/.config/xonsh/rc.xsh`:
+Since `.xsh` files are [not compiled](https://github.com/xonsh/xonsh/issues/3953) you may shave a
+bit off startup time by using a pure Python import: add the code below to, for
+example, `~/.config/xonsh/mise.py` config file and `import mise` it in `~/.config/xonsh/rc.xsh`:
 
 ```python
 from pathlib         import Path
@@ -364,9 +394,12 @@ Or continue to use `rc.xsh`/`.xonshrc`:
 echo 'execx($(~/bin/mise activate xonsh))' >> ~/.config/xonsh/rc.xsh # or ~/.xonshrc
 ```
 
-Given that `mise` replaces both shell env `$PATH` and OS environ `PATH`, watch out that your configs don't have these two set differently (might throw `os.environ['PATH'] = xonsh.built_ins.XSH.env.get_detyped('PATH')` at the end of a config to make sure they match)
+Given that `mise` replaces both shell env `$PATH` and OS environ `PATH`, watch out that your configs
+don't have these two set differently (might
+throw `os.environ['PATH'] = xonsh.built_ins.XSH.env.get_detyped('PATH')` at the end of a config to
+make sure they match)
 
-#### Something else?
+### Something else?
 
 Adding a new shell is not hard at all since very little shell code is
 in this project.
diff --git a/docs/how-i-use-mise.md b/docs/how-i-use-mise.md
index 437d9dd2f8..f5d06e4acb 100644
--- a/docs/how-i-use-mise.md
+++ b/docs/how-i-use-mise.md
@@ -52,8 +52,8 @@ This way I can easily test mise in any directory with `@mise`. I probably
 run this more often than without just out of habit. For example, if I want to test `mise activate` in zsh:
 
 ```sh
-$ zsh
-$ eval "$(@mise activate zsh)"
+zsh
+eval "$(@mise activate zsh)"
 ```
 
 ## Minimal tools
@@ -110,10 +110,10 @@ instead.
 I often need to access mise's internals so I do the following:
 
 ```sh
-$ ln -s ~/.mise ~/.config/mise
-$ ln -s ~/.mise ~/.local/share/mise
-$ ln -s ~/.mise ~/.local/state/mise
-$ ln -s ~/.mise/cache ~/.cache/mise
+ln -s ~/.mise ~/.config/mise
+ln -s ~/.mise ~/.local/share/mise
+ln -s ~/.mise ~/.local/state/mise
+ln -s ~/.mise/cache ~/.cache/mise
 ```
 
 It is good that mise generally follows XDG spec, but for tools that I interact
diff --git a/docs/ide-integration.md b/docs/ide-integration.md
index fa9654523c..e07f574770 100644
--- a/docs/ide-integration.md
+++ b/docs/ide-integration.md
@@ -15,6 +15,7 @@ to first add it to `/etc/shells`.
 Once you know the right one, modify the appropriate file:
 
 ::: code-group
+
 ```zsh
 # ~/.zprofile
 eval "$(mise activate zsh --shims)"
@@ -33,14 +34,20 @@ else
   mise activate fish --shims | source
 end
 ```
+
 :::
 
-This assumes that `mise` is on PATH. If it is not, you'll need to use the absolute path (e.g.: `eval "$($HOME/.local/bin/mise activate zsh)"`).
+This assumes that `mise` is on PATH. If it is not, you'll need to use the absolute path (
+e.g.: `eval "$($HOME/.local/bin/mise activate zsh)"`).
 
-This won't work for all of mise's functionality. For example, arbitrary env vars in `[env]` will only be set
-if a shim is executed. For this we need tighter integration with the IDE and a custom plugin. If you feel
-ambitious, take a look at existing direnv extensions for your IDE and see if you can modify it to work for mise.
-Direnv and mise work similarly and there should be a direnv extension that can be used as a starting point.
+This won't work for all of mise's functionality. For example, arbitrary env vars in `[env]` will
+only be set
+if a shim is executed. For this we need tighter integration with the IDE and a custom plugin. If you
+feel
+ambitious, take a look at existing direnv extensions for your IDE and see if you can modify it to
+work for mise.
+Direnv and mise work similarly and there should be a direnv extension that can be used as a starting
+point.
 
 ## Vim
 
@@ -76,7 +83,11 @@ vim.env.PATH = vim.env.HOME .. "/.local/share/mise/shims:" .. vim.env.PATH
 
 ## Xcode
 
-Xcode projects can run system commands from script build phases and schemes. Since Xcode sandboxes the execution of the script using the tool `/usr/bin/sandbox-exec`, don't expect Mise and the automatically-activated tools to work out of the box. First, you'll need to add `$(SRCROOT)/.mise.toml` to the list of **Input files**. This is necessary for Xcode to allow reads to that file. Then, you can use `mise activate` to activate the tools you need:
+Xcode projects can run system commands from script build phases and schemes. Since Xcode sandboxes
+the execution of the script using the tool `/usr/bin/sandbox-exec`, don't expect Mise and the
+automatically-activated tools to work out of the box. First, you'll need to
+add `$(SRCROOT)/.mise.toml` to the list of **Input files**. This is necessary for Xcode to allow
+reads to that file. Then, you can use `mise activate` to activate the tools you need:
 
 ```bash
 # -C ensures that Mise loads the configuration from the Mise configuration 
@@ -88,20 +99,21 @@ swiftlint
 
 ## JetBrains Editors (IntelliJ, RustRover, PyCharm, WebStorm, RubyMine, GoLand, etc)
 
-Some JetBrains IDEs have direct support for mise, others have support for asdf which can be used by first symlinking the mise tool directory which is the
+Some JetBrains IDEs have direct support for mise, others have support for asdf which can be used by
+first symlinking the mise tool directory which is the
 same layout as asdf:
 
 ```sh
-$ ln -s ~/.local/share/mise ~/.asdf
+ln -s ~/.local/share/mise ~/.asdf
 ```
 
 Then they should show up on in Project Settings:
 
-![](https://github.com/jdx/mise-docs/assets/216188/b34a0e3f-7af8-45c9-85b8-2c72bd1dc226)
+![project settings](https://github.com/jdx/mise-docs/assets/216188/b34a0e3f-7af8-45c9-85b8-2c72bd1dc226)
 
 Or in the case of node (possibly other languages), it's under "Languages & Frameworks":
 
-![](https://github.com/jdx/mise-docs/assets/216188/9926be1c-ab88-451a-8ace-edf2dac564b5)
+![languages & frameworks](https://github.com/jdx/mise-docs/assets/216188/9926be1c-ab88-451a-8ace-edf2dac564b5)
 
 ## VSCode
 
@@ -117,9 +129,17 @@ the tools in `launch.json`:
       "name": "Launch Program",
       "program": "${file}",
       "args": [],
-      "osx": { "runtimeExecutable": "mise" },
-      "linux": { "runtimeExecutable": "mise" },
-      "runtimeArgs": ["x", "--", "node"]
+      "osx": {
+        "runtimeExecutable": "mise"
+      },
+      "linux": {
+        "runtimeExecutable": "mise"
+      },
+      "runtimeArgs": [
+        "x",
+        "--",
+        "node"
+      ]
     }
   ]
 }
diff --git a/docs/lang/java.md b/docs/lang/java.md
index 7ddd1620d0..2d2a83ccdf 100644
--- a/docs/lang/java.md
+++ b/docs/lang/java.md
@@ -25,7 +25,8 @@ See available versions with `mise ls-remote java`.
 
 Some applications in macOS rely on `/usr/libexec/java_home` to find installed Java runtimes.
 
-To integrate an installed Java runtime with macOS run the following commands for the proper version (e.g. openjdk-20).
+To integrate an installed Java runtime with macOS run the following commands for the proper
+version (e.g. openjdk-20).
 
 ```sh
 sudo mkdir /Library/Java/JavaVirtualMachines/openjdk-20.jdk
@@ -38,29 +39,38 @@ sudo ln -s ~/.local/share/mise/installs/java/openjdk-20/Contents /Library/Java/J
 
 The Java core plugin supports the legacy version files `.java-version` and `.sdkmanrc`.
 
-For `.sdkmanrc` files, mise will try to map the vendor and version to the appropriate version string. For example, the version `20.0.2-tem` will be mapped to `temurin-20.0.2`. Due to Azul's Zulu versioning, the version `11.0.12-zulu` will be mapped to the major version `zulu-11`. Not all vendors available in SDKMAN are supported by mise. The following vendors are NOT supported: `bsg` (Bisheng), `graal` (GraalVM), `nik` (Liberica NIK).
+For `.sdkmanrc` files, mise will try to map the vendor and version to the appropriate version
+string. For example, the version `20.0.2-tem` will be mapped to `temurin-20.0.2`. Due to Azul's Zulu
+versioning, the version `11.0.12-zulu` will be mapped to the major version `zulu-11`. Not all
+vendors available in SDKMAN are supported by mise. The following vendors are NOT supported: `bsg` (
+Bisheng), `graal` (GraalVM), `nik` (Liberica NIK).
 
 In case an unsupported version of java is needed, some manual work is required:
 
 1. Download the unsupported version to a directory (e.g `~/.sdkman/candidates/java/21.0.1-open`)
 2. symlink the new version:
-   ```sh
-   ln -s ~/.sdkman/candidates/java/21.0.1-open ~/.local/share/mise/installs/java/21.0.1-open
-   ```
+
+```sh
+ln -s ~/.sdkman/candidates/java/21.0.1-open ~/.local/share/mise/installs/java/21.0.1-open
+```
+
 3. If on Mac:
-  ```sh
-  mkdir ~/.local/share/mise/installs/java/21.0.1-open/Contents
-  mkdir ~/.local/share/mise/installs/java/21.0.1-open/Contents/MacOS
-  
-  ln -s ~/.sdkman/candidates/java/21.0.1-open ~/.local/share/mise/installs/java/21.0.1-open/Contents/Home
-  cp ~/.local/share/mise/installs/java/21.0.1-open/lib/libjli.dylib ~/.local/share/mise/installs/java/21.0.1-open/Contents/MacOS/libjli.dylib
-  ```
-4. Don't forget to make sure the cache is blocked and valid, by making sure an **empty** directory **exists** for your version in the [mise cache](https://mise.jdx.dev/directories.html#cache-mise):
+
+```sh
+mkdir ~/.local/share/mise/installs/java/21.0.1-open/Contents
+mkdir ~/.local/share/mise/installs/java/21.0.1-open/Contents/MacOS
+
+ln -s ~/.sdkman/candidates/java/21.0.1-open ~/.local/share/mise/installs/java/21.0.1-open/Contents/Home
+cp ~/.local/share/mise/installs/java/21.0.1-open/lib/libjli.dylib ~/.local/share/mise/installs/java/21.0.1-open/Contents/MacOS/libjli.dylib
+```
+
+4. Don't forget to make sure the cache is blocked and valid, by making sure an **empty** directory *
+   *exists** for your version in the [mise cache](https://mise.jdx.dev/directories.html#cache-mise):
    e.g.
-   ```sh
-   $ ls -R $MISE_CACHE_DIR/java
-   21.0.1-open
-   
-   mise/java/21.0.1-open:
 
-   ```
+```sh
+$ ls -R $MISE_CACHE_DIR/java
+21.0.1-open
+
+mise/java/21.0.1-open:
+```
diff --git a/docs/lang/python.md b/docs/lang/python.md
index 968c9e22de..ff0ef63ad4 100644
--- a/docs/lang/python.md
+++ b/docs/lang/python.md
@@ -69,7 +69,7 @@ Specify the OS to use for precompiled binaries.
 Specify the architecture to use for precompiled binaries. If on an old CPU, you may want to set this
 to
 `"x86_64"` for the most compatible binaries.
-See https://gregoryszorc.com/docs/python-build-standalone/main/running.html for more information.
+See <https://gregoryszorc.com/docs/python-build-standalone/main/running.html> for more information.
 
 ### `python_patch_url`
 
@@ -124,7 +124,7 @@ If you'd like to disable these binaries, set [`python_compile`](#python_compile)
 
 These binaries may not work on older CPUs however you may opt into binaries which
 are more compatible with older CPUs by setting `MISE_PYTHON_PRECOMPILED_ARCH` with
-a different version. See https://gregoryszorc.com/docs/python-build-standalone/main/running.html for
+a different version. See <https://gregoryszorc.com/docs/python-build-standalone/main/running.html> for
 more information
 on this option. Set it to "x86_64" for the most compatible binaries.
 
diff --git a/docs/lang/rust.md b/docs/lang/rust.md
index 42ce485259..ccd04bfa1a 100644
--- a/docs/lang/rust.md
+++ b/docs/lang/rust.md
@@ -1,8 +1,8 @@
 # Rust
 
 Rust is not currently offered as a core plugin. In fact, I don't think you
-should actually use mise for rust development. Rust has an official version 
-manager called [`rustup`](https://rustup.rs/) that is better than what any of 
+should actually use mise for rust development. Rust has an official version
+manager called [`rustup`](https://rustup.rs/) that is better than what any of
 the current mise plugins offer.
 
 You install [rustup](https://rustup.rs/) with the following:
@@ -29,11 +29,10 @@ so you could do something like this:
 rust = "nightly"
 ```
 
-
 Where that would basically be equivalent to:
 
 ```sh
-$ rustup override set nightly
+rustup override set nightly
 ```
 
 Frankly though, this isn't high on my priority list. Use rustup. It's great.
diff --git a/docs/logo-dark.png b/docs/logo-dark.png
new file mode 100644
index 0000000000..a24cd0dde3
Binary files /dev/null and b/docs/logo-dark.png differ
diff --git a/docs/logo-dark@2x.png b/docs/logo-dark@2x.png
new file mode 100644
index 0000000000..d423105636
Binary files /dev/null and b/docs/logo-dark@2x.png differ
diff --git a/docs/logo-light.png b/docs/logo-light.png
new file mode 100644
index 0000000000..8b50fdd5bd
Binary files /dev/null and b/docs/logo-light.png differ
diff --git a/docs/logo-light@2x.png b/docs/logo-light@2x.png
new file mode 100644
index 0000000000..d17dd0d899
Binary files /dev/null and b/docs/logo-light@2x.png differ
diff --git a/docs/paranoid.md b/docs/paranoid.md
index c615eb3449..c1b580d549 100644
--- a/docs/paranoid.md
+++ b/docs/paranoid.md
@@ -1,14 +1,14 @@
 # Paranoid
 
 Paranoid is an optional behavior that locks mise down more to make it harder
-for a bad actor to compromise your system. These are settings that I 
+for a bad actor to compromise your system. These are settings that I
 personally do not use on my own system because I find the behavior too
 restrictive for the benefits.
 
 Paranoid mode can be enabled with either `MISE_PARANOID=1` or a setting:
 
 ```sh
-$ mise settings set paranoid 1
+mise settings set paranoid 1
 ```
 
 ## Config files
@@ -40,7 +40,7 @@ Other than that, say for "shfmt", you'll need to specify the full git repo
 to install:
 
 ```sh
-$ mise plugin install shfmt https://github.com/luizm/asdf-shfmt
+mise plugin install shfmt https://github.com/luizm/asdf-shfmt
 ```
 
 Unlike in normal mode where `mise plugin install shfmt` would be sufficient.
diff --git a/docs/rtx.md b/docs/rtx.md
index c2a9961061..2f35f3bece 100644
--- a/docs/rtx.md
+++ b/docs/rtx.md
@@ -33,7 +33,7 @@ If you build infrastructure where users may still be calling `rtx activate` in t
 shell rc scripts, you can create a symlink `ln -s /path/to/mise /path/to/rtx` so
 `rtx activate` still functions.
 
-For https://mise.run, we're using `~/.local/bin/mise`
+For <https://mise.run>, we're using `~/.local/bin/mise`
 as the executable PATH instead of the old directory `~/.local/share/rtx/bin/mise`
 to keep things a bit cleaner. You can still use the old style if you like by setting
 `MISE_INSTALL_PATH`.
diff --git a/docs/team.md b/docs/team.md
index 6e6c22a1d6..6c0617bc0f 100644
--- a/docs/team.md
+++ b/docs/team.md
@@ -37,6 +37,7 @@ const board = [
   }
 ]
 </script>
+
 # Team
 
 Jeff Dickey is the primary developer behind mise. He does the bulk
diff --git a/docs/tips-and-tricks.md b/docs/tips-and-tricks.md
index f225204c7c..0c428a7ad0 100644
--- a/docs/tips-and-tricks.md
+++ b/docs/tips-and-tricks.md
@@ -27,7 +27,7 @@ If `~/.local/bin` is not in PATH, you'll need to prefix all commands with `~/.lo
 Now you can use `mise-x64` to install tools:
 
 ```sh
-$ mise-x64 use -g node@20
+mise-x64 use -g node@20
 ```
 
 ## Shebang
@@ -78,5 +78,5 @@ jobs:
 Instead of manually editing `.mise.toml` to add env vars, you can use `mise set` instead:
 
 ```sh
-$ mise set NODE_ENV=production
+mise set NODE_ENV=production
 ```
diff --git a/scripts/publish-r2.sh b/scripts/publish-r2.sh
index fefa21985c..6b27fa4093 100755
--- a/scripts/publish-r2.sh
+++ b/scripts/publish-r2.sh
@@ -8,4 +8,4 @@ export AWS_ACCESS_KEY_ID=$CLOUDFLARE_ACCESS_KEY_ID
 export AWS_SECRET_ACCESS_KEY=$CLOUDFLARE_SECRET_ACCESS_KEY
 export AWS_S3_BUCKET=mise
 
-./mise/scripts/publish-s3.sh
+./scripts/publish-s3.sh
diff --git a/scripts/publish-s3.sh b/scripts/publish-s3.sh
index c9456c1d13..076bf81447 100755
--- a/scripts/publish-s3.sh
+++ b/scripts/publish-s3.sh
@@ -12,9 +12,9 @@ aws s3 cp "$RELEASE_DIR" "s3://$AWS_S3_BUCKET/" --cache-control "$cache_day" --n
 aws s3 cp "$RELEASE_DIR/VERSION" "s3://$AWS_S3_BUCKET/" --cache-control "$cache_day" --no-progress --content-type "text/plain"
 aws s3 cp "$RELEASE_DIR/install.sh" "s3://$AWS_S3_BUCKET/" --cache-control "$cache_day" --no-progress --content-type "text/plain"
 aws s3 cp "$RELEASE_DIR/install.sh.sig" "s3://$AWS_S3_BUCKET/" --cache-control "$cache_day" --no-progress
-aws s3 cp "./mise/schema/mise.json" "s3://$AWS_S3_BUCKET/schema/mise.json" --cache-control "$cache_day" --no-progress --content-type "application/json"
-aws s3 cp "./mise/schema/settings.json" "s3://$AWS_S3_BUCKET/schema/settings.json" --cache-control "$cache_day" --no-progress --content-type "application/json"
-aws s3 cp "./mise/schema/mise.plugin.json" "s3://$AWS_S3_BUCKET/schema/mise.plugin.json" --cache-control "$cache_day" --no-progress --content-type "application/json"
+aws s3 cp "./schema/mise.json" "s3://$AWS_S3_BUCKET/schema/mise.json" --cache-control "$cache_day" --no-progress --content-type "application/json"
+aws s3 cp "./schema/settings.json" "s3://$AWS_S3_BUCKET/schema/settings.json" --cache-control "$cache_day" --no-progress --content-type "application/json"
+aws s3 cp "./schema/mise.plugin.json" "s3://$AWS_S3_BUCKET/schema/mise.plugin.json" --cache-control "$cache_day" --no-progress --content-type "application/json"
 
 aws s3 cp artifacts/rpm/mise.repo "s3://$AWS_S3_BUCKET/rpm/" --cache-control "$cache_day" --no-progress
 aws s3 cp artifacts/rpm/packages/ "s3://$AWS_S3_BUCKET/rpm/packages/" --cache-control "$cache_week" --no-progress --recursive
diff --git a/scripts/release.sh b/scripts/release.sh
index 6650af15d9..0ef1b2a9ca 100755
--- a/scripts/release.sh
+++ b/scripts/release.sh
@@ -5,8 +5,8 @@ echo "::group::Setup"
 git config --global user.name mise-en-dev
 git config --global user.email 123107610+mise-en-dev@users.noreply.github.com
 
-BASE_DIR="$(cd mise && pwd)"
-MISE_VERSION=$(cd mise && ./scripts/get-version.sh)
+BASE_DIR="$(pwd)"
+MISE_VERSION=$(./scripts/get-version.sh)
 RELEASE_DIR=releases
 export BASE_DIR MISE_VERSION RELEASE_DIR
 rm -rf "${RELEASE_DIR:?}/$MISE_VERSION"
@@ -65,28 +65,16 @@ gpg --clearsign -u 8B81C9D17413A06D <SHASUMS512.txt >SHASUMS512.asc
 popd
 
 echo "::group::install.sh"
-./mise/scripts/render-install.sh >"$RELEASE_DIR"/install.sh
+./scripts/render-install.sh >"$RELEASE_DIR"/install.sh
 chmod +x "$RELEASE_DIR"/install.sh
 shellcheck "$RELEASE_DIR"/install.sh
 gpg -u 8B81C9D17413A06D --output "$RELEASE_DIR"/install.sh.sig --sign "$RELEASE_DIR"/install.sh
 
 if [[ "$DRY_RUN" != 1 ]]; then
   echo "::group::Publish npm @jdxcode/mise"
-  NPM_PREFIX=@jdxcode/mise ./mise/scripts/release-npm.sh
+  NPM_PREFIX=@jdxcode/mise ./scripts/release-npm.sh
   #  echo "::group::Publish npm mise-cli"
-  #  NPM_PREFIX=mise-cli ./mise/scripts/release-npm.sh
+  #  NPM_PREFIX=mise-cli ./scripts/release-npm.sh
   echo "::group::Publish r2"
-  ./mise/scripts/publish-r2.sh
+  ./scripts/publish-r2.sh
 fi
-
-echo "::group::Publish mise-docs"
-cp ./mise/docs/registry.md ./mise-docs/registry.md
-cp ./mise/docs/cli-reference.md ./mise-docs/cli/index.md
-pushd mise-docs
-if [[ -z $(git status -s) ]]; then
-  echo "No changes to docs"
-else
-  git add cli/index.md registry.md
-  git commit -m "mise ${MISE_VERSION#v}"
-fi
-popd
diff --git a/src/cli/render_help.rs b/src/cli/render_help.rs
index f72f3f7a12..1e108487fc 100644
--- a/src/cli/render_help.rs
+++ b/src/cli/render_help.rs
@@ -14,7 +14,7 @@ pub struct RenderHelp {}
 
 impl RenderHelp {
     pub fn run(self) -> Result<()> {
-        let readme = file::read_to_string("docs/cli-reference.md")?;
+        let readme = file::read_to_string("docs/cli/index.md")?;
         let mut current_readme = readme.split("<!-- MISE:COMMANDS -->");
 
         let mut doc = String::new();
@@ -23,7 +23,7 @@ impl RenderHelp {
         doc.push_str(render_commands().as_str());
         doc.push_str(current_readme.next().unwrap());
         doc = remove_trailing_spaces(&doc) + "\n";
-        file::write("docs/cli-reference.md", &doc)?;
+        file::write("docs/cli/index.md", &doc)?;
         Ok(())
     }
 }
@@ -125,9 +125,9 @@ mod tests {
     #[test]
     fn test_render_help() {
         reset();
-        file::create_dir_all("docs").unwrap();
+        file::create_dir_all("docs/cli").unwrap();
         file::write(
-            "docs/cli-reference.md",
+            "docs/cli/index.md",
             indoc! {r#"
             <!-- MISE:COMMANDS -->
             <!-- MISE:COMMANDS -->
@@ -135,8 +135,8 @@ mod tests {
         )
         .unwrap();
         assert_cli!("render-help");
-        let readme = fs::read_to_string("docs/cli-reference.md").unwrap();
+        let readme = fs::read_to_string("docs/cli/index.md").unwrap();
         assert!(readme.contains("# Commands"));
-        file::remove_file("docs/cli-reference.md").unwrap();
+        file::remove_file("docs/cli/index.md").unwrap();
     }
 }
diff --git a/src/shell/nushell.rs b/src/shell/nushell.rs
index a2d83e25d3..5a32641b5e 100644
--- a/src/shell/nushell.rs
+++ b/src/shell/nushell.rs
@@ -109,13 +109,15 @@ impl Shell for Nushell {
 #[cfg(test)]
 mod tests {
     use insta::assert_snapshot;
+    use test_log::test;
 
-    use crate::test::replace_path;
+    use crate::test::{replace_path, reset};
 
     use super::*;
 
     #[test]
     fn test_hook_init() {
+        reset();
         let nushell = Nushell::default();
         let exe = Path::new("/some/dir/mise");
         assert_snapshot!(nushell.activate(exe, " --status".into()));
@@ -123,22 +125,26 @@ mod tests {
 
     #[test]
     fn test_set_env() {
+        reset();
         assert_snapshot!(Nushell::default().set_env("FOO", "1"));
     }
 
     #[test]
     fn test_prepend_env() {
+        reset();
         let sh = Nushell::default();
         assert_snapshot!(replace_path(&sh.prepend_env("PATH", "/some/dir:/2/dir")));
     }
 
     #[test]
     fn test_unset_env() {
+        reset();
         assert_snapshot!(Nushell::default().unset_env("FOO"));
     }
 
     #[test]
     fn test_deactivate() {
+        reset();
         let deactivate = Nushell::default().deactivate();
         assert_snapshot!(replace_path(&deactivate));
     }
diff --git a/src/toolset/tool_version_request.rs b/src/toolset/tool_version_request.rs
index d7584629fb..f3083cb2de 100644
--- a/src/toolset/tool_version_request.rs
+++ b/src/toolset/tool_version_request.rs
@@ -204,10 +204,13 @@ impl Display for ToolRequest {
 #[cfg(test)]
 mod tests {
     use super::version_sub;
+    use crate::backend::reset;
     use pretty_assertions::assert_str_eq;
+    use test_log::test;
 
     #[test]
     fn test_version_sub() {
+        reset();
         assert_str_eq!(version_sub("18.2.3", "2"), "16");
         assert_str_eq!(version_sub("18.2.3", "0.1"), "18.1");
     }