diff --git a/.gitignore b/.gitignore
index 68774079..31fbfa9f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -17,6 +17,6 @@ web-ext.config.ts
 templates/*/pnpm-lock.yaml
 templates/*/yarn.lock
 templates/*/package-lock.json
-docs/api
+docs/api/reference
 stats.html
 .tool-versions
diff --git a/docs/guide/development.md b/docs/.old/development.md
similarity index 91%
rename from docs/guide/development.md
rename to docs/.old/development.md
index 0ccdd499..50098add 100644
--- a/docs/guide/development.md
+++ b/docs/.old/development.md
@@ -33,7 +33,7 @@ For production builds, none of the above modifications will be applied, and you'
 
 ## Configure Browser Startup
 
-WXT uses [`web-ext` by Mozilla](https://github.com/mozilla/web-ext) to automatically open a browser with the extension installed. You can configure the runner's behavior via the [`runner`](/api/wxt/interfaces/InlineConfig#runner) option, or in a separate gitignored file, `web-ext.config.ts`.
+WXT uses [`web-ext` by Mozilla](https://github.com/mozilla/web-ext) to automatically open a browser with the extension installed. You can configure the runner's behavior via the [`runner`](/api/reference/wxt/interfaces/InlineConfig#runner) option, or in a separate gitignored file, `web-ext.config.ts`.
 
 :::code-group
 
@@ -59,7 +59,7 @@ export default defineRunnerConfig({
 
 ### Browser Binaries
 
-`web-ext`'s browser discovery is very limited. By default, it only guesses at where Chrome and Firefox are installed. If you've customized your install locations, you may need to tell `web-ext` where the binaries/executables are located using the [`binaries` option](/api/wxt/interfaces/ExtensionRunnerConfig#binaries). For other Chromium based browsers, like Edge or Opera, you'll need to explicitly list them in the `binaries` option as well, otherwise they will open in Chrome by default.
+`web-ext`'s browser discovery is very limited. By default, it only guesses at where Chrome and Firefox are installed. If you've customized your install locations, you may need to tell `web-ext` where the binaries/executables are located using the [`binaries` option](/api/reference/wxt/interfaces/ExtensionRunnerConfig#binaries). For other Chromium based browsers, like Edge or Opera, you'll need to explicitly list them in the `binaries` option as well, otherwise they will open in Chrome by default.
 
 ```ts
 // ~/web-ext.config.ts
@@ -93,7 +93,7 @@ export default defineRunnerConfig({
 });
 ```
 
-For a full list of options, see the [API Reference](/api/wxt/interfaces/ExtensionRunnerConfig).
+For a full list of options, see the [API Reference](/api/reference/wxt/interfaces/ExtensionRunnerConfig).
 
 ## Reload the Extension
 
diff --git a/docs/.vitepress/components/UsingWxtSection.vue b/docs/.vitepress/components/UsingWxtSection.vue
index ca6072ce..3181db63 100644
--- a/docs/.vitepress/components/UsingWxtSection.vue
+++ b/docs/.vitepress/components/UsingWxtSection.vue
@@ -54,90 +54,56 @@ function getStoreUrl(extension: ChromeExtension) {
 </script>
 
 <template>
-  <section class="vp-doc">
-    <div class="container">
-      <h2 id="whos-using-wxt">Who's Using WXT?</h2>
-      <p>
-        Battle tested and ready for production. Explore chrome extensions made
-        with WXT.
-      </p>
-      <p v-if="isLoading" style="text-align: center; opacity: 50%">
-        Loading...
-      </p>
-      <p
-        v-else-if="err || sortedExtensions.length === 0"
-        style="text-align: center; opacity: 50%"
-      >
-        Failed to load extension details.
-      </p>
-      <ul v-else>
-        <li
-          v-for="extension of sortedExtensions"
-          :key="extension.id"
-          class="relative"
-        >
-          <img
-            :src="extension.iconUrl"
-            :alt="`${extension.name} icon`"
-            referrerpolicy="no-referrer"
-          />
-          <div class="relative">
-            <a
-              :href="getStoreUrl(extension)"
-              target="_blank"
-              :title="extension.name"
-              class="extension-name"
-              >{{ extension.name }}</a
-            >
-            <p class="description" :title="extension.shortDescription">
-              {{ extension.shortDescription }}
-            </p>
-          </div>
-          <p class="user-count">
-            <span>{{ extension.weeklyActiveUsers.toLocaleString() }} users</span
-            ><template v-if="extension.rating != null"
-              >,
-              <span>{{ extension.rating }} stars</span>
-            </template>
-          </p>
-        </li>
-      </ul>
-      <p class="centered pr">
+  <p v-if="isLoading" style="text-align: center; opacity: 50%">Loading...</p>
+  <p
+    v-else-if="err || sortedExtensions.length === 0"
+    style="text-align: center; opacity: 50%"
+  >
+    Failed to load extension details.
+  </p>
+  <ul v-else>
+    <li
+      v-for="extension of sortedExtensions"
+      :key="extension.id"
+      class="relative"
+    >
+      <img
+        :src="extension.iconUrl"
+        :alt="`${extension.name} icon`"
+        referrerpolicy="no-referrer"
+      />
+      <div class="relative">
         <a
-          href="https://github.com/wxt-dev/wxt/edit/main/docs/.vitepress/components/UsingWxtSection.vue"
+          :href="getStoreUrl(extension)"
           target="_blank"
-          >Open a PR</a
+          :title="extension.name"
+          class="extension-name"
+          >{{ extension.name }}</a
         >
-        to add your extension to the list!
+        <p class="description" :title="extension.shortDescription">
+          {{ extension.shortDescription }}
+        </p>
+      </div>
+      <p class="user-count">
+        <span>{{ extension.weeklyActiveUsers.toLocaleString() }} users</span
+        ><template v-if="extension.rating != null"
+          >,
+          <span>{{ extension.rating }} stars</span>
+        </template>
       </p>
-    </div>
-  </section>
+    </li>
+  </ul>
+  <p class="centered pr">
+    <a
+      href="https://github.com/wxt-dev/wxt/edit/main/docs/.vitepress/components/UsingWxtSection.vue"
+      target="_blank"
+      >Open a PR</a
+    >
+    to add your extension to the list!
+  </p>
 </template>
 
 <style scoped>
-.vp-doc {
-  padding: 0 24px;
-}
-
-@media (min-width: 640px) {
-  .vp-doc {
-    padding: 0 48px;
-  }
-}
-
-@media (min-width: 960px) {
-  .vp-doc {
-    padding: 0 64px;
-  }
-}
-
-.container {
-  max-width: 1152px;
-  margin: 0 auto;
-  display: flex;
-  flex-direction: column;
-}
-
 li img {
   width: 116px;
   height: 116px;
diff --git a/docs/.vitepress/config.ts b/docs/.vitepress/config.ts
index dd6dd34e..4a49e248 100644
--- a/docs/.vitepress/config.ts
+++ b/docs/.vitepress/config.ts
@@ -1,6 +1,5 @@
 import { DefaultTheme, defineConfig } from 'vitepress';
-import { generateCliDocs } from './plugins/generate-cli-docs';
-import typedocSidebar from '../api/typedoc-sidebar.json';
+import typedocSidebar from '../api/reference/typedoc-sidebar.json';
 
 const filteredTypedocSidebar = typedocSidebar.filter(
   (item) => item.text !== 'API',
@@ -31,7 +30,6 @@ export default defineConfig({
   description,
   vite: {
     clearScreen: false,
-    plugins: [generateCliDocs()],
   },
   lastUpdated: true,
   sitemap: {
@@ -69,77 +67,152 @@ export default defineConfig({
     },
 
     nav: [
-      { text: 'Guide', link: '/guide/installation.md' },
-      { text: 'Entrypoints', link: '/entrypoints/background.md' },
-      { text: 'Examples', link: '/examples.md' },
-      { text: 'API', link: '/api/cli.md' },
+      { text: 'Get Started', link: '/get-started/introduction' },
+      { text: 'Guide', link: '/guide/key-concepts/manifest' },
+      { text: 'Examples', link: '/examples' },
+      { text: 'API', link: '/api/reference/wxt' },
     ],
 
     sidebar: {
-      '/guide/': [
+      '/get-started/': [
         {
-          text: 'Guide',
+          text: 'Get Started',
+          base: '/get-started/',
           items: [
-            { text: 'Introduction', link: '/guide/introduction.md' },
-            { text: 'Installation', link: '/guide/installation.md' },
-            { text: 'Configuration', link: '/guide/configuration.md' },
-            { text: 'Entrypoints', link: '/guide/entrypoints.md' },
-            { text: 'Manifest.json', link: '/guide/manifest.md' },
-            { text: 'Extension APIs', link: '/guide/extension-apis.md' },
-            { text: 'Storage', link: '/guide/storage.md' },
-            { text: 'Assets', link: '/guide/assets.md' },
-            { text: 'Content Script UI', link: '/guide/content-script-ui.md' },
-            { text: 'Multiple Browsers', link: '/guide/multiple-browsers.md' },
-            { text: 'ES Modules', link: '/guide/esm.md' },
-            { text: 'Auto-imports', link: '/guide/auto-imports.md' },
-            { text: 'Vite', link: '/guide/vite.md' },
-            { text: 'Remote Code', link: '/guide/remote-code.md' },
-            { text: 'Publishing', link: '/guide/publishing.md' },
-            { text: 'Handling Updates', link: '/guide/handling-updates.md' },
-            { text: 'Development', link: '/guide/development.md' },
-            { text: 'Testing', link: '/guide/testing.md' },
-          ],
-        },
-        {
-          text: 'Other',
-          items: [
-            { text: 'Migrate to WXT', link: '/guide/migrate-to-wxt.md' },
-            { text: 'Compare', link: '/guide/compare.md' },
+            { text: 'Introduction', link: 'introduction' },
+            { text: 'Installation', link: 'installation' },
+            { text: 'Configuration', link: 'configuration' },
+            { text: 'Entrypoints', link: 'entrypoints' },
+            { text: 'Assets', link: 'assets' },
+            { text: 'Testing', link: 'testing' },
+            { text: 'Publishing', link: 'publishing' },
+            { text: 'Migrate to WXT', link: 'migrate-to-wxt' },
+            { text: 'Compare', link: 'compare' },
           ],
         },
       ],
-      '/entrypoints/': [
+      '/guide/': [
         {
-          text: 'Entrypoints',
           items: [
-            { text: 'Background', link: '/entrypoints/background.md' },
-            { text: 'Bookmarks', link: '/entrypoints/bookmarks.md' },
             {
-              text: 'Content Scripts',
-              link: '/entrypoints/content-scripts.md',
+              text: 'Key Concepts',
+              collapsed: true,
+              base: '/guide/key-concepts/',
+              items: [
+                { text: 'Manifest', link: 'manifest' },
+                { text: 'Auto-imports', link: 'auto-imports' },
+                {
+                  text: 'Web Extension Polyfill',
+                  link: 'web-extension-polyfill',
+                },
+                { text: 'Frontend Frameworks', link: 'frontend-frameworks' },
+                { text: 'Content Script UI', link: 'content-script-ui' },
+              ],
             },
-            { text: 'CSS', link: '/entrypoints/css.md' },
-            { text: 'Devtools', link: '/entrypoints/devtools.md' },
-            { text: 'History', link: '/entrypoints/history.md' },
-            { text: 'Newtab', link: '/entrypoints/newtab.md' },
-            { text: 'Options', link: '/entrypoints/options.md' },
-            { text: 'Popup', link: '/entrypoints/popup.md' },
-            { text: 'Sandbox', link: '/entrypoints/sandbox.md' },
-            { text: 'Side Panel', link: '/entrypoints/sidepanel.md' },
-            { text: 'Unlisted Pages', link: '/entrypoints/unlisted-pages.md' },
             {
-              text: 'Unlisted Scripts',
-              link: '/entrypoints/unlisted-scripts.md',
+              text: 'Directory Structure',
+              collapsed: true,
+              base: '/guide/directory-structure/',
+              items: [
+                // Folders
+                { text: '.output/', link: 'output' },
+                { text: '.wxt/', link: 'wxt' },
+                { text: 'assets/', link: 'assets' },
+                { text: 'components/', link: 'components' },
+                { text: 'composables/', link: 'composables' },
+                {
+                  text: 'entrypoints/',
+                  base: '/guide/directory-structure/entrypoints/',
+                  collapsed: true,
+                  items: [
+                    { text: 'background', link: 'background.md' },
+                    { text: 'bookmarks', link: 'bookmarks.md' },
+                    { text: '*.content.ts', link: 'content-scripts.md' },
+                    { text: '*.css', link: 'css.md' },
+                    { text: 'devtools', link: 'devtools.md' },
+                    { text: 'history', link: 'history.md' },
+                    { text: 'newtab', link: 'newtab.md' },
+                    { text: 'options', link: 'options.md' },
+                    { text: 'popup', link: 'popup.md' },
+                    { text: 'sandbox', link: 'sandbox.md' },
+                    { text: 'sidepanel', link: 'sidepanel.md' },
+                    { text: '*.html', link: 'unlisted-pages.md' },
+                    {
+                      text: '*.ts',
+                      link: 'unlisted-scripts.md',
+                    },
+                  ],
+                },
+                { text: 'hooks/', link: 'hooks' },
+                { text: 'modules/', link: 'modules' },
+                {
+                  text: 'public/',
+                  link: 'public',
+                  items: [{ text: '_locales/', link: 'public/locales' }],
+                },
+                { text: 'utils/', link: 'modules' },
+                // Files
+                { text: '.env', link: 'env' },
+                { text: 'package.json', link: 'package' },
+                { text: 'tsconfig.json', link: 'tsconfig' },
+                { text: 'web-ext.config.ts', link: 'web-ext-config' },
+                { text: 'wxt.config.ts', link: 'wxt-config' },
+              ],
             },
-          ].sort((l, r) => l.text.localeCompare(r.text)),
+            {
+              text: 'Extension APIs',
+              collapsed: true,
+              base: '/guide/extension-apis/',
+              items: [
+                { text: 'Storage', link: 'storage' },
+                { text: 'Messaging', link: 'messaging' },
+                { text: 'Scripting', link: 'scripting' },
+                { text: 'Others', link: 'others' },
+              ],
+            },
+            {
+              text: 'Go Further',
+              collapsed: true,
+              base: '/guide/go-further/',
+              items: [
+                { text: 'Testing', link: 'testing' },
+                { text: 'ES Modules', link: 'es-modules' },
+                { text: 'Debugging', link: 'debugging' },
+                { text: 'Handling Updates', link: 'handling-updates' },
+                { text: 'Vite', link: 'vite' },
+                { text: 'Custom Events', link: 'custom-events' },
+                { text: 'Remote Code', link: 'remote-code' },
+                {
+                  text: 'Entrypoint Side Effects',
+                  link: 'entrypoint-side-effects',
+                },
+                { text: 'How WXT Works', link: 'how-wxt-works' },
+              ],
+            },
+          ],
         },
       ],
       '/api/': [
         {
           items: [
-            { text: 'CLI', link: '/api/cli.md' },
             {
-              text: 'Modules',
+              text: 'CLI',
+              collapsed: true,
+              base: '/api/cli/',
+              items: [
+                { text: 'wxt', link: 'wxt.md' },
+                { text: 'wxt build', link: 'wxt-build.md' },
+                { text: 'wxt zip', link: 'wxt-zip.md' },
+                { text: 'wxt prepare', link: 'wxt-prepare.md' },
+                { text: 'wxt clean', link: 'wxt-clean.md' },
+                { text: 'wxt init', link: 'wxt-init.md' },
+                { text: 'wxt submit', link: 'wxt-submit.md' },
+                { text: 'wxt submit init', link: 'wxt-submit-init.md' },
+              ],
+            },
+            {
+              text: 'API Reference',
+              collapsed: true,
               items: filteredTypedocSidebar,
             },
           ],
diff --git a/docs/.vitepress/loaders/cli.data.ts b/docs/.vitepress/loaders/cli.data.ts
new file mode 100644
index 00000000..c99d9484
--- /dev/null
+++ b/docs/.vitepress/loaders/cli.data.ts
@@ -0,0 +1,60 @@
+import { resolve, join } from 'node:path';
+import consola from 'consola';
+import { execaCommand } from 'execa';
+
+const cliDir = resolve('packages/wxt/src/cli/commands');
+const cliDirGlob = resolve(cliDir, '**');
+
+export default {
+  watch: [cliDirGlob],
+  async load() {
+    consola.info(`Generating CLI docs`);
+
+    const [wxt, build, zip, prepare, clean, init, submit, submitInit] =
+      await Promise.all([
+        getWxtHelp(''),
+        getWxtHelp('build'),
+        getWxtHelp('zip'),
+        getWxtHelp('prepare'),
+        getWxtHelp('clean'),
+        getWxtHelp('init'),
+        getPublishExtensionHelp(''),
+        getPublishExtensionHelp('init'),
+      ]);
+
+    consola.success(`Generated CLI docs`);
+    return {
+      wxt,
+      build,
+      zip,
+      prepare,
+      clean,
+      init,
+      submit,
+      submitInit,
+    };
+  },
+};
+
+async function getHelp(command: string): Promise<string> {
+  const res = await execaCommand(command + ' --help', {
+    cwd: 'packages/wxt',
+  });
+  return res.stdout;
+}
+
+function getWxtHelp(command: string): Promise<string> {
+  return getHelp(`pnpm -s wxt ${command}`.trim());
+}
+
+async function getPublishExtensionHelp(command: string): Promise<string> {
+  const res = await getHelp(
+    `./node_modules/.bin/publish-extension ${command}`.trim(),
+  );
+  return res.replace(/\$ publish-extension/g, '$ wxt submit');
+}
+
+export interface Command {
+  name: string;
+  docs: string;
+}
diff --git a/docs/.vitepress/plugins/cli.tpl.md b/docs/.vitepress/plugins/cli.tpl.md
deleted file mode 100644
index 85d34d48..00000000
--- a/docs/.vitepress/plugins/cli.tpl.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# CLI Reference
-
-> Reference generated from `wxt <command> --help`
-
-{{ DOCS }}
diff --git a/docs/.vitepress/plugins/generate-cli-docs.ts b/docs/.vitepress/plugins/generate-cli-docs.ts
deleted file mode 100644
index 104807bb..00000000
--- a/docs/.vitepress/plugins/generate-cli-docs.ts
+++ /dev/null
@@ -1,118 +0,0 @@
-import { relative, resolve } from 'node:path';
-import { readFileSync, writeFileSync } from 'node:fs';
-import { format } from 'prettier';
-import consola from 'consola';
-import { execaCommand } from 'execa';
-
-let hasGenerated = false;
-
-const cliDir = resolve('packages/wxt/src/cli/commands');
-const cliDirGlob = resolve(cliDir, '**');
-const cliTemplatePath = resolve('docs/.vitepress/plugins/cli.tpl.md');
-const cliPath = resolve('docs/api/cli.md');
-
-const PREFACE = `<!--
-DO NOT EDIT
-Generated by \`wxt/docs/.vitepress/plugins/generate-config-docs.ts\`
-To make changes to the config reference, update the JSDoc in \`src/core/types/external.ts\`.
--->`;
-
-export function generateCliDocs() {
-  writeFileSync(cliPath, '');
-
-  const generateDocs = async () => {
-    consola.info(`Generating ${relative(process.cwd(), cliPath)}`);
-    try {
-      const res = await execaCommand('pnpm -s wxt --help', {
-        cwd: 'packages/wxt',
-      });
-      const dev = splitInfo(res.stdout);
-      const lines: Array<string | string[]> = [
-        `## \`wxt\``,
-        '```sh',
-        dev.rest,
-        '```',
-      ];
-
-      const commands = await Promise.allSettled(
-        extractCommands(dev.info).map(async (command) => {
-          const res = await execaCommand(`pnpm -s wxt ${command} --help`, {
-            cwd: 'packages/wxt',
-          });
-          const { rest: docs } = splitInfo(res.stdout);
-          return [`## \`wxt ${command}\``, '```sh', docs, '```'];
-        }),
-      );
-      lines.push(
-        ...commands
-          .filter((res) => res.status === 'fulfilled')
-          .map(
-            (res) => (res as unknown as PromiseFulfilledResult<string>).value,
-          ),
-      );
-
-      const text = await format(
-        PREFACE +
-          '\n\n' +
-          readFileSync(cliTemplatePath, 'utf-8').replace(
-            '{{ DOCS }}',
-            lines.flat().join('\n'),
-          ),
-        { parser: 'markdown' },
-      );
-
-      writeFileSync(cliPath, text);
-      consola.success(`Generated ${relative(process.cwd(), cliPath)}`);
-    } catch (err) {
-      consola.fail(`Failed to generate ${relative(process.cwd(), cliPath)}`);
-      consola.error(err.message);
-    }
-  };
-
-  return {
-    name: 'docs:generate-cli-docs',
-    async config() {
-      if (!hasGenerated) {
-        hasGenerated = true;
-        await generateDocs();
-      }
-    },
-    configureServer(server: any) {
-      server.watcher.add(cliDirGlob);
-    },
-    async handleHotUpdate(ctx: { file: string }) {
-      if (ctx.file === cliTemplatePath || ctx.file.includes(cliDir)) {
-        await generateDocs();
-      }
-    },
-  };
-}
-
-function splitInfo(text: string): { info: string; rest: string } {
-  const infoStart = text.indexOf('For more info,');
-  const infoEnd = text.indexOf('\n\nOptions:');
-
-  if (infoStart === -1 || infoEnd === -1) {
-    return { info: '', rest: text };
-  }
-
-  const info = text.substring(infoStart, infoEnd).trim();
-  const rest = text.replace(info, '').trim().replace('\n\n\n\n', '\n\n');
-
-  return { info, rest };
-}
-
-function extractCommands(info: string): string[] {
-  const commands: string[] = [];
-
-  // Split the info by line and iterate through each line
-  info.split('\n').forEach((line) => {
-    // Use regex to capture the command after "$ wxt " and before "--help"
-    const match = line.match(/\$ wxt (\w+) --help/);
-    if (match && match[1]) {
-      commands.push(match[1]);
-    }
-  });
-
-  return commands;
-}
diff --git a/docs/api/cli/wxt-build.md b/docs/api/cli/wxt-build.md
new file mode 100644
index 00000000..9f64a7ae
--- /dev/null
+++ b/docs/api/cli/wxt-build.md
@@ -0,0 +1,7 @@
+# `wxt build`
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.build }}</code></pre></div>
diff --git a/docs/api/cli/wxt-clean.md b/docs/api/cli/wxt-clean.md
new file mode 100644
index 00000000..d5c993d8
--- /dev/null
+++ b/docs/api/cli/wxt-clean.md
@@ -0,0 +1,7 @@
+# `wxt clean`
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.clean }}</code></pre></div>
diff --git a/docs/api/cli/wxt-init.md b/docs/api/cli/wxt-init.md
new file mode 100644
index 00000000..1db90c94
--- /dev/null
+++ b/docs/api/cli/wxt-init.md
@@ -0,0 +1,7 @@
+# `wxt init`
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.init }}</code></pre></div>
diff --git a/docs/api/cli/wxt-prepare.md b/docs/api/cli/wxt-prepare.md
new file mode 100644
index 00000000..f8c36462
--- /dev/null
+++ b/docs/api/cli/wxt-prepare.md
@@ -0,0 +1,7 @@
+# `wxt prepare`
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.prepare }}</code></pre></div>
diff --git a/docs/api/cli/wxt-submit-init.md b/docs/api/cli/wxt-submit-init.md
new file mode 100644
index 00000000..ae837232
--- /dev/null
+++ b/docs/api/cli/wxt-submit-init.md
@@ -0,0 +1,9 @@
+# `wxt submit init`
+
+> Alias for [`publish-browser-extension`](https://www.npmjs.com/package/publish-browser-extension)
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.submitInit }}</code></pre></div>
diff --git a/docs/api/cli/wxt-submit.md b/docs/api/cli/wxt-submit.md
new file mode 100644
index 00000000..2c194929
--- /dev/null
+++ b/docs/api/cli/wxt-submit.md
@@ -0,0 +1,9 @@
+# `wxt submit`
+
+> Alias for [`publish-browser-extension`](https://www.npmjs.com/package/publish-browser-extension)
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.submit }}</code></pre></div>
diff --git a/docs/api/cli/wxt-zip.md b/docs/api/cli/wxt-zip.md
new file mode 100644
index 00000000..814ef049
--- /dev/null
+++ b/docs/api/cli/wxt-zip.md
@@ -0,0 +1,7 @@
+# `wxt zip`
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.zip }}</code></pre></div>
diff --git a/docs/api/cli/wxt.md b/docs/api/cli/wxt.md
new file mode 100644
index 00000000..ab8499f9
--- /dev/null
+++ b/docs/api/cli/wxt.md
@@ -0,0 +1,7 @@
+# `wxt`
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.wxt }}</code></pre></div>
diff --git a/docs/get-started/assets.md b/docs/get-started/assets.md
new file mode 100644
index 00000000..f8ef639a
--- /dev/null
+++ b/docs/get-started/assets.md
@@ -0,0 +1,33 @@
+# Assets
+
+WXT has two directories for storing assets like CSS, images, or fonts.
+
+- [public directory](/guide/directory-structure/public/): Store files that will be copied into the output directory as-is
+- [assets directory](/guide/directory-structure/assets): Store files that will be processed by Vite during the build process
+
+To learn more about how to use assets at runtime from either of these directories, visit their guides linked above.
+
+## Public Directory
+
+Place static files like the extension icon or `_locales/` directory here. These files will be copied over to the output directory without being transformed by Vite.
+
+```
+<srcDir>
+└─ public/
+   ├─ icon-16.png
+   ├─ icon-32.png
+   ├─ icon-48.png
+   ├─ icon-96.png
+   └─ icon-128.png
+```
+
+## Assets Directory
+
+Files in the assets directory will be processed by Vite. They are imported in your source code, and will be transformed or renamed in the output directory.
+
+```
+<srcDir>
+└─ assets/
+   ├─ tailwind.css
+   └─ illustration.svg
+```
diff --git a/docs/guide/compare.md b/docs/get-started/compare.md
similarity index 77%
rename from docs/guide/compare.md
rename to docs/get-started/compare.md
index b64dfa4e..46b6be69 100644
--- a/docs/guide/compare.md
+++ b/docs/get-started/compare.md
@@ -1,6 +1,6 @@
 # Compare
 
-Lets compare the features of WXT vs [Plasmo](https://docs.plasmo.com/framework) (another web extension framework) and [CRXJS](https://crxjs.dev/vite-plugin) (the most popular bundler plugin).
+Lets compare the features of WXT vs [Plasmo](https://docs.plasmo.com/framework) (another framework) and [CRXJS](https://crxjs.dev/vite-plugin) (a bundler plugin).
 
 ## Overview
 
@@ -31,20 +31,3 @@ Lets compare the features of WXT vs [Plasmo](https://docs.plasmo.com/framework)
 | Storage                                              |             ✅              |                    ✅                    |                                   ❌                                    |
 | Messaging                                            |             ❌              |                    ✅                    |                                   ❌                                    |
 | Content Script UI                                    |             ✅              |                    ✅                    |                                   ❌                                    |
-
-## Why use WXT?
-
-WXT's main goal is improving the development experience (DX) of creating web extensions, while not sacrificing support. There are two things WXT does differently:
-
-1. Automatically opens a browser with the extension installed when starting development
-2. Reload each part of the extension individually rather than reloading the entire extension
-
-Opening a browser automatically makes it super easy to start and stop development without having to manually load the extension in your browser.
-
-Reloading each part of the extension individually improves your iteration speed while developing UIs. This is because reloading the entire extension on every change will close the popup and any tabs open to an extension page, like options. If you save a file associated with a UI and a content script while working on the UI, it will randomly close because it needed to reload the extension when the content script changed. This interrupts your development flow and is really annoying.
-
-WXT solves this problem by reloading HTML pages and content scripts individually (when possible) to keep your UIs open while you develop them. This is a MV3 feature, so if you're developing a MV2 extension, you'll get the same dev experience as Plasmo.
-
-:::info
-Unfortunately, there isn't an API for reloading the background page/service worker individually, so if you change a file used by the background, the entire extension will reload. See [Issue #53](https://github.com/wxt-dev/wxt/issues/53) for more details.
-:::
diff --git a/docs/get-started/configuration.md b/docs/get-started/configuration.md
new file mode 100644
index 00000000..04cb62ef
--- /dev/null
+++ b/docs/get-started/configuration.md
@@ -0,0 +1,57 @@
+# Configuration
+
+By default, WXT provides sensible configuration for bundling web extensions with Vite.
+
+## Config File
+
+To configure WXT, create a `wxt.config.ts` file in your project root. It should have the following contents:
+
+```ts
+import { defineConfig } from 'wxt';
+
+export default defineConfig({
+  // My WXT config
+});
+```
+
+:::info
+For more information on configuring WXT via the `wxt.config.ts` file, read the dedicated [`wxt.config.ts` guide](/guide/directory-structure/wxt-config).
+:::
+
+## Manifest.json
+
+WXT generates your extension's `manifest.json` based on the project structure. To add additional properties, like permissions, use the [`manifest` property](/api/reference/wxt/interfaces/InlineConfig#manifest).
+
+```ts
+import { defineConfig } from 'wxt';
+
+export default defineConfig({
+  manifest: {
+    permissions: ['storage'],
+  },
+});
+```
+
+:::info
+For more information on configuring the manifest, read the dedicated [Manifest guide](/guide/key-concepts/manifest).
+:::
+
+## Environment
+
+WXT can read `.env` files, and variables are accessible via `import.meta.env.*`.
+
+:::code-group
+
+```sh [.env]
+VITE_OAUTH_CLIENT_ID=abc123
+```
+
+```ts [JS]
+import.meta.env.VITE_OAUTH_CLIENT_ID;
+```
+
+:::
+
+:::info
+For more information on using .env files, read the dedicated [`.env` guide](/guide/directory-structure/env).
+:::
diff --git a/docs/get-started/entrypoints.md b/docs/get-started/entrypoints.md
new file mode 100644
index 00000000..36d8a1af
--- /dev/null
+++ b/docs/get-started/entrypoints.md
@@ -0,0 +1,60 @@
+# Entrypoints
+
+An "entrypoint" is any HTML, JS, or CSS file that needs to be bundled and included with your extension, which will be loaded and executed by the browser.
+
+## Defining Entrypoints
+
+In WXT, you create an entrypoint by adding a file to the `entrypoints/` directory.
+
+```
+<rootDir>
+└─ entrypoints/
+   ├─ background.ts
+   ├─ content.ts
+   ├─ injected.ts
+   └─ popup.html
+```
+
+Some entrypoint filesname patterns are reserved by WXT and effect how the manifest is generated.
+
+- `popup` adds a `action` to the manifest
+- `background` adds a background script/service worker
+- `*.content.ts` adds a content script
+- ...
+
+> For a full list of recognized filenames, see the the [Entrypoints Directory guide](/guide/directory-structure/entrypoints/background).
+
+Any other files, whether JS, CSS, or HTML, is considered "unlisted". Unlisted files, like `injected.ts` from above, are just bundled to the output directory and not added to the manifest. You can still access or load them at runtime.
+
+## Entrypoint Options
+
+Most entrypoints allow customizing their options in the file you define them in. This differs from regular web extension development, where all options are placed in the `manifest.json`.
+
+WXT looks for custom options in the entrypoint, and adds them to the manifest when generated.
+
+In HTML files, options are listed as `meta` tags:
+
+```html
+<html>
+  <head>
+    <!-- Defining the popup's "default_icon" field -->
+    <meta name="manifest.default_icon" content="{ '16': '/icon/16.png' }" />
+  </head>
+</html>
+```
+
+In TS files, options are apart of the file's default export:
+
+```ts
+export default defineContentScript({
+  matches: ['*://*.google.com/*'],
+  runAt: 'document_start',
+  main() {
+    // ...
+  },
+});
+```
+
+:::info
+All options for each entrypoint type is listed in the [entrypoints directory docs](/guide/directory-structure/entrypoints/background).
+:::
diff --git a/docs/guide/installation.md b/docs/get-started/installation.md
similarity index 56%
rename from docs/guide/installation.md
rename to docs/get-started/installation.md
index 81adf755..d6d3d00c 100644
--- a/docs/guide/installation.md
+++ b/docs/get-started/installation.md
@@ -1,6 +1,6 @@
 # Installation
 
-Bootstrap a new project, start from scratch, or [migrate an existing project](/guide/migrate-to-wxt).
+Bootstrap a new project, start from scratch, or [migrate an existing project](/get-started/migrate-to-wxt).
 
 ## Bootstrap Project
 
@@ -36,54 +36,27 @@ All templates default to TypeScript. Rename the file extensions to `.js` to use
 
 ## From Scratch
 
-Create a new NPM project:
+Initialize a project and install `wxt`:
 
 :::code-group
 
 ```sh [pnpm]
-mkdir project-name
-cd project-name
 pnpm init
-echo 'shamefully-hoist=true' >> .npmrc
-```
-
-```sh [npm]
-mkdir project-name
-cd project-name
-npm init
-```
-
-```sh [yarn]
-mkdir project-name
-cd project-name
-yarn init
-```
-
-```sh [bun]
-mkdir project-name
-cd project-name
-bun init
-```
-
-:::
-
-Then install `wxt`:
-
-:::code-group
-
-```sh [pnpm]
 pnpm add -D wxt
 ```
 
 ```sh [npm]
+npm init
 npm i --save-dev wxt
 ```
 
 ```sh [yarn]
+yarn init
 yarn add --dev wxt
 ```
 
 ```sh [bun]
+bun init
 bun add --dev wxt
 ```
 
@@ -98,7 +71,7 @@ export default defineBackground(() => {
 });
 ```
 
-Finally, add scripts to your `package.json`:
+And add scripts to your `package.json`:
 
 ```json
 {
@@ -114,25 +87,9 @@ Finally, add scripts to your `package.json`:
 }
 ```
 
-## Migrate an Existing Project
-
-Before starting the migration, it is recommended to run `pnpm dlx wxt@latest init` to see what a basic project looks like. Once you have an understanding of how WXT projects are structured, you're ready to convert the project, using the initialized project as a reference.
-
-Migrating a project to WXT comes down to a few steps:
-
-1. Install WXT and remove any old build tools: `pnpm i -D wxt`
-1. Refactoring/move your entrypoints to the `entrypoints` directory
-1. Moving public assets to the `public` directory
-1. Update the dev and build scripts to use WXT
-1. Ensure project is compatible with Vite, which is used under the hood to bundle your extension
-
-:::info
-Since projects vary greatly in setup, [start a discussion on GitHub](https://github.com/wxt-dev/wxt/discussions/new/choose) if you need help migrating your project to WXT.
-:::
-
 ## Development
 
-Once you've installed WXT, you can start the development server using the `dev` script.
+Once the project is setup, you can start the development server using the `dev` script.
 
 ```sh
 pnpm dev
@@ -143,22 +100,11 @@ pnpm dev
 The dev command will build the extension for development, open the browser, and reload the different parts of the extension when you save changes.
 :::
 
-:::details Development Manifest
-When running the dev command, WXT will make several changes to your `manifest.json` to improve your development experience:
-
-- If missing, add a background script/service worker to enable fast reloads
-- Add several `permissions` and `host_permissions` to enable HMR and fast reloads
-- Modify the CSP to allow connections with the dev server
-- Remove `content_scripts` and register them at runtime so they can be easily reloaded when you save a file
-
-If you're an experienced web extension developer and think the dev manifest looks wrong, this is why. Run a production build with `wxt build` to see the unmodified `manifest.json`.
-:::
-
 ## Next Steps
 
 You're ready to build your web extension!
 
-- Learn how to [add entrypoints](./entrypoints) like the popup, options page, or content scripts
-- Configure your entrypoints to [use ESM](./esm) at runtime
+- Read the rest of the "Get Started" pages for a high-overview of what WXT can do
+- Read the [Guide](/guide/key-concepts/manifest) to learn in-depth about each feature WXT supports
 - [Configure WXT](./configuration) by creating a `wxt.config.ts` file
 - Checkout [example projects](https://github.com/wxt-dev/wxt-examples) to see how to perform common tasks with WXT
diff --git a/docs/guide/introduction.md b/docs/get-started/introduction.md
similarity index 80%
rename from docs/guide/introduction.md
rename to docs/get-started/introduction.md
index 39ab318f..886b3090 100644
--- a/docs/guide/introduction.md
+++ b/docs/get-started/introduction.md
@@ -7,6 +7,8 @@ head:
 
 # Introduction
 
+## Overview
+
 WXT is a free and open source framework for building web extensions in an conventional, intuitive, and safe way **_for all browsers_**.
 
 WXT is based of [Nuxt](https://nuxt.com), and aims to provide the same great DX with TypeScript, auto-imports, and an opinionated project structure.
@@ -37,3 +39,9 @@ In addition, WXT fully supports Firefox's source code requirements when using a
 :::info
 See [Publishing](./publishing) for more info around production builds.
 :::
+
+## New to Extension Development?
+
+Most of these docs assume you have a basic understanding of how to write a chrome or web extension.
+
+If you've never written a web extension before or need a refresher, follow Google's ["Hello, World!" tutorial](https://developer.chrome.com/docs/extensions/get-started/tutorial/hello-world) to understand the basics.
diff --git a/docs/guide/migrate-to-wxt.md b/docs/get-started/migrate-to-wxt.md
similarity index 61%
rename from docs/guide/migrate-to-wxt.md
rename to docs/get-started/migrate-to-wxt.md
index 817a4e48..ef2ef4c4 100644
--- a/docs/guide/migrate-to-wxt.md
+++ b/docs/get-started/migrate-to-wxt.md
@@ -4,7 +4,7 @@ outline: deep
 
 # Migrate to WXT
 
-> If you have problems migrating to WXT, feel free to ask for help in GitHub by [starting a discussion](https://github.com/wxt-dev/wxt/discussions/new?category=q-a)!
+> If you have problems migrating to WXT, feel free to ask for help in GitHub by [starting a discussion](https://github.com/wxt-dev/wxt/discussions/new?category=q-a) or in [Discord](https://discord.gg/ZFsZqGery9)!
 
 ## Overview
 
@@ -17,16 +17,16 @@ pnpm dlx wxt@latest init example-wxt --template vanilla
 
 In general, you'll need to:
 
-<input type="checkbox" /> Install `wxt`<br />
-<input type="checkbox" /> Update/create `package.json` scripts to use `wxt` (don't forget about `postinstall`)<br />
-<input type="checkbox" /> Move entrypoints into `entrypoints/` directory<br />
-<input type="checkbox" /> Move assets into either the `assets/` or `public/` directories<br />
-<input type="checkbox" /> Move manifest.json content into `wxt.config.ts`<br />
-<input type="checkbox" /> Convert custom import syntax to be compatible with Vite<br />
-<input type="checkbox" /> Add a default export to JS entrypoints<br />
-<input type="checkbox" /> Use the `browser` global instead of `chrome`<br />
-<input type="checkbox" /> Compare final `manifest.json` files, making sure permissions and host permissions are unchanged<br />
-<input type="checkbox" /> Extension output by `wxt build` works the same way as before the migration<br />
+&ensp;<input type="checkbox" /> Install `wxt`<br />
+&ensp;<input type="checkbox" /> Update/create `package.json` scripts to use `wxt` (don't forget about `postinstall`)<br />
+&ensp;<input type="checkbox" /> Move entrypoints into `entrypoints/` directory<br />
+&ensp;<input type="checkbox" /> Move assets into either the `assets/` or `public/` directories<br />
+&ensp;<input type="checkbox" /> Move manifest.json content into `wxt.config.ts`<br />
+&ensp;<input type="checkbox" /> Convert custom import syntax to be compatible with Vite<br />
+&ensp;<input type="checkbox" /> Add a default export to JS entrypoints<br />
+&ensp;<input type="checkbox" /> Use the `browser` global instead of `chrome`<br />
+&ensp;<input type="checkbox" /> Compare final `manifest.json` files, making sure permissions and host permissions are unchanged<br />
+&ensp;<input type="checkbox" /> Extension output by `wxt build` works the same way as before the migration<br />
 
 Every project is different, so there's no one-solution-fits-all to migrating your project. Just make sure `wxt dev` runs, `wxt build` results in a working extension, and the list of permissions in the `manifest.json` hasn't changed. If all that looks good, you've finished migrating your extension!
 
@@ -55,3 +55,11 @@ Since you're already using Vite, it's a simple refactor.
 5. Convert Plasmo's custom import resolutions to Vite's
 6. If importing remote code via a URL, add a `url:` prefix so it works with WXT
 7. Compare your output `manifest.json` files from before the migration to after the migration. They should have the same content. If not, tweak your entrypoints and config to get as close as possible.
+
+<!--
+## Migrate an Existing Project
+
+:::info
+Since projects vary greatly in setup, [start a discussion on GitHub](https://github.com/wxt-dev/wxt/discussions/new/choose) if you need help migrating your project to WXT.
+:::
+-->
diff --git a/docs/guide/publishing.md b/docs/get-started/publishing.md
similarity index 97%
rename from docs/guide/publishing.md
rename to docs/get-started/publishing.md
index 15f255bd..5aec4385 100644
--- a/docs/guide/publishing.md
+++ b/docs/get-started/publishing.md
@@ -20,8 +20,8 @@ For specific details about each store, see the stores sections below.
 
 WXT provides two commands to help automate the release process:
 
+- `wxt submit init`: Setup all the required secrets and options for the `wxt submit` command
 - `wxt submit`: Submit new versions of your extension for review (and publish them automatically once approved)
-- `wxt submit init`: Help setup all the required secrets and options for the `wxt submit` command
 
 To get started, run `wxt submit init` and follow the prompts. Once finished, you should have a `.env.submit` file! WXT will use this file to submit your updates.
 
@@ -181,7 +181,7 @@ bun zip:firefox
 Make sure the build output is the exact same when running `wxt build -b firefox` in your main project and inside the zipped sources.
 
 :::warning
-If you use a `.env` files, they can effect the chunk hashes in the output directory. Either delete the .env file before running `wxt zip -b firefox`, or include it in your sources zip with the [`zip.includeSources`](/api/wxt/interfaces/InlineConfig#includesources) option. Be careful to not include any secrets in your `.env` files.
+If you use a `.env` files, they can effect the chunk hashes in the output directory. Either delete the .env file before running `wxt zip -b firefox`, or include it in your sources zip with the [`zip.includeSources`](/api/reference/wxt/interfaces/InlineConfig#includesources) option. Be careful to not include any secrets in your `.env` files.
 
 See Issue [#377](https://github.com/wxt-dev/wxt/issues/377) for more details.
 :::
diff --git a/docs/get-started/testing.md b/docs/get-started/testing.md
new file mode 100644
index 00000000..27d88fd6
--- /dev/null
+++ b/docs/get-started/testing.md
@@ -0,0 +1,25 @@
+# Testing
+
+## Official Frameworks
+
+WXT officially supports [Vitest](https://vitest.dev/) for unit tests and either [Playwright](https://playwright.dev/) or [Puppeteer](https://pptr.dev/) for E2E tests against Chromium browsers.
+
+For details setting up each testing framework, see the official examples:
+
+<ExampleList tag="testing" />
+
+## Unofficial Frameworks
+
+Puppeteer and Playwright are the only E2E test runners that support Chrome Extensions. There are no other options at the time of writing.
+
+There are other options for unit tests however, like [Jest](https://jestjs.io/), [Mocha](https://mochajs.org/), or [`node:test`](https://nodejs.org/api/test.html). **_WXT does not claim to support any of them_** because none of them support all of WXT's features, like TypeScript or auto-imports.
+
+If you want to try to use a different framework for unit tests, you will need to configure the environment manually:
+
+- **Auto-imports**: Add `unimport` to your test environment or disable them by setting `imports: false` in your `wxt.config.ts` file
+- **`browser` mock**: Mock the `webextension-polyfill` module globally with `wxt/dist/virtual/mock-browser.js`
+- **[Remote Code Bundling](/guide/go-further/remote-code)**: If you use it, configure your environment to handle the `url:` module prefix
+- **Global Variables**: If you consume them, manually define globals provided by WXT (like `import.meta.env.BROWSER`) by adding them to the global scope before accessing them (`import.meta.env.BROWSER = "chrome"`)
+- **Import paths**: If you use the `@/` or `~/` path aliases, add them to your test environment
+
+[Here's how Vitest is configured](https://github.com/wxt-dev/wxt/blob/main/packages/wxt/src/testing/wxt-vitest-plugin.ts) for reference.
diff --git a/docs/guide/assets.md b/docs/guide/assets.md
deleted file mode 100644
index a762d4d1..00000000
--- a/docs/guide/assets.md
+++ /dev/null
@@ -1,85 +0,0 @@
-# Assets
-
-WXT has two directories for storing assets like CSS, images, or fonts.
-
-- `<srcDir>/public`: Store files that will be copied into the output directory as-is
-- `<srcDir>/assets`: Store files that will be processed by Vite during the build process
-
-## `/public` Directory
-
-Place static files like the extension icon or `_locales/` directory here. These files will be copied over to the output directory without being transformed by Vite.
-
-```
-<srcDir>
-└─ public/
-   ├─ icon-16.png
-   ├─ icon-32.png
-   ├─ icon-48.png
-   ├─ icon-96.png
-   └─ icon-128.png
-```
-
-### Example
-
-You can reference these files by using absolute paths in HTML files or `browser.runtime.getURL` in content scripts.
-
-:::code-group
-
-```html [popup.html]
-<img src="/icon-128.png" />
-```
-
-```ts [content.ts]
-defineContentScript({
-  main() {
-    const image = document.createElement('img');
-    image.src = browser.runtime.getURL('/icon-128.png');
-    document.body.append(image);
-  },
-});
-```
-
-:::
-
-## `/assets` Directory
-
-Files in the assets directory will be processed by Vite. They are imported in your source code, and will be transformed or renamed in the output directory.
-
-```
-<srcDir>
-└─ assets/
-   ├─ style.css
-   └─ illustration.svg
-```
-
-### Example
-
-:::code-group
-
-```html [popup.html]
-<html>
-  <head>
-    <link rel="stylesheet" href="~/assets/style.css" />
-    <!-- ... -->
-  </head>
-  <body>
-    <img src="~/assets/illustration.svg" />
-    <!-- ... -->
-  </body>
-</html>
-```
-
-```ts [content.ts]
-import '~/assets/style.css';
-import illustration from '~/assets/style.svg';
-
-defineContentScript({
-  main() {
-    const image = document.createElement('img');
-    image.src = illustration;
-    document.body.append(image);
-  },
-});
-```
-
-:::
diff --git a/docs/guide/configuration.md b/docs/guide/configuration.md
deleted file mode 100644
index 297131c9..00000000
--- a/docs/guide/configuration.md
+++ /dev/null
@@ -1,99 +0,0 @@
-# Configuration
-
-WXT's behavior can be configured via the `wxt.config.ts` file. In this file, you can add Vite plugins, change the directory structure of your project, and set fields on your `manifest.json`.
-
-## Config File
-
-To configure WXT, create a `wxt.config.ts` file in your project root. It should have the following contents:
-
-```ts
-import { defineConfig } from 'wxt';
-
-export default defineConfig({
-  // My WXT config
-});
-```
-
-:::info
-See the [Config reference](/api/wxt/interfaces/InlineConfig) for a full list of options.
-:::
-
-## Directory Config
-
-WXT allows you to edit several directories to your liking:
-
-- `root` (default: `process.cwd()`) - Root of the WXT project
-- `srcDir` (default: `<rootDir>`) - Location of all your source code
-- `entrypointsDir` (default: `<srcDir>/entrypoints`) - Folder containing all the entrypoints.
-- `publicDir` (default: `<srcDir>/public`) - Folder containing [public assets](/guide/assets)
-
-### Example
-
-You want a `src/` directory to contain all your source code, and you want to rename `entrypoints/` &rarr; `entries/`:
-
-```
-<rootDir>
-├─ src/
-│  └─ entries/
-│     ├─ background.ts
-│     └─ ...
-└─ wxt.config.ts
-```
-
-Your config would look like this:
-
-```ts
-import { defineConfig } from 'wxt';
-
-export default defineConfig({
-  srcDir: 'src',
-  entrypointsDir: 'entries',
-});
-```
-
-## Frontend Frameworks
-
-Adding a framework like Vue, React, or Svelte is easy!
-
-In the `wxt.config.ts` file, install and add the framework's Vite plugin to the config.
-
-:::code-group
-
-```ts [Vue]
-import { defineConfig } from 'wxt';
-import vue from '@vitejs/plugin-vue';
-
-export default defineConfig({
-  vite: () => ({
-    plugins: [vue()],
-  }),
-});
-```
-
-```ts [React]
-import { defineConfig } from 'wxt';
-import react from '@vitejs/plugin-react';
-
-export default defineConfig({
-  vite: () => ({
-    plugins: [react()],
-  }),
-});
-```
-
-```ts [Svelte]
-import { defineConfig } from 'wxt';
-import { svelte } from '@sveltejs/vite-plugin-svelte';
-
-export default defineConfig({
-  vite: () => ({
-    plugins: [svelte()],
-  }),
-});
-```
-
-:::
-
-:::info
-Internally, WXT runs `vite build` multiple times during a single build. It can't share the same instance of some plugins between each build, so a function is used to return completely new instances of each plugin for each build.
-:::
diff --git a/docs/guide/directory-structure/assets.md b/docs/guide/directory-structure/assets.md
new file mode 100644
index 00000000..f28bac1a
--- /dev/null
+++ b/docs/guide/directory-structure/assets.md
@@ -0,0 +1,42 @@
+# `<srcDir>/assets`
+
+Files in the assets directory will be processed by Vite. They are imported in your source code, and will be transformed or renamed in the output directory.
+
+```
+<srcDir>
+└─ assets/
+   ├─ style.css
+   └─ illustration.svg
+```
+
+### Example
+
+:::code-group
+
+```html [popup.html]
+<html>
+  <head>
+    <link rel="stylesheet" href="~/assets/style.css" />
+    <!-- ... -->
+  </head>
+  <body>
+    <img src="~/assets/illustration.svg" />
+    <!-- ... -->
+  </body>
+</html>
+```
+
+```ts [content.ts]
+import '~/assets/style.css';
+import illustration from '~/assets/style.svg';
+
+defineContentScript({
+  main() {
+    const image = document.createElement('img');
+    image.src = illustration;
+    document.body.append(image);
+  },
+});
+```
+
+:::
diff --git a/docs/guide/directory-structure/components.md b/docs/guide/directory-structure/components.md
new file mode 100644
index 00000000..0bb2f0b2
--- /dev/null
+++ b/docs/guide/directory-structure/components.md
@@ -0,0 +1,5 @@
+# `<srcDir>/components`
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/directory-structure/composables.md b/docs/guide/directory-structure/composables.md
new file mode 100644
index 00000000..c1ada3ec
--- /dev/null
+++ b/docs/guide/directory-structure/composables.md
@@ -0,0 +1,5 @@
+# `<srcDir>/composables`
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/entrypoints/background.md b/docs/guide/directory-structure/entrypoints/background.md
similarity index 100%
rename from docs/entrypoints/background.md
rename to docs/guide/directory-structure/entrypoints/background.md
diff --git a/docs/entrypoints/bookmarks.md b/docs/guide/directory-structure/entrypoints/bookmarks.md
similarity index 100%
rename from docs/entrypoints/bookmarks.md
rename to docs/guide/directory-structure/entrypoints/bookmarks.md
diff --git a/docs/entrypoints/content-scripts.md b/docs/guide/directory-structure/entrypoints/content-scripts.md
similarity index 95%
rename from docs/entrypoints/content-scripts.md
rename to docs/guide/directory-structure/entrypoints/content-scripts.md
index 2896ddcc..41982076 100644
--- a/docs/entrypoints/content-scripts.md
+++ b/docs/guide/directory-structure/entrypoints/content-scripts.md
@@ -104,4 +104,4 @@ export default defineContentScript({
 });
 ```
 
-See [Content Script UI](/guide/content-script-ui) for more info on creating UIs and including CSS in content scripts.
+See [Content Script UI](/guide/key-concepts/content-script-ui) for more info on creating UIs and including CSS in content scripts.
diff --git a/docs/entrypoints/css.md b/docs/guide/directory-structure/entrypoints/css.md
similarity index 79%
rename from docs/entrypoints/css.md
rename to docs/guide/directory-structure/entrypoints/css.md
index e48f7047..0e38c46c 100644
--- a/docs/entrypoints/css.md
+++ b/docs/guide/directory-structure/entrypoints/css.md
@@ -2,10 +2,10 @@
 
 WXT can build CSS entrypoints individually. CSS entrypoints are always unlisted.
 
-See [Content Script CSS](/entrypoints/content-scripts#css) documentation for the recommended approach to include CSS with a content script.
+See [Content Script CSS](/guide/directory-structure/entrypoints/content-scripts#css) documentation for the recommended approach to include CSS with a content script.
 
 :::info
-If the recommended approach doesn't work for your use case, you can use any of the filename patterns below to build the styles separate from the JS and use the [`transformManifest` hook](/api/wxt/interfaces/InlineConfig#transformmanifest) to manually add your CSS file to the manifest.
+If the recommended approach doesn't work for your use case, you can use any of the filename patterns below to build the styles separate from the JS and use the [`transformManifest` hook](/api/reference/wxt/interfaces/InlineConfig#transformmanifest) to manually add your CSS file to the manifest.
 :::
 
 ## Filenames
diff --git a/docs/entrypoints/devtools.md b/docs/guide/directory-structure/entrypoints/devtools.md
similarity index 100%
rename from docs/entrypoints/devtools.md
rename to docs/guide/directory-structure/entrypoints/devtools.md
diff --git a/docs/entrypoints/history.md b/docs/guide/directory-structure/entrypoints/history.md
similarity index 100%
rename from docs/entrypoints/history.md
rename to docs/guide/directory-structure/entrypoints/history.md
diff --git a/docs/entrypoints/newtab.md b/docs/guide/directory-structure/entrypoints/newtab.md
similarity index 100%
rename from docs/entrypoints/newtab.md
rename to docs/guide/directory-structure/entrypoints/newtab.md
diff --git a/docs/entrypoints/options.md b/docs/guide/directory-structure/entrypoints/options.md
similarity index 100%
rename from docs/entrypoints/options.md
rename to docs/guide/directory-structure/entrypoints/options.md
diff --git a/docs/entrypoints/popup.md b/docs/guide/directory-structure/entrypoints/popup.md
similarity index 100%
rename from docs/entrypoints/popup.md
rename to docs/guide/directory-structure/entrypoints/popup.md
diff --git a/docs/entrypoints/sandbox.md b/docs/guide/directory-structure/entrypoints/sandbox.md
similarity index 100%
rename from docs/entrypoints/sandbox.md
rename to docs/guide/directory-structure/entrypoints/sandbox.md
diff --git a/docs/entrypoints/sidepanel.md b/docs/guide/directory-structure/entrypoints/sidepanel.md
similarity index 100%
rename from docs/entrypoints/sidepanel.md
rename to docs/guide/directory-structure/entrypoints/sidepanel.md
diff --git a/docs/entrypoints/unlisted-pages.md b/docs/guide/directory-structure/entrypoints/unlisted-pages.md
similarity index 100%
rename from docs/entrypoints/unlisted-pages.md
rename to docs/guide/directory-structure/entrypoints/unlisted-pages.md
diff --git a/docs/entrypoints/unlisted-scripts.md b/docs/guide/directory-structure/entrypoints/unlisted-scripts.md
similarity index 100%
rename from docs/entrypoints/unlisted-scripts.md
rename to docs/guide/directory-structure/entrypoints/unlisted-scripts.md
diff --git a/docs/guide/directory-structure/env.md b/docs/guide/directory-structure/env.md
new file mode 100644
index 00000000..6a17fbce
--- /dev/null
+++ b/docs/guide/directory-structure/env.md
@@ -0,0 +1,5 @@
+# `<root>/.env`
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/directory-structure/hooks.md b/docs/guide/directory-structure/hooks.md
new file mode 100644
index 00000000..e6e19836
--- /dev/null
+++ b/docs/guide/directory-structure/hooks.md
@@ -0,0 +1,5 @@
+# `<srcDir>/hooks`
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/directory-structure/output.md b/docs/guide/directory-structure/output.md
new file mode 100644
index 00000000..bb5ef417
--- /dev/null
+++ b/docs/guide/directory-structure/output.md
@@ -0,0 +1,5 @@
+# `<root>/.output`
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/directory-structure/package.md b/docs/guide/directory-structure/package.md
new file mode 100644
index 00000000..79f23b57
--- /dev/null
+++ b/docs/guide/directory-structure/package.md
@@ -0,0 +1,5 @@
+# `<root>/package.json`
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/directory-structure/public/index.md b/docs/guide/directory-structure/public/index.md
new file mode 100644
index 00000000..765e1a44
--- /dev/null
+++ b/docs/guide/directory-structure/public/index.md
@@ -0,0 +1,35 @@
+# `public/`
+
+Place static files like the extension icon or `_locales/` directory here. These files will be copied over to the output directory without being transformed by Vite.
+
+```
+<srcDir>
+└─ public/
+   ├─ icon-16.png
+   ├─ icon-32.png
+   ├─ icon-48.png
+   ├─ icon-96.png
+   └─ icon-128.png
+```
+
+### Example
+
+You can reference these files by using absolute paths in HTML files or `browser.runtime.getURL` in content scripts.
+
+:::code-group
+
+```html [popup.html]
+<img src="/icon-128.png" />
+```
+
+```ts [content.ts]
+defineContentScript({
+  main() {
+    const image = document.createElement('img');
+    image.src = browser.runtime.getURL('/icon-128.png');
+    document.body.append(image);
+  },
+});
+```
+
+:::
diff --git a/docs/guide/directory-structure/public/locales.md b/docs/guide/directory-structure/public/locales.md
new file mode 100644
index 00000000..36a57303
--- /dev/null
+++ b/docs/guide/directory-structure/public/locales.md
@@ -0,0 +1,5 @@
+# `public/_locales/`
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/directory-structure/tsconfig.md b/docs/guide/directory-structure/tsconfig.md
new file mode 100644
index 00000000..81220e42
--- /dev/null
+++ b/docs/guide/directory-structure/tsconfig.md
@@ -0,0 +1,5 @@
+# `<root>/tsconfig.json`
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/directory-structure/utils.md b/docs/guide/directory-structure/utils.md
new file mode 100644
index 00000000..54cd86e5
--- /dev/null
+++ b/docs/guide/directory-structure/utils.md
@@ -0,0 +1,5 @@
+# `<srcDir>/utils`
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/directory-structure/web-ext-config.md b/docs/guide/directory-structure/web-ext-config.md
new file mode 100644
index 00000000..9065a303
--- /dev/null
+++ b/docs/guide/directory-structure/web-ext-config.md
@@ -0,0 +1,5 @@
+# `web-ext.config.ts`
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/directory-structure/wxt-config.md b/docs/guide/directory-structure/wxt-config.md
new file mode 100644
index 00000000..30c0e831
--- /dev/null
+++ b/docs/guide/directory-structure/wxt-config.md
@@ -0,0 +1,5 @@
+# `<root>/wxt.config.ts`
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/directory-structure/wxt.md b/docs/guide/directory-structure/wxt.md
new file mode 100644
index 00000000..557ce148
--- /dev/null
+++ b/docs/guide/directory-structure/wxt.md
@@ -0,0 +1,5 @@
+# `.wxt/`
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/entrypoints.md b/docs/guide/entrypoints.md
deleted file mode 100644
index 4f153a8c..00000000
--- a/docs/guide/entrypoints.md
+++ /dev/null
@@ -1,141 +0,0 @@
-# Defining Entrypoints
-
-An "entrypoint" is any HTML, JS, or CSS file that needs to be bundled and included with the extension.
-
-Entrypoints may or may not be listed in the extension's `manifest.json`.
-
-## `/entrypoints` Directory
-
-In WXT, entrypoints are defined by adding a file to the `entrypoints/` directory.
-
-For example, a project that looks like this:
-
-```
-<rootDir>
-└─ entrypoints/
-   ├─ background.ts
-   ├─ content.ts
-   ├─ injected.ts
-   └─ popup.html
-```
-
-would result in the following `manifest.json`:
-
-```json
-{
-  // ...
-  "manifest_version": 3,
-  "action": {
-    // ...
-    "default_popup": "popup.html"
-  },
-  "background": {
-    // ...
-    "service_worker": "background.js"
-  },
-  "content_scripts": [
-    {
-      // ...
-      "js": ["content-scripts/content.js"]
-    }
-  ]
-}
-```
-
-If a file uses a special name recognized by WXT, it will be added to the manifest. In this case:
-
-- `popup.html` &rarr; `action.default_popup`
-- `content.ts` &rarr; `content_scripts.0.js.0`
-- `background.ts` &rarr; `background.service_worker`
-
-But not all entrypoints are added to the `manifest.json`. If the filename is not recognized by WXT, they are still built and included in the extension, but they are considered "unlisted" and are not apart of the manifest.
-
-In this case, `injected.ts` gets output to `<outdir>/injected.js` and is accessible via `browser.runtime.getURL("/injected.js")`.
-
-:::info
-See [`/entrypoints` folder](/entrypoints/background) documentation for a full list of recognized entrypoint filenames.
-:::
-
-## Entrypoint Options
-
-Some entrypoints, like content scripts, actions, or the background, can receive additional options.
-
-In HTML files, options are listed as `meta` tags:
-
-```html
-<html>
-  <head>
-    <!-- Defining the popup's "default_icon" field -->
-    <meta name="manifest.default_icon" content="{ '16': '/icon/16.png' }" />
-  </head>
-</html>
-```
-
-In TS files, options are apart of the file's default export:
-
-```ts
-export default defineContentScript({
-  matches: ['*://*.google.com/*'],
-  runAt: 'document_start',
-  main() {
-    // ...
-  },
-});
-```
-
-:::info
-For a full list of entrypoints and each of their options, see the [`/entrypoints` folder](/entrypoints/background) documentation.
-:::
-
-### Side Effects
-
-You cannot use imported variables outside the `main` function in JS entrypoints. This includes options, as shown below:
-
-```ts
-// entrypoints/content.ts
-import { GOOGLE_MATCHES } from '~/utils/match-patterns';
-
-export default defineContentScript({
-  matches: GOOGLE_MATCHES,
-  main() {
-    // ...
-  },
-});
-```
-
-```
-$ wxt build
-wxt build
-
-WXT 0.14.1
-ℹ Building chrome-mv3 for production with Vite 5.0.5
-✖ Command failed after 360 ms
-
-[8:55:54 AM]  ERROR  entrypoints/content.ts: Cannot use imported variable "GOOGLE_MATCHES" before main function. See https://wxt.dev/guide/entrypoints.html#side-effects
-```
-
-This throws an error because WXT needs to import each entrypoint during the build process to extract its definition (containing the `match`, `runAt`, `include`/`exclude`, etc.) to render the `manifest.json` correctly. Before loading an entrypoint, a transformation is applied to remove all imports. This prevents imported modules (local or NPM) with side-effects from running during the build process, potentially throwing an error.
-
-:::details Why?
-
-When importing your entrypoint to get its definition, the file is imported in a **_node environment_**, and doesn't have access to the `window`, `chrome`, or `browser` globals a web extension usually has access to. If WXT doesn't remove all the imports from the file, the imported modules could try and access one of these variables, throwing an error.
-
-:::
-
-:::warning
-See [`wxt-dev/wxt#336`](https://github.com/wxt-dev/wxt/issues/336) to track the status of this bug.
-:::
-
-Usually, this error occurs when you try to extract options into a shared file or try to run code outside the `main` function. To fix the example from above, use literal values when defining an entrypoint instead of importing them:
-
-```ts
-import { GOOGLE_MATCHES } from '~/utils/match-patterns'; // [!code --]
-
-export default defineContentScript({
-  matches: GOOGLE_MATCHES, // [!code --]
-  matches: ['*//*.google.com/*'], // [!code ++]
-  main() {
-    // ...
-  },
-});
-```
diff --git a/docs/guide/extension-apis.md b/docs/guide/extension-apis.md
deleted file mode 100644
index 95779b99..00000000
--- a/docs/guide/extension-apis.md
+++ /dev/null
@@ -1,94 +0,0 @@
-# Extension APIs
-
-WXT is built on top of [`webextension-polyfill`](https://www.npmjs.com/package/webextension-polyfill), which uses the standard `browser` global.
-
-If you're used to Chrome's `chrome` global, its a simple switch:
-
-1. Replace `chrome` with `browser`
-2. [Replace callbacks with async/await](https://developer.chrome.com/docs/extensions/mv3/promises/)
-
-And that's it! Your extension now supports Chrome, Firefox, Safari, Edge, and other Chromium browsers.
-
-## Basic Usage
-
-The `browser` variable is available globally via [auto-imports](/guide/auto-imports), or it can be imported manually.
-
-```ts
-import { browser } from 'wxt/browser';
-```
-
-The `wxt/browser` module exports a customized version of `webextension-polyfill`'s browser with improved typing.
-
-### Example
-
-Let's save the date the extension was installed. Just like `chrome`, some APIs require the permission is added to your manifest before the API is defined. Here, we need to add the `storage` permission to your manifest.
-
-```ts
-// wxt.config.ts
-import { defineConfig } from 'wxt';
-
-export default defineConfig({
-  manifest: {
-    permissions: ['storage'],
-  },
-});
-```
-
-Then we can use `browser.storage` to save the install date to local storage.
-
-```ts
-// background.ts
-export default defineBackground(() => {
-  browser.runtime.onInstalled.addListener(({ reason }) => {
-    if (reason === 'install') {
-      browser.storage.local.set({ installDate: Date.now() });
-    }
-  });
-});
-```
-
-## Messaging
-
-Follow [Chrome's message passing guide](https://developer.chrome.com/docs/extensions/mv3/messaging/) to understand how message passing works in web extensions. In Google's examples, just replace `chrome` with `browser`, and it will work in WXT.
-
-Here's a basic request/response example:
-
-```ts
-// popup/main.ts
-const res = await browser.runtime.sendMessage('ping');
-
-console.log(res); // "pong"
-```
-
-```ts
-// background.ts
-export default defineBackground(() => {
-  browser.runtime.onMessage.addListener((message, sender, sendResponse) => {
-    console.log(message); // "ping"
-
-    // Wait 1 second and respond with "pong"
-    setTimeout(() => sendResponse('pong'), 1000);
-    return true;
-  });
-});
-```
-
-There are a number of message passing libraries you can use to improve the message passing experience.
-
-Here are some that are compatible with WXT (because they are based off `webextension-polyfill` as well):
-
-- [`@webext-core/messaging`](https://webext-core.aklinker1.io/guide/messaging/) - "A light-weight, type-safe wrapper around the `browser.runtime` messaging APIs"
-- [`@webext-core/proxy-service`](https://webext-core.aklinker1.io/guide/proxy-service/) - "Create TRPC-like services that can be called from anywhere but run in the background"
-- [`webext-bridge`](https://github.com/zikaari/webext-bridge) - "Messaging in Web Extensions made super easy. Out of the box."
-
-## Browser Differences
-
-Some APIs are only available on certain browsers or manifest versions. You will have to check if an API exists at runtime if it is not in the `browser` standard.
-
-```ts
-if ('session' in browser.storage) {
-  // Do something with the non-standard session storage API
-}
-```
-
-> If you're using TypeScript, knowing what is non-standard is easy! APIs that are not typed are non-standard.
diff --git a/docs/guide/extension-apis/messaging.md b/docs/guide/extension-apis/messaging.md
new file mode 100644
index 00000000..a55f1355
--- /dev/null
+++ b/docs/guide/extension-apis/messaging.md
@@ -0,0 +1,36 @@
+# Messaging
+
+## Overview
+
+Follow [Chrome's message passing guide](https://developer.chrome.com/docs/extensions/mv3/messaging/) to understand how message passing works in web extensions. In Google's examples, just replace `chrome` with `browser`, and it will work in WXT.
+
+Here's a basic request/response example:
+
+```ts
+// popup/main.ts
+const res = await browser.runtime.sendMessage('ping');
+
+console.log(res); // "pong"
+```
+
+```ts
+// background.ts
+export default defineBackground(() => {
+  browser.runtime.onMessage.addListener((message, sender, sendResponse) => {
+    console.log(message); // "ping"
+
+    // Wait 1 second and respond with "pong"
+    setTimeout(() => sendResponse('pong'), 1000);
+    return true;
+  });
+});
+```
+
+## Third Party Libraries
+
+There are a number of message passing libraries you can use to improve the message passing experience.
+
+- [`@webext-core/messaging`](https://webext-core.aklinker1.io/guide/messaging/) - "A light-weight, type-safe wrapper around the `browser.runtime` messaging APIs"
+- [`@webext-core/proxy-service`](https://webext-core.aklinker1.io/guide/proxy-service/) - "Create RPC-like services that can be called from anywhere but run in the background"
+- [`webext-bridge`](https://github.com/zikaari/webext-bridge) - "Messaging in Web Extensions made super easy. Out of the box."
+- [`trpc-chrome`](https://www.npmjs.com/package/trpc-chrome) - "tRPC adapter for Web Extensions 🧩"
diff --git a/docs/guide/extension-apis/others.md b/docs/guide/extension-apis/others.md
new file mode 100644
index 00000000..db707c98
--- /dev/null
+++ b/docs/guide/extension-apis/others.md
@@ -0,0 +1,5 @@
+# All Other APIs
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/extension-apis/scripting.md b/docs/guide/extension-apis/scripting.md
new file mode 100644
index 00000000..9565a739
--- /dev/null
+++ b/docs/guide/extension-apis/scripting.md
@@ -0,0 +1,26 @@
+# `browser.scripting`
+
+[Chrome Docs](https://developer.chrome.com/docs/extensions/reference/api/scripting) &bull; [Firefox Docs](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/scripting)
+
+Refer to the browser docs above for basics on how the API works.
+
+## Execute Script Return Values
+
+When using `browser.scripting.executeScript`, you can execute content scripts or unlisted scripts. To return a value, just return a value from the script's main function.
+
+```ts
+// entrypoints/background.ts
+const res = await browser.scripting.executeScript({
+  target: { tabId },
+  files: ['injected.js'],
+});
+console.log(res); // "Hello John!"
+```
+
+```ts
+// entrypoints/injected.js
+export default defineContentScript(() => {
+  console.log('Script was injected!');
+  return 'Hello John!';
+});
+```
diff --git a/docs/guide/storage.md b/docs/guide/extension-apis/storage.md
similarity index 97%
rename from docs/guide/storage.md
rename to docs/guide/extension-apis/storage.md
index 43998209..c6f07b38 100644
--- a/docs/guide/storage.md
+++ b/docs/guide/extension-apis/storage.md
@@ -22,7 +22,7 @@ export default defineConfig({
 });
 ```
 
-More info on permissions [here](/guide/manifest#permissions).
+More info on permissions [here](/guide/key-concepts/manifest#permissions).
 :::
 
 [[toc]]
@@ -54,7 +54,7 @@ await storage.watch<number>(
 await storage.getMeta<{ v: number }>('local:installDate');
 ```
 
-For a full list of methods available, see the [API reference](/api/wxt/storage/interfaces/WxtStorage).
+For a full list of methods available, see the [API reference](/api/reference/wxt/storage/interfaces/WxtStorage).
 
 ## Watchers
 
@@ -137,7 +137,7 @@ const unwatch = showChangelogOnUpdate.watch((newValue) => {
 });
 ```
 
-For a full list of properties and methods available, see the [API reference](/api/wxt/storage/interfaces/WxtStorageItem).
+For a full list of properties and methods available, see the [API reference](/api/reference/wxt/storage/interfaces/WxtStorageItem).
 
 ### Versioning
 
diff --git a/docs/guide/go-further/custom-events.md b/docs/guide/go-further/custom-events.md
new file mode 100644
index 00000000..9963a574
--- /dev/null
+++ b/docs/guide/go-further/custom-events.md
@@ -0,0 +1,5 @@
+# Custom Events
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/go-further/debugging.md b/docs/guide/go-further/debugging.md
new file mode 100644
index 00000000..26920e60
--- /dev/null
+++ b/docs/guide/go-further/debugging.md
@@ -0,0 +1,5 @@
+# Debugging
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/go-further/entrypoint-side-effects.md b/docs/guide/go-further/entrypoint-side-effects.md
new file mode 100644
index 00000000..6c730f98
--- /dev/null
+++ b/docs/guide/go-further/entrypoint-side-effects.md
@@ -0,0 +1,52 @@
+# Entrypoint Side Effects
+
+You cannot use imported variables outside the `main` function in JS entrypoints. This includes options, as shown below:
+
+```ts
+// entrypoints/content.ts
+import { GOOGLE_MATCHES } from '~/utils/match-patterns';
+
+export default defineContentScript({
+  matches: GOOGLE_MATCHES,
+  main() {
+    // ...
+  },
+});
+```
+
+```
+$ wxt build
+wxt build
+
+WXT 0.14.1
+ℹ Building chrome-mv3 for production with Vite 5.0.5
+✖ Command failed after 360 ms
+
+[8:55:54 AM]  ERROR  entrypoints/content.ts: Cannot use imported variable "GOOGLE_MATCHES" before main function. See https://wxt.dev/guide/entrypoints.html#side-effects
+```
+
+This throws an error because WXT needs to import each entrypoint during the build process to extract its definition (containing the `match`, `runAt`, `include`/`exclude`, etc.) to render the `manifest.json` correctly. Before loading an entrypoint, a transformation is applied to remove all imports. This prevents imported modules (local or NPM) with side-effects from running during the build process, potentially throwing an error.
+
+:::details Why?
+
+When importing your entrypoint to get its definition, the file is imported in a **_node environment_**, and doesn't have access to the `window`, `chrome`, or `browser` globals a web extension usually has access to. If WXT doesn't remove all the imports from the file, the imported modules could try and access one of these variables, throwing an error.
+
+:::
+
+:::warning
+See [`wxt-dev/wxt#336`](https://github.com/wxt-dev/wxt/issues/336) to track the status of this bug.
+:::
+
+Usually, this error occurs when you try to extract options into a shared file or try to run code outside the `main` function. To fix the example from above, use literal values when defining an entrypoint instead of importing them:
+
+```ts
+import { GOOGLE_MATCHES } from '~/utils/match-patterns'; // [!code --]
+
+export default defineContentScript({
+  matches: GOOGLE_MATCHES, // [!code --]
+  matches: ['*//*.google.com/*'], // [!code ++]
+  main() {
+    // ...
+  },
+});
+```
diff --git a/docs/guide/esm.md b/docs/guide/go-further/es-modules.md
similarity index 100%
rename from docs/guide/esm.md
rename to docs/guide/go-further/es-modules.md
diff --git a/docs/guide/handling-updates.md b/docs/guide/go-further/handling-updates.md
similarity index 94%
rename from docs/guide/handling-updates.md
rename to docs/guide/go-further/handling-updates.md
index 9d89516b..533d5359 100644
--- a/docs/guide/handling-updates.md
+++ b/docs/guide/go-further/handling-updates.md
@@ -41,7 +41,7 @@ The `ctx` also provides other convenient APIs for stopping your content script w
    });
    ```
 
-Other WXT APIs require a `ctx` object so they can clean themselves up. For example, [`createIntegratedUi`](/guide/content-script-ui#integrated), [`createShadowRootUi`](/guide/content-script-ui#shadow-root), and [`createIframeUi`](/guide/content-script-ui#iframe) automatically unmount and stop a UI when the script is invalidated.
+Other WXT APIs require a `ctx` object so they can clean themselves up. For example, [`createIntegratedUi`](/guide/key-concepts/content-script-ui#integrated), [`createShadowRootUi`](/guide/key-concepts/content-script-ui#shadow-root), and [`createIframeUi`](/guide/key-concepts/content-script-ui#iframe) automatically unmount and stop a UI when the script is invalidated.
 
 :::warning
 When working with content scripts, **you should always use the `ctx` object to stop any async or future work.**
diff --git a/docs/guide/go-further/how-wxt-works.md b/docs/guide/go-further/how-wxt-works.md
new file mode 100644
index 00000000..84a33f7d
--- /dev/null
+++ b/docs/guide/go-further/how-wxt-works.md
@@ -0,0 +1,5 @@
+# How WXT Works
+
+:::warning 🚧 Under construction
+These docs will be coming soon!
+:::
diff --git a/docs/guide/remote-code.md b/docs/guide/go-further/remote-code.md
similarity index 100%
rename from docs/guide/remote-code.md
rename to docs/guide/go-further/remote-code.md
diff --git a/docs/guide/testing.md b/docs/guide/go-further/testing.md
similarity index 92%
rename from docs/guide/testing.md
rename to docs/guide/go-further/testing.md
index 2494b3bc..37e1848c 100644
--- a/docs/guide/testing.md
+++ b/docs/guide/go-further/testing.md
@@ -18,7 +18,7 @@ If you want to try to use a different framework for unit tests, you will need to
 
 - **Auto-imports**: Add `unimport` to your test environment or disable them by setting `imports: false` in your `wxt.config.ts` file
 - **`browser` mock**: Mock the `webextension-polyfill` module globally with `wxt/dist/virtual/mock-browser.js`
-- **[Remote Code Bundling](/guide/remote-code)**: If you use it, configure your environment to handle the `url:` module prefix
+- **[Remote Code Bundling](/guide/go-further/remote-code)**: If you use it, configure your environment to handle the `url:` module prefix
 - **Global Variables**: If you consume them, manually define globals provided by WXT (like `import.meta.env.BROWSER`) by adding them to the global scope before accessing them (`import.meta.env.BROWSER = "chrome"`)
 - **Import paths**: If you use the `@/` or `~/` path aliases, add them to your test environment
 
diff --git a/docs/guide/vite.md b/docs/guide/go-further/vite.md
similarity index 100%
rename from docs/guide/vite.md
rename to docs/guide/go-further/vite.md
diff --git a/docs/guide/auto-imports.md b/docs/guide/key-concepts/auto-imports.md
similarity index 60%
rename from docs/guide/auto-imports.md
rename to docs/guide/key-concepts/auto-imports.md
index e0d06589..a75613c2 100644
--- a/docs/guide/auto-imports.md
+++ b/docs/guide/key-concepts/auto-imports.md
@@ -2,22 +2,18 @@
 
 WXT uses the same tool as Nuxt for auto-imports, [`unimport`](https://github.com/unjs/unimport).
 
-:::info Testing
-To setup your test environment for auto-imports, see [Testing](/guide/testing).
-:::
-
 ## WXT Auto-imports
 
 Some WXT APIs can be used without importing them:
 
-- [`browser`](/api/wxt/browser/variables/browser) from `wxt/browser`, a small wrapper around `webextension-polyfill`
-- [`defineContentScript`](/api/wxt/sandbox/functions/defineContentScript) from `wxt/sandbox`
-- [`defineBackground`](/api/wxt/sandbox/functions/defineBackground) from `wxt/sandbox`
-- [`defineUnlistedScript`](/api/wxt/sandbox/functions/defineUnlistedScript) from `wxt/sandbox`
-- [`createIntegratedUi`](/api/wxt/client/functions/createIntegratedUi) from `wxt/client`
-- [`createShadowRootUi`](/api/wxt/client/functions/createShadowRootUi) from `wxt/client`
-- [`createIframeUi`](/api/wxt/client/functions/createIframeUi) from `wxt/client`
-- [`fakeBrowser`](/api/wxt/testing/variables/fakeBrowser) from `wxt/testing`
+- [`browser`](/api/reference/wxt/browser/variables/browser) from `wxt/browser`, a small wrapper around `webextension-polyfill`
+- [`defineContentScript`](/api/reference/wxt/sandbox/functions/defineContentScript) from `wxt/sandbox`
+- [`defineBackground`](/api/reference/wxt/sandbox/functions/defineBackground) from `wxt/sandbox`
+- [`defineUnlistedScript`](/api/reference/wxt/sandbox/functions/defineUnlistedScript) from `wxt/sandbox`
+- [`createIntegratedUi`](/api/reference/wxt/client/functions/createIntegratedUi) from `wxt/client`
+- [`createShadowRootUi`](/api/reference/wxt/client/functions/createShadowRootUi) from `wxt/client`
+- [`createIframeUi`](/api/reference/wxt/client/functions/createIframeUi) from `wxt/client`
+- [`fakeBrowser`](/api/reference/wxt/testing/variables/fakeBrowser) from `wxt/testing`
 
 And more!
 
@@ -43,7 +39,7 @@ Alternatively, you could add the directory to the list of auto-import directorie
 
 For TypeScript to work, you need to run the `wxt prepare` command. This will ensure types are generated for auto-imports.
 
-This should be added to your `postinstall` script:
+This should be added to your `postinstall` script so your editor has everything it needs to report type errors after installing dependencies:
 
 ```json
 // package.json
@@ -71,6 +67,8 @@ export default defineConfig({
 });
 ```
 
+## Disabling Auto-imports
+
 To disable auto-imports, set `imports: false`
 
 ```ts
diff --git a/docs/guide/content-script-ui.md b/docs/guide/key-concepts/content-script-ui.md
similarity index 89%
rename from docs/guide/content-script-ui.md
rename to docs/guide/key-concepts/content-script-ui.md
index 0c503e4e..c75935ee 100644
--- a/docs/guide/content-script-ui.md
+++ b/docs/guide/key-concepts/content-script-ui.md
@@ -155,20 +155,20 @@ export default defineContentScript({
 
 :::
 
-See the [API Reference](/api/wxt/client/functions/createIntegratedUi) for the complete list of options.
+See the [API Reference](/api/reference/wxt/client/functions/createIntegratedUi) for the complete list of options.
 
-You can control how CSS is injected for an integrated content script UI with the [`cssInjectionMode`](/api/wxt/interfaces/BaseContentScriptEntrypointOptions#cssinjectionmode) property. Usually, you'll want to leave it as `"manifest"`, the default, so the UI inherits its style from the website's CSS.
+You can control how CSS is injected for an integrated content script UI with the [`cssInjectionMode`](/api/reference/wxt/interfaces/BaseContentScriptEntrypointOptions#cssinjectionmode) property. Usually, you'll want to leave it as `"manifest"`, the default, so the UI inherits its style from the website's CSS.
 
 ## Shadow Root
 
 Often in web extensions, you don't want your content script's CSS affecting the page, or vise-versa. The [`ShadowRoot`](https://developer.mozilla.org/en-US/docs/Web/API/ShadowRoot) API is ideal for this.
 
-WXT's [`createShadowRootUi`](/api/wxt/client/functions/createShadowRootUi) abstracts all the `ShadowRoot` setup away, making it easy to create UIs with isolated CSS. It also supports an optional `isolateEvents` parameter to further isolate user interactions.
+WXT's [`createShadowRootUi`](/api/reference/wxt/client/functions/createShadowRootUi) abstracts all the `ShadowRoot` setup away, making it easy to create UIs with isolated CSS. It also supports an optional `isolateEvents` parameter to further isolate user interactions.
 
 To use `createShadowRootUi`, follow these steps:
 
 1. Import your CSS file at the top of your content script
-2. Set [`cssInjectionMode: "ui"`](/api/wxt/interfaces/BaseContentScriptEntrypointOptions#cssinjectionmode) inside `defineContentScript`
+2. Set [`cssInjectionMode: "ui"`](/api/reference/wxt/interfaces/BaseContentScriptEntrypointOptions#cssinjectionmode) inside `defineContentScript`
 3. Define your UI with `createShadowRootUi()`
 4. Mount the UI so it is visible to users
 
@@ -341,7 +341,7 @@ export default defineContentScript({
 
 :::
 
-See the [API Reference](/api/wxt/client/functions/createShadowRootUi) for the complete list of options.
+See the [API Reference](/api/reference/wxt/client/functions/createShadowRootUi) for the complete list of options.
 
 :::info TailwindCSS
 `createShadowRootUi` supports TailwindCSS out of the box! When importing the styles, just import the main CSS file containing the `@tailwind` directives, and everything will just work :+1:.
@@ -351,7 +351,7 @@ See the [API Reference](/api/wxt/client/functions/createShadowRootUi) for the co
 
 If you don't need to run your UI in the same frame as the content script, you can use an IFrame to host your UI instead. Since an IFrame just hosts an HTML page, **_HMR is supported_**.
 
-WXT provides a helper function, [`createIframeUi`](/api/wxt/client/functions/createIframeUi), which simplifies setting up the IFrame.
+WXT provides a helper function, [`createIframeUi`](/api/reference/wxt/client/functions/createIframeUi), which simplifies setting up the IFrame.
 
 1. Create an HTML page that will be loaded into your IFrame
    ```html
@@ -405,4 +405,4 @@ WXT provides a helper function, [`createIframeUi`](/api/wxt/client/functions/cre
    });
    ```
 
-See the [API Reference](/api/wxt/client/functions/createIframeUi) for the complete list of options.
+See the [API Reference](/api/reference/wxt/client/functions/createIframeUi) for the complete list of options.
diff --git a/docs/guide/key-concepts/frontend-frameworks.md b/docs/guide/key-concepts/frontend-frameworks.md
new file mode 100644
index 00000000..d0d34516
--- /dev/null
+++ b/docs/guide/key-concepts/frontend-frameworks.md
@@ -0,0 +1,92 @@
+# Frontend Frameworks
+
+WXT supports all frontend frameworks with a Vite plugin:
+
+- `@vitejs/plugin-vue`
+- `@vitejs/plugin-react`
+- `@vitejs/plugin-react-swc`
+- And more!
+
+Just add the vite plugin to your config and you're good to go! Use the framework in HTML pages or content scripts, it will just work 👍
+
+:::code-group
+
+```ts [Vue]
+import { defineConfig } from 'wxt';
+import vue from '@vitejs/plugin-vue';
+
+export default defineConfig({
+  vite: () => ({
+    plugins: [vue()],
+  }),
+});
+```
+
+```ts [React]
+import { defineConfig } from 'wxt';
+import react from '@vitejs/plugin-react';
+
+export default defineConfig({
+  vite: () => ({
+    plugins: [react()],
+  }),
+});
+```
+
+```ts [Svelte]
+import { defineConfig } from 'wxt';
+import { svelte } from '@sveltejs/vite-plugin-svelte';
+
+export default defineConfig({
+  vite: () => ({
+    plugins: [svelte()],
+  }),
+});
+```
+
+:::
+
+## Multiple Apps
+
+Since web extensions usually contain multiple UIs as separate HTML files (popup, options, changelog, side panel, etc), you'll need to create individual app instances, one per HTML page.
+
+Usually, this means each entrypoint should be a directory with it's own files inside it:
+
+```
+<root>/
+  ├ assets/  <------------------ Put shared assets here
+  │   ├ style.css  <------------ Like styles all your pages share
+  │   └ ...
+  ├ components/  <-------------- Put shared components here
+  │   └ ...
+  └ entrypoints/
+      ├ popup/  <--------------- Use a folder with an index.html file in it
+      │   ├ index.html
+      │   ├ main.tsx  <--------- Create and mount your app here
+      │   ├ style.css  <-------- Have some global styles to apply?
+      │   └ ... <--------------- Rest of the files can be named whatever
+      └ options/
+          ├ pages/  <------------ A good place to put your router pages
+          │   ├ [id]/
+          │   │   └ details.tsx
+          │   ├ index.tsx
+          │   └...
+          ├ index.html
+          ├ App.vue
+          ├ main.ts
+          ├ style.css
+          └ rotuer.ts
+```
+
+## Configuring Routers
+
+Lots of frameworks come with routers for building a multi-page app using the URL's path. Chrome extensions don't don't work like this. Since HTML files are static, `chrome-extension://{id}/popup.html`, there's no way to change the entire path for routing.
+
+Instead, you need to configure the router to run in "hash" mode, where the routing information is apart of the URL's hash, not the path (ie: `popup.html#/` and `popup.html#/account/settings`)
+
+Refer to your router's docs for information about "hash" mode and how to enable it. Here's a non-extensive list of a few popular routers:
+
+- [React](https://reactrouter.com/en/main/routers/create-hash-router)
+- [Vue](https://router.vuejs.org/guide/essentials/history-mode.html#Hash-Mode)
+- [Svelte](https://www.npmjs.com/package/svelte-spa-router#hash-based-routing)
+- [Solid](https://github.com/solidjs/solid-router?tab=readme-ov-file#hash-mode-router)
diff --git a/docs/guide/manifest.md b/docs/guide/key-concepts/manifest.md
similarity index 51%
rename from docs/guide/manifest.md
rename to docs/guide/key-concepts/manifest.md
index 79569682..6060e9aa 100644
--- a/docs/guide/manifest.md
+++ b/docs/guide/key-concepts/manifest.md
@@ -1,145 +1,25 @@
----
-outline: deep
----
+# Manifest
 
-# Manifest.json
+## Overview
 
-The manifest.json is generated at build-time based on files in the `entrypoints/` directory and `wxt.config.ts`.
-
-## Configuration
-
-While entrypoints are generated and added to the manifest at build-time, you can customize or add to your `manifest.json` in the config file.
+Sometimes, you'll need to make manual changes to how the `manifest.json` is generated. You can do this by using the `manifest` configuration:
 
 ```ts
-// wxt.config.ts entrypoint of your extension
-import { defineConfig } from 'wxt';
-
+// wxt.config.ts
 export default defineConfig({
   manifest: {
-    host_permissions: ['*://google.com/*'],
-    content_security_policy: {
-      // ...
-    },
+    // Put manual changes here
   },
 });
 ```
 
-### `name`
+## Manifest Version Compatibility
 
-If not provided via the `manifest` config, the [manifest's `name`](https://developer.chrome.com/docs/extensions/mv3/manifest/name/) defaults to your package.json's `name` property.
+When defining options in the manifest, always define them for MV3 when possible. WXT will either convert them to their MV2 equivalents or remove them from the generated manifest if there is not MV2 equivalent.
 
-### `version` and `version_name`
+So for fields like `web_accessible_resources` or `content_security_policy`, you just need to list them in their MV3 forms. Other fields, like `side_panel`, which doesn't exist in MV2, will be removed automatically.
 
-The [manifest's `version` and `version_name`](https://developer.chrome.com/docs/extensions/mv3/manifest/version/) properties are based on the `version` field listed in your `package.json` or `wxt.config.ts`.
-
-- `version_name` is the exact string listed in your `package.json` or `wxt.config.ts` file
-- `version` is the string cleaned up, with any invalid suffixes removed
-
-If a version is not found, a warning is logged and the version defaults to `"0.0.0"`.
-
-#### Example
-
-```json
-// package.json
-{
-  "version": "1.3.0-alpha2"
-}
-```
-
-```json
-// .output/<dir>/manifest.json
-{
-  "version": "1.3.0",
-  "version_name": "1.3.0-alpha2"
-}
-```
-
-### `icons`
-
-By default, WXT will discover icons in your [`public` directory](/guide/assets#public-directory) and use them for the [manifest's `icons`](https://developer.chrome.com/docs/extensions/mv3/manifest/icons/).
-
-```
-public/
-├─ icon-16.png
-├─ icon-24.png
-├─ icon-48.png
-├─ icon-96.png
-└─ icon-128.png
-```
-
-Icon files need to match the following regex to be automatically included in the manifest. Most design software can output icons in one of these formats
-
-<<< @/../packages/wxt/src/core/utils/manifest.ts#snippet
-
-If you prefer to use filenames in a different format, you can add the icons manually in your `wxt.config.ts` file:
-
-```ts
-export default defineConfig({
-  manifest: {
-    icons: {
-      16: '/extension-icon-16.png',
-      24: '/extension-icon-24.png',
-      48: '/extension-icon-48.png',
-      96: '/extension-icon-96.png',
-      128: '/extension-icon-128.png',
-    },
-  },
-});
-```
-
-### `permissions`
-
-[Permissions](https://developer.chrome.com/docs/extensions/reference/permissions/) must be listed in the manifest config.
-
-```ts
-export default defineConfig({
-  manifest: {
-    permissions: ['storage', 'tabs'],
-  },
-});
-```
-
-## Localization
-
-Similar to the icon, the [`_locales` directory](https://developer.chrome.com/docs/extensions/reference/i18n/) should be placed inside the the WXT's [`public` directory](/guide/assets#public-directory).
-
-```
-public/
-└─ _locales/
-   ├─ en/
-   │  └─ messages.json
-   ├─ es/
-   │  └─ messages.json
-   └─ ko/
-      └─ messages.json
-```
-
-Then you'll need to explicitly override the `name` and `description` properties in your config for them to be localized.
-
-```ts
-export default defineConfig({
-  manifest: {
-    name: '__MSG_extName__',
-    description: '__MSG_extDescription__',
-    default_locale: 'en',
-  },
-});
-```
-
-See the official localization examples for more details:
-
-<ExampleList tag="i18n" />
-
-## Per-Manifest Version Config
-
-WXT applies several transformations to your manifest to simplify managing both MV2 and MV3 keys in your `wxt.config.ts` file:
-
-1. Top level MV2-only or MV3-only keys are stripped from the final manifest when targeting the other manifest version
-2. Some keys, are automatically converted between versions when possible:
-   - Define `web_accessible_resources` in it's MV3 style and it will be converted to the MV2 style automatically
-   - `action` will automatically be converted to `browser_action` for MV3. To use `page_action` instead, add both `action` and `page_action` entries to your manifest
-
-For example, a `wxt.config.ts` file that looks like this:
+Here's an example `wxt.config.ts` file:
 
 ```ts
 import { defineConfig } from 'wxt';
@@ -159,7 +39,7 @@ export default defineConfig({
 });
 ```
 
-Will be output differently for each manifest version:
+And here's the different `manifest.json` files generated:
 
 :::code-group
 
@@ -192,46 +72,180 @@ Will be output differently for each manifest version:
 
 :::
 
-:::tip
-If this isn't enough control for your use-case, remember you can use a function for the `manifest` key and generate it however you'd like, or you can use the `build:manifestGenerated` hook to apply additional transformations.
-:::
+## Name
 
-## Per-Browser Configuration
+If not provided via the `manifest` config, the [manifest's `name`](https://developer.chrome.com/docs/extensions/mv3/manifest/name/) defaults to your `package.json`'s `name` property.
 
-The `manifest` field can be a function. If you are building and extension for multiple browsers, and need to modify the manifest per browser, using a function instead of an object is very useful.
+## Version
+
+The [manifest's `version` and `version_name`](https://developer.chrome.com/docs/extensions/mv3/manifest/version/) properties are based on the `version` field listed in your `package.json` or `wxt.config.ts`.
+
+- `version_name` is the exact string listed in your `package.json` or `wxt.config.ts` file
+- `version` is the string cleaned up, with any invalid suffixes removed
+
+If a version is not found, a warning is logged and the version defaults to `"0.0.0"`.
+
+#### Example
+
+```json
+// package.json
+{
+  "version": "1.3.0-alpha2"
+}
+```
+
+```json
+// .output/<dir>/manifest.json
+{
+  "version": "1.3.0",
+  "version_name": "1.3.0-alpha2"
+}
+```
+
+### `icons`
+
+By default, WXT will discover icons in your [`public` directory](/guide/directory-structure/public/) and use them for the [manifest's `icons`](https://developer.chrome.com/docs/extensions/mv3/manifest/icons/).
+
+```
+public/
+├─ icon-16.png
+├─ icon-24.png
+├─ icon-48.png
+├─ icon-96.png
+└─ icon-128.png
+```
+
+Icon files need to match the following regex to be automatically included in the manifest. Most design software can output icons in one of these formats
+
+<<< @/../packages/wxt/src/core/utils/manifest.ts#snippet
+
+If you prefer to use filenames in a different format, you can add the icons manually in your `wxt.config.ts` file:
 
 ```ts
 export default defineConfig({
-  manifest: ({ browser, manifestVersion, mode, command }) => {
-    return {
-      // Your manifest
-    };
+  manifest: {
+    icons: {
+      16: '/extension-icon-16.png',
+      24: '/extension-icon-24.png',
+      48: '/extension-icon-48.png',
+      96: '/extension-icon-96.png',
+      128: '/extension-icon-128.png',
+    },
   },
 });
 ```
 
-:::info
-The first argument is of type `ConfigEnv`. See the [API reference](/api/wxt/interfaces/ConfigEnv) for info about each property.
-:::
+### Permissions
 
-For example, say you use OAuth, and you need to provide a different `oauth.client_id` for each browser:
+[Permissions](https://developer.chrome.com/docs/extensions/reference/permissions/) must be listed in the manifest config.
 
 ```ts
-const clientIds = {
-  chrome: '<your-chrome-client-id>',
-  edge: '<your-edge-client-id>',
-  firefox: '<your-firefox-client-id>',
-  opera: '<your-opera-client-id>',
-};
-
 export default defineConfig({
-  manifest: ({ browser }) => ({
-    oauth: {
-      client_id: clientIds[browser],
-      scopes: [
-        // ...
-      ],
+  manifest: {
+    permissions: ['storage', 'tabs'],
+  },
+});
+```
+
+## Localization
+
+Similar to the icon, the [`_locales` directory](https://developer.chrome.com/docs/extensions/reference/i18n/) should be placed inside the the WXT's [`public` directory](/guide/directory-structure/public/).
+
+```
+public/
+└─ _locales/
+   ├─ en/
+   │  └─ messages.json
+   ├─ es/
+   │  └─ messages.json
+   └─ ko/
+      └─ messages.json
+```
+
+Then you'll need to explicitly override the `name` and `description` properties in your config for them to be localized.
+
+```ts
+export default defineConfig({
+  manifest: {
+    name: '__MSG_extName__',
+    description: '__MSG_extDescription__',
+    default_locale: 'en',
+  },
+});
+```
+
+See the official localization examples for more details:
+
+<ExampleList tag="i18n" />
+
+## Actions
+
+In MV2, you had two options: [`browser_action`](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/browser_action) and [`page_action`](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/page_action). In MV3, they were merged into a single [`action`](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/action) API.
+
+By default, whenever an action is generated, WXT falls back to `browser_action` when targetting MV2.
+
+### Action With Popup
+
+To generate a manifest where a UI appears after clicking the icon, just create a [popup entrypoint](/guide/directory-structure/entrypoints/popup).
+
+If you want to use a `page_action` for MV2, add the following `meta` tag to the HTML document's head:
+
+```html
+<meta name="manifest.type" content="page_action" />
+```
+
+### Action Without Popup
+
+If you want to use the `activeTab` permission or the `browser.action.onClick` event, but don't want to show a popup UI:
+
+1. Delete the [popup entrypoint](/guide/directory-structure/entrypoints/popup) if it exists
+2. Add the `action` key to your manifest:
+   ```ts
+   // wxt.config.ts
+   export default defineConfig({
+     manifest: {
+       action: {},
+     },
+   });
+   ```
+
+Same as an action with a popup, WXT will fallback on using `browser_action` for MV2. To use a `page_action` instead, add that key as well:
+
+```ts
+// wxt.config.ts
+export default defineConfig({
+  manifest: {
+    action: {},
+    page_action: {},
+  },
+});
+```
+
+## Full Control
+
+The `manifest` option can also be set equal to a function, letting you use logical statements to determine what should be output.
+
+```ts
+// wxt.config.ts
+export default defineConfig({
+  manifest: ({ manifestVersion, browser, mode, comamnd }) => {
+    return { ... }
+  }
+})
+```
+
+Or, you can use the `build:manifestGenerated` hook to transform the manifest before it is written to the output directory.
+
+```ts
+// wxt.config.ts
+export default defineConfig({
+  hooks: {
+    build: {
+      manifestGenerated(manifest) {
+        // Update the manifest variable by reference
+        manifest.name = 'Overriden name';
+      },
     },
-  }),
+  },
 });
 ```
diff --git a/docs/guide/multiple-browsers.md b/docs/guide/key-concepts/multiple-browsers.md
similarity index 97%
rename from docs/guide/multiple-browsers.md
rename to docs/guide/key-concepts/multiple-browsers.md
index a8edacea..ee5a743d 100644
--- a/docs/guide/multiple-browsers.md
+++ b/docs/guide/key-concepts/multiple-browsers.md
@@ -33,7 +33,7 @@ By default, it will build for `chrome`. When excluding the [manifest version fla
 | Any other string |            3             |
 
 :::tip
-To configure which browser is opened when running dev mode via `wxt -b <browser>`, see the [Development docs](/guide/development#configure-browser-startup) docs.
+To configure which browser is opened when running dev mode via `wxt -b <browser>`, see the [`web-ext.config.ts` docs](/guide/directory-structure/web-ext-config).
 :::
 
 ## Target Manifest Version
diff --git a/docs/guide/key-concepts/web-extension-polyfill.md b/docs/guide/key-concepts/web-extension-polyfill.md
new file mode 100644
index 00000000..81b585b2
--- /dev/null
+++ b/docs/guide/key-concepts/web-extension-polyfill.md
@@ -0,0 +1,108 @@
+# Web Extension Polyfill
+
+## Overview
+
+WXT is built on top [`webextension-polyfill` by Mozilla](https://www.npmjs.com/package/webextension-polyfill). The polyfill standardizes much of web extension APIs so they behave the same across different browsers and manifest versions.
+
+Unlike with Chrome Extension development, which uses a `chrome` global, you need to import the `browser` variable from WXT to use the polyfill:
+
+```ts
+import { browser } from 'wxt/browser';
+
+console.log(browser.runtime.id);
+```
+
+If you use auto-imports (enabled by default), you don't need to import this variable, it will work just like the `chrome` global:
+
+```ts
+console.log(browser.runtime.id);
+```
+
+## Handling Differences
+
+Web extensions behave **_VERY_** differently between browsers and manifest versions. You will have to handle these API differences yourself.
+
+:::info
+MDN has great compatibility tables for tracking which browsers support which APIs: [Web Extension Browser Support for JavaScript APIs](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs)
+:::
+
+Lets go over a few approaches:
+
+1. **Feature detection**: If an API isn't available, it is `undefined`. So check if that's the case before using it.
+
+   ```ts
+   if (browser.runtime.onStartup) {
+     browser.runtime.onStartup.addListener(...);
+   }
+   ```
+
+   If there's a similar API you can fallback on, you can do something like this:
+
+   ```ts
+   (browser.action ?? browser.browserAction).setBadgeColor('red');
+   ```
+
+2. **Check the browser**: WXT provides environment variables about which browser is being targetted.
+   ```ts
+   if (!import.meta.env.SAFARI) {
+     // Safari doesn't implement `onStartup` correctly, so we need a custom solution
+     // ...
+   } else {
+     browser.runtime.onStartup.addListener(...)
+   }
+   ```
+3. **Check the manifest version**: WXT provides environment variables about which manifest version is being targetted.
+   ```ts
+   if (import.meta.env.MANIFEST_VERSION === 3) {
+     // MV3 only code...
+   } else {
+     // MV2 only code...
+   }
+   ```
+
+### Environment Variables
+
+| Name                               | Type      | Description                                           |
+| ---------------------------------- | --------- | ----------------------------------------------------- |
+| `import.meta.env.BROWSER`          | `string`  | The target browser                                    |
+| `import.meta.env.MANIFEST_VERSION` | `2 │ 3`   | The target manifest version                           |
+| `import.meta.env.CHROME`           | `boolean` | equivalent to `import.meta.env.BROWSER === "chrome"`  |
+| `import.meta.env.FIREFOX`          | `boolean` | equivalent to `import.meta.env.BROWSER === "firefox"` |
+| `import.meta.env.SAFARI`           | `boolean` | equivalent to `import.meta.env.BROWSER === "safari"`  |
+| `import.meta.env.EDGE`             | `boolean` | equivalent to `import.meta.env.BROWSER === "edge"`    |
+| `import.meta.env.OPERA`            | `boolean` | equivalent to `import.meta.env.BROWSER === "opera"`   |
+
+WXT uses Vite, so all of Vite's `import.meta.env` variables are also available:
+
+<https://vitejs.dev/guide/env-and-mode#env-variables>
+
+## Augmented Types
+
+Based on the files in your project, WXT will modify some of the polyfill's types to be type-safe.
+
+For example, `browser.runtime.getURL` will be typed to only allow getting the URL of known files.
+
+## Missing Types
+
+Some newer APIs that Chrome provides are missing types. But don't worry, the APIs are present at runtime! The polyfill only provides types for standard and stable APIs that work on all browsers, so just be careful when you use them.
+
+If you're using TypeScript, you can use `@ts-expect-error` to ignore any errors when using an API that doesn't have any types.
+
+```ts
+// @ts-expect-error: desktopCapture is not typed
+browser.desktopCapture.chooseDesktopMedia(...)
+```
+
+Note that when running this code in a different browser that doesn't support the `desktopCapture` API, `browser.desktopCapture` will evaluate to `undefined` and an error will be thrown.
+
+## Missing Permissions
+
+Just like with the `chrome` global, you need to request the required permissions to use each API. Otherwise, `browser.{apiName}` will be `undefined`.
+
+For example, if you try to use `browser.storage.local.getItem(...)` without requesting the `storage` permission, the extension will throw an error:
+
+```
+Cannot access property "local" of undefined.
+```
+
+You can request permissions using the [`wxt.config.ts` file](/guide/directory-structure/wxt-config#permissions).
diff --git a/docs/guide/key-concepts/wxt-submit.md b/docs/guide/key-concepts/wxt-submit.md
new file mode 100644
index 00000000..2c194929
--- /dev/null
+++ b/docs/guide/key-concepts/wxt-submit.md
@@ -0,0 +1,9 @@
+# `wxt submit`
+
+> Alias for [`publish-browser-extension`](https://www.npmjs.com/package/publish-browser-extension)
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.submit }}</code></pre></div>
diff --git a/docs/index.md b/docs/index.md
index 06408bfc..08b29442 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -70,29 +70,22 @@ features:
     linkText: Read docs
 ---
 
-<section class="vp-doc" style="padding: 0 48px">
-  <div class="container">
-    <h2>Put <span style="color: var(--vp-c-brand-1)">Developer Experience</span> First</h2>
-    <p>
-      WXT's simplifies the chrome extension development process by providing tools for zipping and publishing, the best-in-class dev mode, an opinionated project structure, and more. Iterate faster, develop features not build scripts, and use everything the JS ecosystem has to offer.
-    </p>
-    <div style="margin: auto; width: 100%; max-width: 900px; text-align: center">
-      <video src="https://github.com/wxt-dev/wxt/assets/10101283/4d678939-1bdb-495c-9c36-3aa281d84c94" controls></video>
-      <br />
-      <small>
-        And who doesn't appreciate a beautiful CLI?
-      </small>
-    </div>
-  </div>
-</section>
+## Put <span style="color: var(--vp-c-brand-1)">Developer Experience</span> First
+
+WXT's simplifies the chrome extension development process by providing tools for zipping and publishing, the best-in-class dev mode, an opinionated project structure, and more. Iterate faster, develop features not build scripts, and use everything the JS ecosystem has to offer.
+
+<div style="margin: auto; width: 100%; max-width: 900px; text-align: center">
+  <video src="https://github.com/wxt-dev/wxt/assets/10101283/4d678939-1bdb-495c-9c36-3aa281d84c94" controls></video>
+  <br />
+  <small>
+    And who doesn't appreciate a beautiful CLI?
+  </small>
+</div>
+
+## Who's Using WXT?
+
+Battle tested and ready for production. Explore chrome extensions made with WXT.
 
 <ClientOnly>
   <UsingWxtSection />
 </ClientOnly>
-
-<style scoped>
-.container {
-  margin: 0 auto;
-  max-width: 1152px;
-}
-</style>
diff --git a/docs/public/_redirects b/docs/public/_redirects
index 922e8902..595e8d0e 100644
--- a/docs/public/_redirects
+++ b/docs/public/_redirects
@@ -2,8 +2,8 @@
 # https://docs.netlify.com/routing/redirects/
 
 # Old URLs -> New URLs
-/config.html                    /api/wxt/interfaces/InlineConfig.html
-/api/config.html                /api/wxt/interfaces/InlineConfig.html
+/config.html                    /api/reference/wxt/interfaces/InlineConfig.html
+/api/config.html                /api/reference/wxt/interfaces/InlineConfig.html
 /entrypoints                    /entrypoints/background.html
 /get-started/assets.html        /guide/assets.html
 /get-started/build-targets.html /guide/multiple-browsers.html
diff --git a/docs/typedoc.json b/docs/typedoc.json
index f09aff57..5ac20200 100644
--- a/docs/typedoc.json
+++ b/docs/typedoc.json
@@ -3,7 +3,7 @@
   "entryPointStrategy": "packages",
   "entryPoints": ["../packages/wxt"],
   "plugin": ["typedoc-plugin-markdown", "typedoc-vitepress-theme"],
-  "out": "./api",
+  "out": "./api/reference",
   "githubPages": false,
   "excludePrivate": true,
   "excludeProtected": true,
diff --git a/package.json b/package.json
index e3936e18..d285b152 100644
--- a/package.json
+++ b/package.json
@@ -30,7 +30,7 @@
     "typedoc-plugin-markdown": "4.0.0-next.23",
     "typedoc-vitepress-theme": "1.0.0-next.3",
     "typescript": "^5.3.2",
-    "vitepress": "1.0.0-rc.34",
+    "vitepress": "^1.2.2",
     "vitest": "^1.5.3",
     "vitest-mock-extended": "^1.3.1",
     "vitest-plugin-random-seed": "^1.0.2",
diff --git a/packages/wxt-demo/vitest.config.ts b/packages/wxt-demo/vitest.config.ts
index bec0c7c2..7bd958d5 100644
--- a/packages/wxt-demo/vitest.config.ts
+++ b/packages/wxt-demo/vitest.config.ts
@@ -6,5 +6,6 @@ export default defineProject({
     mockReset: true,
     restoreMocks: true,
   },
+  // @ts-expect-error
   plugins: [WxtVitest()],
 });
diff --git a/packages/wxt/CHANGELOG.md b/packages/wxt/CHANGELOG.md
index 0bc99bdd..ea1cd905 100644
--- a/packages/wxt/CHANGELOG.md
+++ b/packages/wxt/CHANGELOG.md
@@ -1046,7 +1046,7 @@ Renamed undocumented constants for detecting the build config at runtime in [#38
 
 #### ⚠️ Breaking Changes
 
-- `wxt/storage` no longer relies on [`unstorage`](https://www.npmjs.com/package/unstorage). Some `unstorage` APIs, like `prefixStorage`, have been removed, while others, like `snapshot`, are methods on the new `storage` object. Most of the standard usage remains the same. See https://wxt.dev/guide/storage and https://wxt.dev/api/wxt/storage/ for more details ([#300](https://github.com/wxt-dev/wxt/pull/300))
+- `wxt/storage` no longer relies on [`unstorage`](https://www.npmjs.com/package/unstorage). Some `unstorage` APIs, like `prefixStorage`, have been removed, while others, like `snapshot`, are methods on the new `storage` object. Most of the standard usage remains the same. See https://wxt.dev/guide/storage and https://wxt.dev/api/reference/wxt/storage/ for more details ([#300](https://github.com/wxt-dev/wxt/pull/300))
 
 ## v0.12.5
 
diff --git a/packages/wxt/src/client/content-scripts/ui/index.ts b/packages/wxt/src/client/content-scripts/ui/index.ts
index 62d6a9a4..14e8283d 100644
--- a/packages/wxt/src/client/content-scripts/ui/index.ts
+++ b/packages/wxt/src/client/content-scripts/ui/index.ts
@@ -17,7 +17,7 @@ export * from './types';
 /**
  * Create a content script UI without any isolation.
  *
- * @see https://wxt.dev/guide/content-script-ui.html#integrated
+ * @see https://wxt.dev/guide/key-concepts/content-script-ui.html#integrated
  */
 export function createIntegratedUi<TMounted>(
   ctx: ContentScriptContext,
@@ -53,7 +53,7 @@ export function createIntegratedUi<TMounted>(
 /**
  * Create a content script UI using an iframe.
  *
- * @see https://wxt.dev/guide/content-script-ui.html#iframe
+ * @see https://wxt.dev/guide/key-concepts/content-script-ui.html#iframe
  */
 export function createIframeUi<TMounted>(
   ctx: ContentScriptContext,
@@ -95,7 +95,7 @@ export function createIframeUi<TMounted>(
  *
  * > This function is async because it has to load the CSS via a network call.
  *
- * @see https://wxt.dev/guide/content-script-ui.html#shadowroot
+ * @see https://wxt.dev/guide/key-concepts/content-script-ui.html#shadowroot
  */
 export async function createShadowRootUi<TMounted>(
   ctx: ContentScriptContext,
diff --git a/packages/wxt/vitest.config.ts b/packages/wxt/vitest.config.ts
index 1aa9b1db..485aecaf 100644
--- a/packages/wxt/vitest.config.ts
+++ b/packages/wxt/vitest.config.ts
@@ -16,6 +16,7 @@ export default defineProject({
     setupFiles: ['vitest.setup.ts'],
     testTimeout: 120e3,
   },
+  // @ts-expect-error
   plugins: [RandomSeed()],
   resolve: {
     alias: {
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index c0cb9487..6f2e4b13 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -45,8 +45,8 @@ importers:
         specifier: ^5.3.2
         version: 5.3.3
       vitepress:
-        specifier: 1.0.0-rc.34
-        version: 1.0.0-rc.34(typescript@5.3.3)
+        specifier: ^1.2.2
+        version: 1.2.2(typescript@5.3.3)
       vitest:
         specifier: ^1.5.3
         version: 1.5.3
@@ -515,14 +515,14 @@ packages:
       - supports-color
     dev: false
 
-  /@docsearch/css@3.5.2:
-    resolution: {integrity: sha512-SPiDHaWKQZpwR2siD0KQUwlStvIAnEyK6tAE2h2Wuoq8ue9skzhlyVQ1ddzOxX6khULnAALDiR/isSF3bnuciA==}
+  /@docsearch/css@3.6.0:
+    resolution: {integrity: sha512-+sbxb71sWre+PwDK7X2T8+bhS6clcVMLwBPznX45Qu6opJcgRjAp7gYSDzVFp187J+feSj5dNBN1mJoi6ckkUQ==}
     dev: true
 
-  /@docsearch/js@3.5.2:
-    resolution: {integrity: sha512-p1YFTCDflk8ieHgFJYfmyHBki1D61+U9idwrLh+GQQMrBSP3DLGKpy0XUJtPjAOPltcVbqsTjiPFfH7JImjUNg==}
+  /@docsearch/js@3.6.0:
+    resolution: {integrity: sha512-QujhqINEElrkIfKwyyyTfbsfMAYCkylInLYMRqHy7PHc8xTBQCow73tlo/Kc7oIwBrCLf0P3YhjlOeV4v8hevQ==}
     dependencies:
-      '@docsearch/react': 3.5.2
+      '@docsearch/react': 3.6.0
       preact: 10.18.1
     transitivePeerDependencies:
       - '@algolia/client-search'
@@ -532,8 +532,8 @@ packages:
       - search-insights
     dev: true
 
-  /@docsearch/react@3.5.2:
-    resolution: {integrity: sha512-9Ahcrs5z2jq/DcAvYtvlqEBHImbm4YJI8M9y0x6Tqg598P40HTEkX7hsMcIuThI+hTFxRGZ9hll0Wygm2yEjng==}
+  /@docsearch/react@3.6.0:
+    resolution: {integrity: sha512-HUFut4ztcVNmqy9gp/wxNbC7pTOHhgVVkHVGCACTuLhUKUhKAF9KYHJtMiLUJxEqiFLQiuri1fWF8zqwM/cu1w==}
     peerDependencies:
       '@types/react': '>= 16.8.0 < 19.0.0'
       react: '>= 16.8.0 < 19.0.0'
@@ -551,7 +551,7 @@ packages:
     dependencies:
       '@algolia/autocomplete-core': 1.9.3(algoliasearch@4.20.0)
       '@algolia/autocomplete-preset-algolia': 1.9.3(algoliasearch@4.20.0)
-      '@docsearch/css': 3.5.2
+      '@docsearch/css': 3.6.0
       algoliasearch: 4.20.0
     transitivePeerDependencies:
       - '@algolia/client-search'
@@ -1358,6 +1358,16 @@ packages:
     resolution: {integrity: sha512-831qok9r2t8AlxLko40y2ebgSDhenenCatLVeW/uBtnHPyhHOvG0C7TvfgecV+wHzIm5KUICgzmVpWS+IMEAeg==}
     dev: true
 
+  /@shikijs/core@1.6.2:
+    resolution: {integrity: sha512-guW5JeDzZ7uwOjTfCOFZ2VtVXk5tmkMzBYbKGfXsmAH1qYOej49L5jQDcGmwd6/OgvpmWhzO2GNJkQIFnbwLPQ==}
+    dev: true
+
+  /@shikijs/transformers@1.6.2:
+    resolution: {integrity: sha512-ndqTWyHnxmsLkowhKWTam26opw8hg5a34y6FAUG/Xf6E49n3MM//nenKxXiWpPYkNPl1KZnYXB1k+Ia46wjOZg==}
+    dependencies:
+      shiki: 1.6.2
+    dev: true
+
   /@sinclair/typebox@0.27.8:
     resolution: {integrity: sha512-+Fj43pSMwJs4KRrH/938Uf+uAELIgVBmQzg/q1YG10djyfA3TnrU8N8XzqCh/okZdszqBQTZf96idMfE5lnwTA==}
     dev: true
@@ -1403,8 +1413,8 @@ packages:
       '@types/node': 20.10.3
     dev: true
 
-  /@types/linkify-it@3.0.4:
-    resolution: {integrity: sha512-hPpIeeHb/2UuCw06kSNAOVWgehBLXEo0/fUs0mw3W2qhqX89PI2yvok83MnuctYGCPrabGIoi0fFso4DQ+sNUQ==}
+  /@types/linkify-it@5.0.0:
+    resolution: {integrity: sha512-sVDA58zAw4eWAffKOaQH5/5j3XeayukzDk+ewSsnv3p4yJEZHCCzMDiZM8e0OUrRvmpGZ85jf4yDHkHsgBNr9Q==}
     dev: true
 
   /@types/lodash.merge@4.6.9:
@@ -1417,15 +1427,15 @@ packages:
     resolution: {integrity: sha512-YI/M/4HRImtNf3pJgbF+W6FrXovqj+T+/HpENLTooK9PnkacBsDpeP3IpHab40CClUfhNmdM2WTNP2sa2dni5Q==}
     dev: true
 
-  /@types/markdown-it@13.0.7:
-    resolution: {integrity: sha512-U/CBi2YUUcTHBt5tjO2r5QV/x0Po6nsYwQU4Y04fBS6vfoImaiZ6f8bi3CjTCxBPQSO1LMyUqkByzi8AidyxfA==}
+  /@types/markdown-it@14.1.1:
+    resolution: {integrity: sha512-4NpsnpYl2Gt1ljyBGrKMxFYAYvpqbnnkgP/i/g+NLpjEUa3obn1XJCur9YbEXKDAkaXqsR1LbDnGEJ0MmKFxfg==}
     dependencies:
-      '@types/linkify-it': 3.0.4
-      '@types/mdurl': 1.0.4
+      '@types/linkify-it': 5.0.0
+      '@types/mdurl': 2.0.0
     dev: true
 
-  /@types/mdurl@1.0.4:
-    resolution: {integrity: sha512-ARVxjAEX5TARFRzpDRVC6cEk0hUIXCCwaMhz8y7S1/PxU6zZS1UMjyobz7q4w/D/R552r4++EhwmXK1N2rAy0A==}
+  /@types/mdurl@2.0.0:
+    resolution: {integrity: sha512-RGdgjQUZba5p6QEFAVx2OGb8rQDL/cPRG7GiedRzMcJ1tYnUANBncjbSB1NRGwbvjcPeikRABz2nshyPk1bhWg==}
     dev: true
 
   /@types/minimatch@3.0.5:
@@ -1496,15 +1506,15 @@ packages:
       '@types/node': 20.10.3
     optional: true
 
-  /@vitejs/plugin-vue@5.0.2(vite@5.2.8)(vue@3.4.21):
-    resolution: {integrity: sha512-kEjJHrLb5ePBvjD0SPZwJlw1QTRcjjCA9sB5VyfonoXVBxTS7TMnqL6EkLt1Eu61RDeiuZ/WN9Hf6PxXhPI2uA==}
+  /@vitejs/plugin-vue@5.0.5(vite@5.2.12)(vue@3.4.27):
+    resolution: {integrity: sha512-LOjm7XeIimLBZyzinBQ6OSm3UBCNVCpLkxGC0oWmm2YPzVZoxMsdvNVimLTBzpAnR9hl/yn1SHGuRfe6/Td9rQ==}
     engines: {node: ^18.0.0 || >=20.0.0}
     peerDependencies:
       vite: ^5.0.0
       vue: ^3.2.25
     dependencies:
-      vite: 5.2.8(@types/node@20.10.3)
-      vue: 3.4.21(typescript@5.3.3)
+      vite: 5.2.12
+      vue: 3.4.27(typescript@5.3.3)
     dev: true
 
   /@vitest/coverage-v8@1.2.2(vitest@1.5.3):
@@ -1579,6 +1589,16 @@ packages:
       source-map-js: 1.2.0
     dev: true
 
+  /@vue/compiler-core@3.4.27:
+    resolution: {integrity: sha512-E+RyqY24KnyDXsCuQrI+mlcdW3ALND6U7Gqa/+bVwbcpcR3BRRIckFoz7Qyd4TTlnugtwuI7YgjbvsLmxb+yvg==}
+    dependencies:
+      '@babel/parser': 7.24.5
+      '@vue/shared': 3.4.27
+      entities: 4.5.0
+      estree-walker: 2.0.2
+      source-map-js: 1.2.0
+    dev: true
+
   /@vue/compiler-dom@3.4.21:
     resolution: {integrity: sha512-IZC6FKowtT1sl0CR5DpXSiEB5ayw75oT2bma1BEhV7RRR1+cfwLrxc2Z8Zq/RGFzJ8w5r9QtCOvTjQgdn0IKmA==}
     dependencies:
@@ -1586,6 +1606,13 @@ packages:
       '@vue/shared': 3.4.21
     dev: true
 
+  /@vue/compiler-dom@3.4.27:
+    resolution: {integrity: sha512-kUTvochG/oVgE1w5ViSr3KUBh9X7CWirebA3bezTbB5ZKBQZwR2Mwj9uoSKRMFcz4gSMzzLXBPD6KpCLb9nvWw==}
+    dependencies:
+      '@vue/compiler-core': 3.4.27
+      '@vue/shared': 3.4.27
+    dev: true
+
   /@vue/compiler-sfc@3.4.21:
     resolution: {integrity: sha512-me7epoTxYlY+2CUM7hy9PCDdpMPfIwrOvAXud2Upk10g4YLv9UBW7kL798TvMeDhPthkZ0CONNrK2GoeI1ODiQ==}
     dependencies:
@@ -1600,6 +1627,20 @@ packages:
       source-map-js: 1.2.0
     dev: true
 
+  /@vue/compiler-sfc@3.4.27:
+    resolution: {integrity: sha512-nDwntUEADssW8e0rrmE0+OrONwmRlegDA1pD6QhVeXxjIytV03yDqTey9SBDiALsvAd5U4ZrEKbMyVXhX6mCGA==}
+    dependencies:
+      '@babel/parser': 7.24.5
+      '@vue/compiler-core': 3.4.27
+      '@vue/compiler-dom': 3.4.27
+      '@vue/compiler-ssr': 3.4.27
+      '@vue/shared': 3.4.27
+      estree-walker: 2.0.2
+      magic-string: 0.30.10
+      postcss: 8.4.38
+      source-map-js: 1.2.0
+    dev: true
+
   /@vue/compiler-ssr@3.4.21:
     resolution: {integrity: sha512-M5+9nI2lPpAsgXOGQobnIueVqc9sisBFexh5yMIMRAPYLa7+5wEJs8iqOZc1WAa9WQbx9GR2twgznU8LTIiZ4Q==}
     dependencies:
@@ -1607,8 +1648,38 @@ packages:
       '@vue/shared': 3.4.21
     dev: true
 
-  /@vue/devtools-api@6.5.1:
-    resolution: {integrity: sha512-+KpckaAQyfbvshdDW5xQylLni1asvNSGme1JFs8I1+/H5pHEhqUKMEQD/qn3Nx5+/nycBq11qAEi8lk+LXI2dA==}
+  /@vue/compiler-ssr@3.4.27:
+    resolution: {integrity: sha512-CVRzSJIltzMG5FcidsW0jKNQnNRYC8bT21VegyMMtHmhW3UOI7knmUehzswXLrExDLE6lQCZdrhD4ogI7c+vuw==}
+    dependencies:
+      '@vue/compiler-dom': 3.4.27
+      '@vue/shared': 3.4.27
+    dev: true
+
+  /@vue/devtools-api@7.2.1(vue@3.4.27):
+    resolution: {integrity: sha512-6oNCtyFOrNdqm6GUkFujsCgFlpbsHLnZqq7edeM/+cxAbMyCWvsaCsIMUaz7AiluKLccCGEM8fhOsjaKgBvb7g==}
+    dependencies:
+      '@vue/devtools-kit': 7.2.1(vue@3.4.27)
+    transitivePeerDependencies:
+      - vue
+    dev: true
+
+  /@vue/devtools-kit@7.2.1(vue@3.4.27):
+    resolution: {integrity: sha512-Wak/fin1X0Q8LLIfCAHBrdaaB+R6IdpSXsDByPHbQ3BmkCP0/cIo/oEGp9i0U2+gEqD4L3V9RDjNf1S34DTzQQ==}
+    peerDependencies:
+      vue: ^3.0.0
+    dependencies:
+      '@vue/devtools-shared': 7.2.1
+      hookable: 5.5.3
+      mitt: 3.0.1
+      perfect-debounce: 1.0.0
+      speakingurl: 14.0.1
+      vue: 3.4.27(typescript@5.3.3)
+    dev: true
+
+  /@vue/devtools-shared@7.2.1:
+    resolution: {integrity: sha512-PCJF4UknJmOal68+X9XHyVeQ+idv0LFujkTOIW30+GaMJqwFVN9LkQKX4gLqn61KkGMdJTzQ1bt7EJag3TI6AA==}
+    dependencies:
+      rfdc: 1.3.1
     dev: true
 
   /@vue/reactivity@3.4.21:
@@ -1617,6 +1688,12 @@ packages:
       '@vue/shared': 3.4.21
     dev: true
 
+  /@vue/reactivity@3.4.27:
+    resolution: {integrity: sha512-kK0g4NknW6JX2yySLpsm2jlunZJl2/RJGZ0H9ddHdfBVHcNzxmQ0sS0b09ipmBoQpY8JM2KmUw+a6sO8Zo+zIA==}
+    dependencies:
+      '@vue/shared': 3.4.27
+    dev: true
+
   /@vue/runtime-core@3.4.21:
     resolution: {integrity: sha512-pQthsuYzE1XcGZznTKn73G0s14eCJcjaLvp3/DKeYWoFacD9glJoqlNBxt3W2c5S40t6CCcpPf+jG01N3ULyrA==}
     dependencies:
@@ -1624,6 +1701,13 @@ packages:
       '@vue/shared': 3.4.21
     dev: true
 
+  /@vue/runtime-core@3.4.27:
+    resolution: {integrity: sha512-7aYA9GEbOOdviqVvcuweTLe5Za4qBZkUY7SvET6vE8kyypxVgaT1ixHLg4urtOlrApdgcdgHoTZCUuTGap/5WA==}
+    dependencies:
+      '@vue/reactivity': 3.4.27
+      '@vue/shared': 3.4.27
+    dev: true
+
   /@vue/runtime-dom@3.4.21:
     resolution: {integrity: sha512-gvf+C9cFpevsQxbkRBS1NpU8CqxKw0ebqMvLwcGQrNpx6gqRDodqKqA+A2VZZpQ9RpK2f9yfg8VbW/EpdFUOJw==}
     dependencies:
@@ -1632,6 +1716,14 @@ packages:
       csstype: 3.1.3
     dev: true
 
+  /@vue/runtime-dom@3.4.27:
+    resolution: {integrity: sha512-ScOmP70/3NPM+TW9hvVAz6VWWtZJqkbdf7w6ySsws+EsqtHvkhxaWLecrTorFxsawelM5Ys9FnDEMt6BPBDS0Q==}
+    dependencies:
+      '@vue/runtime-core': 3.4.27
+      '@vue/shared': 3.4.27
+      csstype: 3.1.3
+    dev: true
+
   /@vue/server-renderer@3.4.21(vue@3.4.21):
     resolution: {integrity: sha512-aV1gXyKSN6Rz+6kZ6kr5+Ll14YzmIbeuWe7ryJl5muJ4uwSwY/aStXTixx76TwkZFJLm1aAlA/HSWEJ4EyiMkg==}
     peerDependencies:
@@ -1642,24 +1734,38 @@ packages:
       vue: 3.4.21(typescript@5.3.3)
     dev: true
 
+  /@vue/server-renderer@3.4.27(vue@3.4.27):
+    resolution: {integrity: sha512-dlAMEuvmeA3rJsOMJ2J1kXU7o7pOxgsNHVr9K8hB3ImIkSuBrIdy0vF66h8gf8Tuinf1TK3mPAz2+2sqyf3KzA==}
+    peerDependencies:
+      vue: 3.4.27
+    dependencies:
+      '@vue/compiler-ssr': 3.4.27
+      '@vue/shared': 3.4.27
+      vue: 3.4.27(typescript@5.3.3)
+    dev: true
+
   /@vue/shared@3.4.21:
     resolution: {integrity: sha512-PuJe7vDIi6VYSinuEbUIQgMIRZGgM8e4R+G+/dQTk0X1NEdvgvvgv7m+rfmDH1gZzyA1OjjoWskvHlfRNfQf3g==}
     dev: true
 
-  /@vueuse/core@10.7.1(vue@3.4.21):
-    resolution: {integrity: sha512-74mWHlaesJSWGp1ihg76vAnfVq9NTv1YT0SYhAQ6zwFNdBkkP+CKKJmVOEHcdSnLXCXYiL5e7MaewblfiYLP7g==}
+  /@vue/shared@3.4.27:
+    resolution: {integrity: sha512-DL3NmY2OFlqmYYrzp39yi3LDkKxa5vZVwxWdQ3rG0ekuWscHraeIbnI8t+aZK7qhYqEqWKTUdijadunb9pnrgA==}
+    dev: true
+
+  /@vueuse/core@10.10.0(vue@3.4.27):
+    resolution: {integrity: sha512-vexJ/YXYs2S42B783rI95lMt3GzEwkxzC8Hb0Ndpd8rD+p+Lk/Za4bd797Ym7yq4jXqdSyj3JLChunF/vyYjUw==}
     dependencies:
       '@types/web-bluetooth': 0.0.20
-      '@vueuse/metadata': 10.7.1
-      '@vueuse/shared': 10.7.1(vue@3.4.21)
-      vue-demi: 0.14.6(vue@3.4.21)
+      '@vueuse/metadata': 10.10.0
+      '@vueuse/shared': 10.10.0(vue@3.4.27)
+      vue-demi: 0.14.8(vue@3.4.27)
     transitivePeerDependencies:
       - '@vue/composition-api'
       - vue
     dev: true
 
-  /@vueuse/integrations@10.7.1(focus-trap@7.5.4)(vue@3.4.21):
-    resolution: {integrity: sha512-cKo5LEeKVHdBRBtMTOrDPdR0YNtrmN9IBfdcnY2P3m5LHVrsD0xiHUtAH1WKjHQRIErZG6rJUa6GA4tWZt89Og==}
+  /@vueuse/integrations@10.10.0(focus-trap@7.5.4)(vue@3.4.27):
+    resolution: {integrity: sha512-vHGeK7X6mkdkpcm1eE9t3Cpm21pNVfZRwrjwwbrEs9XftnSgszF4831G2rei8Dt9cIYJIfFV+iyx/29muimJPQ==}
     peerDependencies:
       async-validator: '*'
       axios: '*'
@@ -1699,23 +1805,23 @@ packages:
       universal-cookie:
         optional: true
     dependencies:
-      '@vueuse/core': 10.7.1(vue@3.4.21)
-      '@vueuse/shared': 10.7.1(vue@3.4.21)
+      '@vueuse/core': 10.10.0(vue@3.4.27)
+      '@vueuse/shared': 10.10.0(vue@3.4.27)
       focus-trap: 7.5.4
-      vue-demi: 0.14.6(vue@3.4.21)
+      vue-demi: 0.14.8(vue@3.4.27)
     transitivePeerDependencies:
       - '@vue/composition-api'
       - vue
     dev: true
 
-  /@vueuse/metadata@10.7.1:
-    resolution: {integrity: sha512-jX8MbX5UX067DYVsbtrmKn6eG6KMcXxLRLlurGkZku5ZYT3vxgBjui2zajvUZ18QLIjrgBkFRsu7CqTAg18QFw==}
+  /@vueuse/metadata@10.10.0:
+    resolution: {integrity: sha512-UNAo2sTCAW5ge6OErPEHb5z7NEAg3XcO9Cj7OK45aZXfLLH1QkexDcZD77HBi5zvEiLOm1An+p/4b5K3Worpug==}
     dev: true
 
-  /@vueuse/shared@10.7.1(vue@3.4.21):
-    resolution: {integrity: sha512-v0jbRR31LSgRY/C5i5X279A/WQjD6/JsMzGa+eqt658oJ75IvQXAeONmwvEMrvJQKnRElq/frzBR7fhmWY5uLw==}
+  /@vueuse/shared@10.10.0(vue@3.4.27):
+    resolution: {integrity: sha512-2aW33Ac0Uk0U+9yo3Ypg9s5KcR42cuehRWl7vnUHadQyFvCktseyxxEPBi1Eiq4D2yBGACOnqLZpx1eMc7g5Og==}
     dependencies:
-      vue-demi: 0.14.6(vue@3.4.21)
+      vue-demi: 0.14.8(vue@3.4.27)
     transitivePeerDependencies:
       - '@vue/composition-api'
       - vue
@@ -3218,7 +3324,6 @@ packages:
 
   /hookable@5.5.3:
     resolution: {integrity: sha512-Yc+BQe8SvoXH1643Qez1zqLRmbA5rCL+sSmk6TVos0LWVfNIB7PGncdlId77WzLGSIB5KaWgTaNTs2lNVEI6VQ==}
-    dev: false
 
   /hosted-git-info@2.8.9:
     resolution: {integrity: sha512-mxIDAb9Lsm6DoOJ7xH+5+X4y1LU/4Hi50L9C5sIswK3JzULS4bwk1FvjdBgvYR4bzT4tuUQiC15FE2f5HbLvYw==}
@@ -3914,6 +4019,12 @@ packages:
     resolution: {integrity: sha512-zTU3DaZaF3Rt9rhN3uBMGQD3dD2/vFQqnvZCDv4dl5iOzq2IZQqTxu90r4E5J+nP70J3ilqVCrbho2eWaeW8Ow==}
     dev: true
 
+  /magic-string@0.30.10:
+    resolution: {integrity: sha512-iIRwTIf0QKV3UAnYK4PU8uiEc4SRh5jX0mwpIwETPpHdhVM4f53RSwS/vXvN1JhGX+Cs7B8qIq3d6AH49O5fAQ==}
+    dependencies:
+      '@jridgewell/sourcemap-codec': 1.4.15
+    dev: true
+
   /magic-string@0.30.8:
     resolution: {integrity: sha512-ISQTe55T2ao7XtlAStud6qwYPZjE4GK1S/BeVPus4jrq6JuOnQ00YKQC581RWhR122W7msZV263KzVeLoqidyQ==}
     engines: {node: '>=12'}
@@ -4035,6 +4146,10 @@ packages:
       yallist: 4.0.0
     dev: false
 
+  /mitt@3.0.1:
+    resolution: {integrity: sha512-vKivATfr97l2/QBCYAkXYDbrIWPM2IIKEl7YPhjCvKlG3kE2gm+uBo6nEXK3M5/Ffh/FLpKExzOQ3JJoJGFKBw==}
+    dev: true
+
   /mkdirp@0.5.6:
     resolution: {integrity: sha512-FP+p8RB8OWpF3YZBCrP5gtADmtXApB5AMLn+vdyA+PyxCjrCs00mjyUozssO33cwDeT3wNGdLxJ5M//YqtHAJw==}
     hasBin: true
@@ -4068,11 +4183,6 @@ packages:
     resolution: {integrity: sha512-tzzskb3bG8LvYGFF/mDTpq3jpI6Q9wc3LEmBaghu+DdCssd1FakN7Bc0hVNmEyGq1bq3RgfkCb3cmQLpNPOroA==}
     engines: {node: '>=4'}
 
-  /mrmime@2.0.0:
-    resolution: {integrity: sha512-eu38+hdgojoyq63s+yTpN4XMBdt5l8HhMhc4VKLO9KM5caLIBvUm4thi7fFaxyTmCKeNnXZ5pAlBwCUnhA09uw==}
-    engines: {node: '>=10'}
-    dev: true
-
   /ms@2.0.0:
     resolution: {integrity: sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A==}
     dev: false
@@ -4471,7 +4581,6 @@ packages:
 
   /perfect-debounce@1.0.0:
     resolution: {integrity: sha512-xCy9V055GLEqoFaHoC1SoLIaLmWctgCUaBaWxDZ7/Zx4CTyX7cJQLJOok/orfjZAh9kEYpjJa4d0KcJmCbctZA==}
-    dev: false
 
   /picocolors@1.0.0:
     resolution: {integrity: sha512-1fygroTLlHu66zi26VoTDv8yRgm0Fccecssto+MhsZ0D/DGW2sm8E8AjW7NU5VVTRt5GxbeZ5qBuJr+HyLYkjQ==}
@@ -4972,20 +5081,10 @@ packages:
       vscode-textmate: 8.0.0
     dev: true
 
-  /shikiji-core@0.9.16:
-    resolution: {integrity: sha512-eJIK8/IpzvAGnbckCE2Qf/fOSfpjVLSosUfI3pQAnbphGXagEqiRcT/gyVtL4llqmBh0nexqRdJKMFZF3A6ayw==}
-    dev: true
-
-  /shikiji-transformers@0.9.16:
-    resolution: {integrity: sha512-DcvhYtLc3Xtme070vgyyeHX0XrNK0zHrKIiPk8wcptFbFUuS65qYDd/UFl68+R8KhdoSFTM9EXlBa9MhrGlbaw==}
+  /shiki@1.6.2:
+    resolution: {integrity: sha512-X3hSm5GzzBd/BmPmGfkueOUADLyBoZo1ojYQXhd+NU2VJn458yt4duaS0rVzC+WtqftSV7mTVvDw+OB9AHi3Eg==}
     dependencies:
-      shikiji: 0.9.16
-    dev: true
-
-  /shikiji@0.9.16:
-    resolution: {integrity: sha512-QeSwiW88gHke9deQ5Av1f6CEVPGW/riRMPT3vMDGPnASCOhBZK4TYk5ZRoa2qYLncPZS5kXKwcggccQvg3+U7Q==}
-    dependencies:
-      shikiji-core: 0.9.16
+      '@shikijs/core': 1.6.2
     dev: true
 
   /side-channel@1.0.4:
@@ -5093,6 +5192,11 @@ packages:
     resolution: {integrity: sha512-XkD+zwiqXHikFZm4AX/7JSCXA98U5Db4AFd5XUg/+9UNtnH75+Z9KxtpYiJZx36mUDVOwH83pl7yvCer6ewM3w==}
     dev: true
 
+  /speakingurl@14.0.1:
+    resolution: {integrity: sha512-1POYv7uv2gXoyGFpBCmpDVSNV74IfsWlDW216UPjbWufNf+bSU6GdbDsxdcxtfwb4xlI3yxzOTKClUosxARYrQ==}
+    engines: {node: '>=0.10.0'}
+    dev: true
+
   /split@1.0.1:
     resolution: {integrity: sha512-mTyOoPbrivtXnwnIxZRFYRrPNtEFKlpB2fvjSnCQUiAA6qAZzqwna5envK4uk6OIeP17CsdF3rSBGYVBsU0Tkg==}
     dependencies:
@@ -5631,7 +5735,7 @@ packages:
       debug: 4.3.4
       pathe: 1.1.2
       picocolors: 1.0.0
-      vite: 5.2.8(@types/node@20.10.3)
+      vite: 5.2.12
     transitivePeerDependencies:
       - '@types/node'
       - less
@@ -5643,6 +5747,41 @@ packages:
       - terser
     dev: true
 
+  /vite@5.2.12:
+    resolution: {integrity: sha512-/gC8GxzxMK5ntBwb48pR32GGhENnjtY30G4A0jemunsBkiEZFw60s8InGpN8gkhHEkjnRK1aSAxeQgwvFhUHAA==}
+    engines: {node: ^18.0.0 || >=20.0.0}
+    hasBin: true
+    peerDependencies:
+      '@types/node': ^18.0.0 || >=20.0.0
+      less: '*'
+      lightningcss: ^1.21.0
+      sass: '*'
+      stylus: '*'
+      sugarss: '*'
+      terser: ^5.4.0
+    peerDependenciesMeta:
+      '@types/node':
+        optional: true
+      less:
+        optional: true
+      lightningcss:
+        optional: true
+      sass:
+        optional: true
+      stylus:
+        optional: true
+      sugarss:
+        optional: true
+      terser:
+        optional: true
+    dependencies:
+      esbuild: 0.20.2
+      postcss: 8.4.38
+      rollup: 4.14.0
+    optionalDependencies:
+      fsevents: 2.3.3
+    dev: true
+
   /vite@5.2.8(@types/node@20.10.3):
     resolution: {integrity: sha512-OyZR+c1CE8yeHw5V5t59aXsUPPVTHMDjEZz8MgguLL/Q7NblxhZUlTu9xSPqlsUO/y+X7dlU05jdhvyycD55DA==}
     engines: {node: ^18.0.0 || >=20.0.0}
@@ -5678,34 +5817,34 @@ packages:
     optionalDependencies:
       fsevents: 2.3.3
 
-  /vitepress@1.0.0-rc.34(typescript@5.3.3):
-    resolution: {integrity: sha512-TUbTiSdAZFni2XlHlpx61KikgkQ5uG4Wtmw2R0SXhIOG6qGqzDJczAFjkMc4i45I9c3KyatwOYe8oEfCnzVYwQ==}
+  /vitepress@1.2.2(typescript@5.3.3):
+    resolution: {integrity: sha512-uZ3nXR5NY4nYj3RJWCo5jev9qlNZAQo5SUXu1U0QSUx84cUm/o7hCTDVjZ4njVSVui+PsV1oAbdQOg8ygbaf4w==}
     hasBin: true
     peerDependencies:
-      markdown-it-mathjax3: ^4.3.2
-      postcss: ^8.4.32
+      markdown-it-mathjax3: ^4
+      postcss: ^8
     peerDependenciesMeta:
       markdown-it-mathjax3:
         optional: true
       postcss:
         optional: true
     dependencies:
-      '@docsearch/css': 3.5.2
-      '@docsearch/js': 3.5.2
-      '@types/markdown-it': 13.0.7
-      '@vitejs/plugin-vue': 5.0.2(vite@5.2.8)(vue@3.4.21)
-      '@vue/devtools-api': 6.5.1
-      '@vueuse/core': 10.7.1(vue@3.4.21)
-      '@vueuse/integrations': 10.7.1(focus-trap@7.5.4)(vue@3.4.21)
+      '@docsearch/css': 3.6.0
+      '@docsearch/js': 3.6.0
+      '@shikijs/core': 1.6.2
+      '@shikijs/transformers': 1.6.2
+      '@types/markdown-it': 14.1.1
+      '@vitejs/plugin-vue': 5.0.5(vite@5.2.12)(vue@3.4.27)
+      '@vue/devtools-api': 7.2.1(vue@3.4.27)
+      '@vue/shared': 3.4.27
+      '@vueuse/core': 10.10.0(vue@3.4.27)
+      '@vueuse/integrations': 10.10.0(focus-trap@7.5.4)(vue@3.4.27)
       focus-trap: 7.5.4
       mark.js: 8.11.1
       minisearch: 6.3.0
-      mrmime: 2.0.0
-      shikiji: 0.9.16
-      shikiji-core: 0.9.16
-      shikiji-transformers: 0.9.16
-      vite: 5.2.8(@types/node@20.10.3)
-      vue: 3.4.21(typescript@5.3.3)
+      shiki: 1.6.2
+      vite: 5.2.12
+      vue: 3.4.27(typescript@5.3.3)
     transitivePeerDependencies:
       - '@algolia/client-search'
       - '@types/node'
@@ -5795,7 +5934,7 @@ packages:
       strip-literal: 2.1.0
       tinybench: 2.5.1
       tinypool: 0.8.4
-      vite: 5.2.8(@types/node@20.10.3)
+      vite: 5.2.12
       vite-node: 1.5.3
       why-is-node-running: 2.2.2
     transitivePeerDependencies:
@@ -5816,8 +5955,8 @@ packages:
     resolution: {integrity: sha512-AFbieoL7a5LMqcnOF04ji+rpXadgOXnZsxQr//r83kLPr7biP7am3g9zbaZIaBGwBRWeSvoMD4mgPdX3e4NWBg==}
     dev: true
 
-  /vue-demi@0.14.6(vue@3.4.21):
-    resolution: {integrity: sha512-8QA7wrYSHKaYgUxDA5ZC24w+eHm3sYCbp0EzcDwKqN3p6HqtTCGR/GVsPyZW92unff4UlcSh++lmqDWN3ZIq4w==}
+  /vue-demi@0.14.8(vue@3.4.27):
+    resolution: {integrity: sha512-Uuqnk9YE9SsWeReYqK2alDI5YzciATE0r2SkA6iMAtuXvNTMNACJLJEXNXaEy94ECuBe4Sk6RzRU80kjdbIo1Q==}
     engines: {node: '>=12'}
     hasBin: true
     requiresBuild: true
@@ -5828,7 +5967,7 @@ packages:
       '@vue/composition-api':
         optional: true
     dependencies:
-      vue: 3.4.21(typescript@5.3.3)
+      vue: 3.4.27(typescript@5.3.3)
     dev: true
 
   /vue@3.4.21(typescript@5.3.3):
@@ -5847,6 +5986,22 @@ packages:
       typescript: 5.3.3
     dev: true
 
+  /vue@3.4.27(typescript@5.3.3):
+    resolution: {integrity: sha512-8s/56uK6r01r1icG/aEOHqyMVxd1bkYcSe9j8HcKtr/xTOFWvnzIVTehNW+5Yt89f+DLBe4A569pnZLS5HzAMA==}
+    peerDependencies:
+      typescript: '*'
+    peerDependenciesMeta:
+      typescript:
+        optional: true
+    dependencies:
+      '@vue/compiler-dom': 3.4.27
+      '@vue/compiler-sfc': 3.4.27
+      '@vue/runtime-dom': 3.4.27
+      '@vue/server-renderer': 3.4.27(vue@3.4.27)
+      '@vue/shared': 3.4.27
+      typescript: 5.3.3
+    dev: true
+
   /watchpack@2.4.0:
     resolution: {integrity: sha512-Lcvm7MGST/4fup+ifyKi2hjyIAwcdI4HRgtvTpIUxBRhB+RFtUh8XtDOxUfctVCnhVi+QQj49i91OyvzkJl6cg==}
     engines: {node: '>=10.13.0'}