wip

joetannenbaum · joetannenbaum · commit 3eea36dd48d8 · 2025-11-21T11:13:57.000-05:00
diff --git a/snippets/react-specific.jsx b/snippets/react-specific.jsx
@@ -1,5 +1,3 @@
-import { useCallback, useEffect, useState } from "react";
-
 export const ReactSpecific = ({ children }) => {
     const [code, setCode] = useState(
         localStorage.getItem("code")?.replace(/"/g, "") || null,
diff --git a/snippets/svelte-specific.jsx b/snippets/svelte-specific.jsx
@@ -1,5 +1,3 @@
-import { useCallback, useEffect, useState } from "react";
-
 export const SvelteSpecific = ({ children }) => {
     const [code, setCode] = useState(
         localStorage.getItem("code")?.replace(/"/g, "") || null,
diff --git a/snippets/svelte4-specific.jsx b/snippets/svelte4-specific.jsx
@@ -1,5 +1,3 @@
-import { useCallback, useEffect, useState } from "react";
-
 export const Svelte4Specific = ({ children }) => {
     const [code, setCode] = useState(
         localStorage.getItem("code")?.replace(/"/g, "") || null,
diff --git a/snippets/svelte5-specific.jsx b/snippets/svelte5-specific.jsx
@@ -1,5 +1,3 @@
-import { useCallback, useEffect, useState } from "react";
-
 export const Svelte5Specific = ({ children }) => {
     const [code, setCode] = useState(
         localStorage.getItem("code")?.replace(/"/g, "") || null,
diff --git a/snippets/vue-specific.jsx b/snippets/vue-specific.jsx
@@ -1,5 +1,3 @@
-import { useCallback, useEffect, useState } from "react";
-
 export const VueSpecific = ({ children }) => {
     const [code, setCode] = useState(
         localStorage.getItem("code")?.replace(/"/g, "") || null,
diff --git a/snippets/vue2-specific.jsx b/snippets/vue2-specific.jsx
@@ -1,5 +1,3 @@
-import { useCallback, useEffect, useState } from "react";
-
 export const Vue2Specific = ({ children }) => {
     const [code, setCode] = useState(
         localStorage.getItem("code")?.replace(/"/g, "") || null,
diff --git a/snippets/vue3-specific.jsx b/snippets/vue3-specific.jsx
@@ -1,5 +1,3 @@
-import { useCallback, useEffect, useState } from "react";
-
 export const Vue3Specific = ({ children }) => {
     const [code, setCode] = useState(
         localStorage.getItem("code")?.replace(/"/g, "") || null,
diff --git a/v2/advanced/error-handling.mdx b/v2/advanced/error-handling.mdx
@@ -14,7 +14,7 @@ Inertia solves this issue by showing all non-Inertia responses in a modal. This
 
 By default, Inertia displays error modals using a custom `<div>` overlay. However, you can opt-in to using the native HTML `<dialog>` element instead, which provides built-in modal functionality including backdrop handling.
 
-To enable this, configure the `future.useDialogForErrorModal` option in your [application defaults](/client-side-setup#configuring-defaults).
+To enable this, configure the `future.useDialogForErrorModal` option in your [application defaults](/v2/installation/client-side-setup#configuring-defaults).
 
 ```js
 createInertiaApp({
diff --git a/v2/advanced/events.mdx b/v2/advanced/events.mdx
@@ -471,7 +471,7 @@ The `error` event is not cancelable.
 
 ## Invalid
 
-The `invalid` event fires when a non-Inertia response is received from the server, such as an HTML or vanilla JSON response. A valid Inertia response is a response that has the `X-Inertia` header set to `true` with a `json` payload containing [the page object](/the-protocol#the-page-object).
+The `invalid` event fires when a non-Inertia response is received from the server, such as an HTML or vanilla JSON response. A valid Inertia response is a response that has the `X-Inertia` header set to `true` with a `json` payload containing [the page object](/v2/core-concepts/the-protocol#the-page-object).
 
 This event is fired for all response types, including `200`, `400`, and `500`response codes.
 
@@ -750,4 +750,4 @@ The `prefetched` event is not cancelable.
 
 ## Event Callbacks
 
-In addition to the global events described throughout this page, Inertia also provides a number of [event callbacks](/manual-visits#event-callbacks) that fire when manually making Inertia visits.
+In addition to the global events described throughout this page, Inertia also provides a number of [event callbacks](/v2/the-basics/manual-visits#event-callbacks) that fire when manually making Inertia visits.
diff --git a/v2/data-props/infinite-scroll.mdx b/v2/data-props/infinite-scroll.mdx
@@ -217,7 +217,7 @@ export default function Users({ users }) {
 
 </CodeGroup>
 
-For more information about the reset option, see the [Resetting props](/merging-props#resetting-props) documentation.
+For more information about the reset option, see the [Resetting props](/v2/data-props/merging-props#resetting-props) documentation.
 
 ## Loading Direction
 
diff --git a/v2/data-props/merging-props.mdx b/v2/data-props/merging-props.mdx
@@ -105,7 +105,7 @@ Route::get('/chat', function () {
 
 ## Client Side Visits
 
-You can also merge props directly on the client side without making a server request using [client side visits](/manual-visits#client-side-visits). Inertia provides [prop helper methods](/manual-visits#prop-helpers) that allow you to append, prepend, or replace prop values.
+You can also merge props directly on the client side without making a server request using [client side visits](/v2/the-basics/manual-visits#client-side-visits). Inertia provides [prop helper methods](/v2/the-basics/manual-visits#prop-helpers) that allow you to append, prepend, or replace prop values.
 
 ## Combining with Deferred Props
 
diff --git a/v2/data-props/prefetching.mdx b/v2/data-props/prefetching.mdx
@@ -6,7 +6,7 @@ Inertia supports prefetching data for pages that are likely to be visited next.
 
 ## Link Prefetching
 
-To prefetch data for a page, you can add the `prefetch` prop to the Inertia link component. By default, Inertia will prefetch the data for the page when the user hovers over the link for more than 75ms. You may customize this hover delay by setting the `prefetch.hoverDelay` option in your [application defaults](/client-side-setup#configuring-defaults).
+To prefetch data for a page, you can add the `prefetch` prop to the Inertia link component. By default, Inertia will prefetch the data for the page when the user hovers over the link for more than 75ms. You may customize this hover delay by setting the `prefetch.hoverDelay` option in your [application defaults](/v2/installation/client-side-setup#configuring-defaults).
 
 <CodeGroup>
 
@@ -30,7 +30,7 @@ import { inertia } from '@inertiajs/svelte'
 
 </CodeGroup>
 
-By default, data is cached for 30 seconds before being evicted. You may customize this default value by setting the `prefetch.cacheFor` option in your [application defaults](/client-side-setup#configuring-defaults). You may also customize the cache duration on a per-link basis by passing a `cacheFor` prop to the `Link` component.
+By default, data is cached for 30 seconds before being evicted. You may customize this default value by setting the `prefetch.cacheFor` option in your [application defaults](/v2/installation/client-side-setup#configuring-defaults). You may also customize the cache duration on a per-link basis by passing a `cacheFor` prop to the `Link` component.
 
 <CodeGroup>
 
diff --git a/v2/data-props/remembering-state.mdx b/v2/data-props/remembering-state.mdx
@@ -128,7 +128,7 @@ const form = useRemember({
 
 ## Form Helper
 
-If you're using the [Inertia form helper](/forms#form-helper), you can pass a unique form key as the first argument when instantiating your form. This will cause the form data and errors to automatically be remembered.
+If you're using the [Inertia form helper](/v2/the-basics/forms#form-helper), you can pass a unique form key as the first argument when instantiating your form. This will cause the form data and errors to automatically be remembered.
 
 <CodeGroup>
 
diff --git a/v2/data-props/shared-data.mdx b/v2/data-props/shared-data.mdx
@@ -8,7 +8,7 @@ Sometimes you need to access specific pieces of data on numerous pages within yo
 
 Inertia's server-side adapters all provide a method of making shared data available for every request. This is typically done outside of your controllers. Shared data will be automatically merged with the page props provided in your controller.
 
-In Laravel applications, this is typically handled by the `HandleInertiaRequests` middleware that is automatically installed when installing the [server-side adapter](/server-side-setup#middleware).
+In Laravel applications, this is typically handled by the `HandleInertiaRequests` middleware that is automatically installed when installing the [server-side adapter](/v2/installation/server-side-setup#middleware).
 
 ```php
 class HandleInertiaRequests extends Middleware
diff --git a/v2/getting-started/upgrade-guide.mdx b/v2/getting-started/upgrade-guide.mdx
@@ -70,7 +70,7 @@ The Vue 2 adapter has been removed. Vue 2 reached End of Life on December 3, 202
 
 ### Router `replace` Method
 
-The previously deprecated `router.replace` method has been re-instated, but its functionality has changed. It is now used to make [Client Side](/manual-visits#client-side-visits) page visits. To make server-side visits that replace the current history entry in the browser, use the `replace` option:
+The previously deprecated `router.replace` method has been re-instated, but its functionality has changed. It is now used to make [Client Side](/v2/the-basics/manual-visits#client-side-visits) page visits. To make server-side visits that replace the current history entry in the browser, use the `replace` option:
 
 ```javascript
 router.get('/users', { search: 'John' }, { replace: true })
@@ -80,8 +80,8 @@ router.get('/users', { search: 'John' }, { replace: true })
 
 - Dropped support for Svelte 3 as it reached End of Life on June 20, 2023.
 - The `remember` helper has been rename to `useRemember` to be consistent with other helpers.
-- Updated `setup` callback in `app.js`. You need to pass `props` when initializing the `App` component. [See setup in app.js](/client-side-setup#initialize-the-inertia-app)
-- `setup` callback is now required in `ssr.js`. [See setup in ssr.js](/server-side-rendering#add-server-entry-point)
+- Updated `setup` callback in `app.js`. You need to pass `props` when initializing the `App` component. [See setup in app.js](/v2/installation/client-side-setup#initialize-the-inertia-app)
+- `setup` callback is now required in `ssr.js`. [See setup in ssr.js](/v2/advanced/server-side-rendering#add-server-entry-point)
 
 ### Partial Reloads Are Now Async
 
diff --git a/v2/installation/client-side-setup.mdx b/v2/installation/client-side-setup.mdx
@@ -134,7 +134,7 @@ createInertiaApp({
 });
 ```
 
-The `visitOptions` callback receives the target URL and the current visit options, and should return an object with any options you want to override. For more details on the available configuration options, see the [forms](/forms#form-errors), [prefetching](/v2/data-props/prefetching), and [manual visits](/manual-visits#global-visit-options) documentation.
+The `visitOptions` callback receives the target URL and the current visit options, and should return an object with any options you want to override. For more details on the available configuration options, see the [forms](/v2/the-basics/forms#form-errors), [prefetching](/v2/data-props/prefetching), and [manual visits](/v2/the-basics/manual-visits#global-visit-options) documentation.
 
 ### Updating Configuration at Runtime
 
@@ -246,4 +246,4 @@ createInertiaApp({
 })
 ```
 
-If you change the `id` of the root element, be sure to update it [server-side](/server-side-setup#root-template) as well.
+If you change the `id` of the root element, be sure to update it [server-side](/v2/installation/server-side-setup#root-template) as well.
diff --git a/v2/installation/community-adapters.mdx b/v2/installation/community-adapters.mdx
@@ -0,0 +1,36 @@
+---
+title: Community Adapters
+---
+
+In addition to the officially supported [Laravel](https://laravel.com/) adapter, there are also
+numerous community built server-side adapters available:
+
+- [AdonisJS](https://docs.adonisjs.com/guides/inertia)
+- [ASP.NET](https://github.com/kapi2289/InertiaCore)
+- [CakePHP InertiaJS Plugin](https://github.com/CakeDC/cakephp-inertia)
+- [CakePHP](https://github.com/ishanvyas22/cakephp-inertiajs)
+- [CanJS](https://github.com/cherifGsoul/inertia-can)
+- [Clojure](https://github.com/prestancedesign/inertia-clojure)
+- [ColdBox](https://github.com/elpete/cbInertia)
+- [Django](https://pypi.org/project/inertia-django/)
+- [Echo](https://github.com/kohkimakimoto/inertia-echo)
+- [Flask](https://github.com/j0ack/flask-inertia)
+- [Go (gonertia)](https://github.com/romsar/gonertia)
+- [Go (inertia-go)](https://github.com/petaki/inertia-go)
+- [Grails](https://github.com/matrei/grails-inertia-plugin)
+- [Kirby CMS](https://github.com/tobimori/kirby-inertia)
+- [Mako](https://github.com/inventor96/inertia-mako/)
+- [Masonite](https://github.com/girardinsamuel/masonite-inertia/)
+- [Mithril.js](https://github.com/maicol07/inertia-mithril)
+- [NestJS](https://github.com/harisfi/nestjs-inertia)
+- [Oak](https://github.com/jcs224/oak_inertia)
+- [Phoenix](https://github.com/inertiajs/inertia-phoenix)
+- [PSR-15](https://github.com/cherifGsoul/inertia-psr15)
+- [Rails](https://github.com/inertiajs/inertia-rails)
+- [Rust](https://github.com/stuarth/inertia-rs)
+- [Rust](https://kaiofelps.github.io/inertia-rust/)
+- [Sails](https://github.com/sailscastshq/boring-stack/tree/main/packages/inertia-sails)
+- [Spring/Ktor](https://github.com/Inertia4J/inertia4j)
+- [Symfony](https://github.com/skipthedragon/inertia-bundle)
+- [WordPress](https://github.com/evo-mark/inertia-wordpress)
+- [Yii2](https://github.com/tbreuss/yii2-inertia)
diff --git a/v2/installation/server-side-setup.mdx b/v2/installation/server-side-setup.mdx
@@ -2,7 +2,7 @@
 title: Server-Side Setup
 ---
 
-The first step when installing Inertia is to configure your server-side framework. Inertia maintains an official server-side adapter for [Laravel](https://laravel.com/). For other frameworks, please see the [community adapters](/community-adapters).
+The first step when installing Inertia is to configure your server-side framework. Inertia maintains an official server-side adapter for [Laravel](https://laravel.com/). For other frameworks, please see the [community adapters](/v2/installation/community-adapters).
 
 Inertia is fine-tuned for Laravel, so the documentation examples on this website utilize Laravel. For examples of using Inertia with other server-side frameworks, please refer to the framework specific documentation maintained by that adapter.
 
@@ -59,7 +59,7 @@ These starter kits are the absolute fastest way to start building a new Inertia
         </html>
         ```
 
-        If you change the `id` of the root element, be sure to update it [client-side](/client-side-setup#defining-a-root-element) as well.
+        If you change the `id` of the root element, be sure to update it [client-side](/v2/installation/client-side-setup#defining-a-root-element) as well.
 
         By default, Inertia's Laravel adapter will assume your root template is named `app.blade.php`. If you would like to use a different root view, you can change it using the `Inertia::setRootView()` method.
     </Step>
diff --git a/v2/security/csrf-protection.mdx b/v2/security/csrf-protection.mdx
@@ -62,7 +62,7 @@ The easiest way to implement this is using server-side middleware. Simply includ
 
 When a CSRF token mismatch occurs, your server-side framework will likely throw an exception that results in an error response. For example, when using Laravel, a `TokenMismatchException` is thrown which results in a `419` error page. Since that isn't a valid Inertia response, the error is shown in a modal.
 
-<video controls=""><source src="/mp4/csrf-mismatch-modal.mp4" type="video/mp4"></source></video>Obviously, this isn't a great user experience. A better way to handle these errors is to return a redirect back to the previous page, along with a flash message that the page expired. This will result in a valid Inertia response with the flash message available as a prop which you can then display to the user. Of course, you'll need to share your [flash messages](/shared-data#flash-messages) with Inertia for this to work.
+<video controls=""><source src="/mp4/csrf-mismatch-modal.mp4" type="video/mp4"></source></video>Obviously, this isn't a great user experience. A better way to handle these errors is to return a redirect back to the previous page, along with a flash message that the page expired. This will result in a valid Inertia response with the flash message available as a prop which you can then display to the user. Of course, you'll need to share your [flash messages](/v2/data-props/shared-data#flash-messages) with Inertia for this to work.
 
 When using Laravel, you may modify your application's exception handler to automatically redirect the user back to the page they were previously on while flashing a message to the session. To accomplish this, you may use the `respond` exception method in your application's `bootstrap/app.php` file.
 
diff --git a/v2/the-basics/file-uploads.mdx b/v2/the-basics/file-uploads.mdx
@@ -152,7 +152,7 @@ return (
 
 </CodeGroup>
 
-This example uses the [Inertia form helper](/forms#form-helper) for convenience, since the form helper provides easy access to the current upload progress. However, you are free to submit your forms using [manual Inertia visits](/v2/the-basics/manual-visits) as well.
+This example uses the [Inertia form helper](/v2/the-basics/forms#form-helper) for convenience, since the form helper provides easy access to the current upload progress. However, you are free to submit your forms using [manual Inertia visits](/v2/the-basics/manual-visits) as well.
 
 ## Multipart Limitations
 
diff --git a/v2/the-basics/forms.mdx b/v2/the-basics/forms.mdx
@@ -1320,7 +1320,7 @@ Unlike an actual form submission, the page's props remain unchanged when manuall
 
 When a form has been successfully submitted, the `wasSuccessful` property will be `true`. In addition to this, forms have a `recentlySuccessful` property, which will be set to `true` for two seconds after a successful form submission. This property can be utilized to show temporary success messages.
 
-You may customize the duration of the `recentlySuccessful` state by setting the `form.recentlySuccessfulDuration` option in your [application defaults](/client-side-setup#configuring-defaults). The default value is `2000` milliseconds.
+You may customize the duration of the `recentlySuccessful` state by setting the `form.recentlySuccessfulDuration` option in your [application defaults](/v2/installation/client-side-setup#configuring-defaults). The default value is `2000` milliseconds.
 
 ### Resetting the Form
 
diff --git a/v2/the-basics/manual-visits.mdx b/v2/the-basics/manual-visits.mdx
@@ -365,7 +365,7 @@ The headers Inertia uses internally to communicate its state to the server take
 
 ## Global Visit Options
 
-You may configure a `visitOptions` callback when [initializing your Inertia app](/client-side-setup#configuring-defaults) to modify visit options globally for every request. The callback receives the target URL and the current visit options, and should return an object with any options you want to override.
+You may configure a `visitOptions` callback when [initializing your Inertia app](/v2/installation/client-side-setup#configuring-defaults) to modify visit options globally for every request. The callback receives the target URL and the current visit options, and should return an object with any options you want to override.
 
 <CodeGroup>
 
@@ -761,7 +761,7 @@ router.post('/users', data, {
 
 ## Scroll Preservation
 
-When navigating between pages, Inertia mimics default browser behavior by automatically resetting the scroll position of the document body (as well as any [scroll regions](/scroll-management#scroll-regions) you've defined) back to the top of the page.
+When navigating between pages, Inertia mimics default browser behavior by automatically resetting the scroll position of the document body (as well as any [scroll regions](/v2/advanced/scroll-management#scroll-regions) you've defined) back to the top of the page.
 
 You can disable this behavior by setting the `preserveScroll` option to `true`.
 
diff --git a/v2/the-basics/routing.mdx b/v2/the-basics/routing.mdx
@@ -63,7 +63,7 @@ When [server-side rendering](/v2/advanced/server-side-rendering) is enabled, you
 
 ## Customizing the Page URL
 
-The [page object](/the-protocol#the-page-object) includes a `url` that represents the current page's URL. By default, the Laravel adapter resolves this using the `fullUrl()` method on the `Request` instance, but strips the scheme and host so the result is a relative URL.
+The [page object](/v2/core-concepts/the-protocol#the-page-object) includes a `url` that represents the current page's URL. By default, the Laravel adapter resolves this using the `fullUrl()` method on the `Request` instance, but strips the scheme and host so the result is a relative URL.
 
 If you need to customize how the URL is resolved, you may provide a resolver within the `urlResolver`method of the Inertia `HandleInertiaRequests` middleware.
 
diff --git a/v2/the-basics/title-and-meta.mdx b/v2/the-basics/title-and-meta.mdx
@@ -267,7 +267,7 @@ import AppHead from './AppHead'
 
 Inertia has historically used the `inertia` attribute to track and manage elements in the document `<head>`. However, you can now opt-in to using the more standards-compliant `data-inertia` attribute instead. According to the HTML specification, custom attributes should be prefixed with `data-` to avoid conflicts with future HTML standards.
 
-To enable this, configure the `future.useDataInertiaHeadAttribute` option in your [application defaults](/client-side-setup#configuring-defaults).
+To enable this, configure the `future.useDataInertiaHeadAttribute` option in your [application defaults](/v2/installation/client-side-setup#configuring-defaults).
 
 ```js
 createInertiaApp({
diff --git a/v2/the-basics/validation.mdx b/v2/the-basics/validation.mdx
diff --git a/v2/the-basics/view-transitions.mdx b/v2/the-basics/view-transitions.mdx

Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,3 @@`
`1`		`-import { useCallback, useEffect, useState } from "react";`
`2`		`-`
`3`	`1`	`export const ReactSpecific = ({ children }) => {`
`4`	`2`	`const [code, setCode] = useState(`
`5`	`3`	`localStorage.getItem("code")?.replace(/"/g, "") \|\| null,`
Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,3 @@`
`1`		`-import { useCallback, useEffect, useState } from "react";`
`2`		`-`
`3`	`1`	`export const SvelteSpecific = ({ children }) => {`
`4`	`2`	`const [code, setCode] = useState(`
`5`	`3`	`localStorage.getItem("code")?.replace(/"/g, "") \|\| null,`
Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,3 @@`
`1`		`-import { useCallback, useEffect, useState } from "react";`
`2`		`-`
`3`	`1`	`export const Svelte4Specific = ({ children }) => {`
`4`	`2`	`const [code, setCode] = useState(`
`5`	`3`	`localStorage.getItem("code")?.replace(/"/g, "") \|\| null,`
Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,3 @@`
`1`		`-import { useCallback, useEffect, useState } from "react";`
`2`		`-`
`3`	`1`	`export const Svelte5Specific = ({ children }) => {`
`4`	`2`	`const [code, setCode] = useState(`
`5`	`3`	`localStorage.getItem("code")?.replace(/"/g, "") \|\| null,`
Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,3 @@`
`1`		`-import { useCallback, useEffect, useState } from "react";`
`2`		`-`
`3`	`1`	`export const VueSpecific = ({ children }) => {`
`4`	`2`	`const [code, setCode] = useState(`
`5`	`3`	`localStorage.getItem("code")?.replace(/"/g, "") \|\| null,`
Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,3 @@`
`1`		`-import { useCallback, useEffect, useState } from "react";`
`2`		`-`
`3`	`1`	`export const Vue2Specific = ({ children }) => {`
`4`	`2`	`const [code, setCode] = useState(`
`5`	`3`	`localStorage.getItem("code")?.replace(/"/g, "") \|\| null,`
Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,3 @@`
`1`		`-import { useCallback, useEffect, useState } from "react";`
`2`		`-`
`3`	`1`	`export const Vue3Specific = ({ children }) => {`
`4`	`2`	`const [code, setCode] = useState(`
`5`	`3`	`localStorage.getItem("code")?.replace(/"/g, "") \|\| null,`