From 7c44afaf63cf5e4a523a769ac8348ad6d304973b Mon Sep 17 00:00:00 2001 From: Daniel Date: Thu, 4 Dec 2025 08:43:13 -0300 Subject: [PATCH] feat: add django as a supported server-side adapter in the introduction --- v2/getting-started/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v2/getting-started/index.mdx b/v2/getting-started/index.mdx index 4a3bf8a..46adb13 100644 --- a/v2/getting-started/index.mdx +++ b/v2/getting-started/index.mdx @@ -10,7 +10,7 @@ Inertia has no client-side routing, nor does it require an API. Simply build con ## Not a Framework -Inertia isn't a framework, nor is it a replacement for your existing server-side or client-side frameworks. Rather, it's designed to work with them. Think of Inertia as glue that connects the two. Inertia does this via adapters. We currently have three official client-side adapters (React, Vue, and Svelte) and three server-side adapters (Laravel, Rails, and Phoenix). +Inertia isn't a framework, nor is it a replacement for your existing server-side or client-side frameworks. Rather, it's designed to work with them. Think of Inertia as glue that connects the two. Inertia does this via adapters. We currently have three official client-side adapters (React, Vue, and Svelte) and four server-side adapters (Laravel, Rails, Phoenix, and Django). ## Next Steps