[C3] Consistently use full official full stack framework names

Instead of using shortened names for the various full stack frameworks
use their full official names

Author: dario-piotrowicz

public/_redirects

@@ -829,6 +829,8 @@
 /pages/how-to/deploy-a-vue-application/ /pages/framework-guides/deploy-a-vue-site/ 301
 /pages/functions/plugins/mailchannels/ /workers/tutorials/send-emails-with-resend/ 301
 /pages/framework-guides/deploy-a-vue-application/ /pages/framework-guides/deploy-a-vue-site 301
+/pages/framework-guides/deploy-a-solid-site/ /pages/framework-guides/deploy-a-solid-start-site/ 301
+/pages/framework-guides//pages/framework-guides/deploy-a-svelte-site/ /pages/framework-guides/deploy-a-svelte-kit-site/ 301
 /pages/how-to/deploy-a-zola-site/ /pages/framework-guides/deploy-a-zola-site/ 301
 /pages/how-to/elderjs/ /pages/framework-guides/deploy-an-elderjs-site/ 301
 /pages/configuration/language-support-and-tools/ /pages/configuration/build-image/ 301

src/content/docs/pages/framework-guides/deploy-a-solid-site.mdx renamed to src/content/docs/pages/framework-guides/deploy-a-solid-start-site.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: how-to
-title: Solid
+title: SolidStart
 ---
 
 import { Render, PackageManagers } from "~/components";

src/content/docs/pages/framework-guides/deploy-a-svelte-site.mdx renamed to src/content/docs/pages/framework-guides/deploy-a-svelte-kit-site.mdx

@@ -1,7 +1,6 @@
 ---
 pcx_content_type: how-to
 title: SvelteKit
-description: Learn how to use Cloudflare's features with SvelteKit
 ---
 
 import { PagesBuildPreset, Render, PackageManagers } from "~/components";

src/content/docs/pages/get-started/c3.mdx

@@ -10,7 +10,14 @@ description: Use C3 (`create-cloudflare` CLI) to set up and deploy new
   deployment.
 ---
 
-import { Render, TabItem, Tabs, Type, MetaInfo, PackageManagers } from "~/components";
+import {
+	Render,
+	TabItem,
+	Tabs,
+	Type,
+	MetaInfo,
+	PackageManagers,
+} from "~/components";
 
 Cloudflare provides a CLI command for creating new Workers and Pages projects — `npm create cloudflare`, powered by the [`create-cloudflare` package](https://www.npmjs.com/package/create-cloudflare).
 
@@ -37,8 +44,8 @@ If you choose the "Framework Starter" option, you will be prompted to choose a f
 - [Qwik](/pages/framework-guides/deploy-a-qwik-site/)
 - [React](/pages/framework-guides/deploy-a-react-site/)
 - [Remix](/pages/framework-guides/deploy-a-remix-site/)
-- [Solid](/pages/framework-guides/deploy-a-solid-site/)
-- [Svelte](/pages/framework-guides/deploy-a-svelte-site/)
+- [SolidStart](/pages/framework-guides/deploy-a-solid-start-site/)
+- [SvelteKit](/pages/framework-guides/deploy-a-svelte-kit-site/)
 - [Vue](/pages/framework-guides/deploy-a-vue-site/)
 
 When you use a framework, `npm create cloudflare` directly uses the framework's own command for generating a new projects, which may prompt additional questions. This ensures that the project you create is up-to-date with the latest version of the framework, and you have all the same options when creating you project via `npm create cloudflare` that you would if you created your project using the framework's tooling directly.
@@ -229,7 +236,7 @@ Cloudflare collects anonymous usage data to improve `create-cloudflare` over tim
 You can opt-out if you do not wish to share any information.
 
 <PackageManagers
-  type="create"
+	type="create"
 	pkg="cloudflare@latest"
 	args="telemetry disable"
 />
@@ -243,15 +250,15 @@ export CREATE_CLOUDFLARE_TELEMETRY_DISABLED=1
 You can check the status of telemetry collection at any time.
 
 <PackageManagers
-  type="create"
-  pkg="cloudflare@latest"
-  args="telemetry status"
+	type="create"
+	pkg="cloudflare@latest"
+	args="telemetry status"
 />
 
 You can always re-enable telemetry collection.
 
 <PackageManagers
-  type="create"
-  pkg="cloudflare@latest"
-  args="telemetry enable"
+	type="create"
+	pkg="cloudflare@latest"
+	args="telemetry enable"
 />