docs: move /docs/components docs/core 📦 (#7958)

Author: gioboa

e2e/docs-e2e/tests/Docs/docs-components-pages-load.spec.ts

@@ -1,37 +1,37 @@
 import { test, expect } from '@playwright/test';
 
 test('Components Overview page loads', async ({ page }) => {
-  await page.goto('/docs/components/overview/');
+  await page.goto('/docs/core/overview/');
   await expect(page).toHaveTitle('Overview | Components 📚 Qwik Documentation');
 });
 
 test('Components State page loads', async ({ page }) => {
-  await page.goto('/docs/components/state/');
+  await page.goto('/docs/core/state/');
   await expect(page).toHaveTitle('State | Components 📚 Qwik Documentation');
 });
 
 test('Components Tasks and Lifecycle page loads', async ({ page }) => {
-  await page.goto('/docs/components/tasks/');
+  await page.goto('/docs/core/tasks/');
   await expect(page).toHaveTitle('Tasks and Lifecycle | Components 📚 Qwik Documentation');
 });
 
 test('Components Context page loads', async ({ page }) => {
-  await page.goto('/docs/components/context/');
+  await page.goto('/docs/core/context/');
   await expect(page).toHaveTitle('Context | Components 📚 Qwik Documentation');
 });
 
 test('Components Slots page loads', async ({ page }) => {
-  await page.goto('/docs/components/slots/');
+  await page.goto('/docs/core/slots/');
   await expect(page).toHaveTitle('Slots | Components 📚 Qwik Documentation');
 });
 
 test('Components Rendering page loads', async ({ page }) => {
-  await page.goto('/docs/components/rendering/');
+  await page.goto('/docs/core/rendering/');
   await expect(page).toHaveTitle('Rendering | Components 📚 Qwik Documentation');
 });
 
 test('Components Styles page loads', async ({ page }) => {
-  await page.goto('/docs/components/styles/');
+  await page.goto('/docs/core/styles/');
   await expect(page).toHaveTitle('Styles | Components 📚 Qwik Documentation');
 });
 

packages/docs/public/_redirects

@@ -57,15 +57,16 @@
 /docs/cheat/qwik-react/ /docs/integrations/react/ 308
 /docs/cheat/best-practices/ /docs/guides/best-practices/ 308
 /docs/cheat/serialization/ /docs/guides/serialization/ 308
-/docs/components/lifecycle/ /docs/components/tasks/ 308
-/docs/components/projection/ /docs/components/slots/ 308
-/docs/components/resource/ /docs/components/state/ 308
+/docs/components/lifecycle/ /docs/core/tasks/ 308
+/docs/components/projection/ /docs/core/slots/ 308
+/docs/components/resource/ /docs/core/state/ 308
 /docs/cookbook/re-exporting-loaders/ /docs/re-exporting-loaders/ 308
 
 /qwikcity/* /docs/:splat 308
 /integrations/* /docs/integrations/:splat 308
 /deployments/* /docs/deployments/:splat 308
 /docs/advanced/i18n/ /docs/integrations/i18n/ 308
-/docs/components/inline-components/ /docs/components/overview/ 308
+/docs/components/inline-components/ /docs/core/overview/ 308
 /docs/think-qwik/ /docs/concepts/think-qwik/ 308
 /docs/env-variables/ /docs/guides/env-variables/ 308
+/docs/components/ /docs/core/ 308

packages/docs/public/_routes.json

@@ -12,9 +12,9 @@
     "/docs/cheat/qwik-react/",
     "/docs/cheat/best-practices/",
     "/docs/cheat/serialization/",
-    "/docs/components/lifecycle/",
-    "/docs/components/projection/",
-    "/docs/components/resource/",
+    "/docs/core/lifecycle/",
+    "/docs/core/projection/",
+    "/docs/core/resource/",
     "/qwikcity/*",
     "/integrations/*",
     "/deployments/*",

packages/docs/public/builder/qwik-0.100.0.js

@@ -85,7 +85,7 @@ The output HTML looks like this:
 
 Right away, you might notice that Qwik needs to create “virtual nodes” in the form of comments. So why does Qwik need this information?
 
-- `<!--qv q:s q:sref=5 q:key=-->`: In this example, a parent [Layout](https://qwik.dev/docs/layout/) component (not shown) is used for routing. The parent component creates the `<main/>` element and [projects the route content](https://qwik.dev/docs/components/slots/#slots) (Counter) into the layout component. So, the framework needs to know where the component projected output should be inserted. Qwik needs a virtual node for that.
+- `<!--qv q:s q:sref=5 q:key=-->`: In this example, a parent [Layout](https://qwik.dev/docs/layout/) component (not shown) is used for routing. The parent component creates the `<main/>` element and [projects the route content](https://qwik.dev/docs/core/slots/#slots) (Counter) into the layout component. So, the framework needs to know where the component projected output should be inserted. Qwik needs a virtual node for that.
 - `<!--qv q:id=7 q:key=xYL1:zl_0-->`: This virtual node represents the Counter component. The component requires component props, which are stored in the data section (`<script type="qwik/json">`). The additional attributes are used to cross-reference the props with this virtual node. A key point of resumability is that one should be able to re-render a component without the parent component needing to be resumed as well. But components get props from the parent, so the props need to be serialized and recoverable so that this component can render independently of others. Qwik needs a virtual node for that.
 - `<!--qv q:key=H1_0-->`: The Counter component JSX has a top-level Fragment represented by `<>...</>`. Qwik needs a virtual node for that.
 - `<!--t=8-->123<!---->`: When the counter updates, Qwik needs to be able to update the text node associated with the signal. HTML merges neighboring text nodes, and there is no easy way to refer to text nodes. So Qwik needs a virtual node for that.

packages/docs/src/routes/(blog)/blog/(articles)/qwik-2-coming-soon/index.mdx

@@ -73,7 +73,7 @@ In the context of Qwik City, the problem becomes a little bit more complicated t
 
 Qwik's Data Loader solves the issue of quickly fetching data to be displayed in the HTML. It helps to ensure that the data is available in a timely manner. This helps to improve the user experience and reduce loading times.
 
-Qwik City goes a long way to execute all relevant loaders as soon as possible and in parallel to keep latency as low as possible, in addition, loaders are connected to the reactivity system of Qwik powered by [signals](https://qwik.dev/docs/components/state/#usesignal), so new data will automatically and efficiently update all parts of the app that depend on it.
+Qwik City goes a long way to execute all relevant loaders as soon as possible and in parallel to keep latency as low as possible, in addition, loaders are connected to the reactivity system of Qwik powered by [signals](https://qwik.dev/docs/core/state/#usesignal), so new data will automatically and efficiently update all parts of the app that depend on it.
 
 ```tsx
 import { loader$ } from '@builder.io/qwik-city';

packages/docs/src/routes/(blog)/blog/(articles)/qwik-city-server-functions/index.mdx

@@ -35,7 +35,7 @@ The JavaScript that's sent is extremely minimal — bite-size amounts of code ge
 
 ## Using visible tasks in Qwik
 
-With Qwik, this takes no extra work. All we need is this [useVisibleTask$](https://qwik.dev/docs/components/tasks/#usevisibletask) hook.
+With Qwik, this takes no extra work. All we need is this [useVisibleTask$](https://qwik.dev/docs/core/tasks/#usevisibletask) hook.
 
 ```jsx
 import { component$, useSignal, useVisibleTask$ } from "@builder.io/qwik";

packages/docs/src/routes/(blog)/blog/(articles)/qwik-tasks/index.mdx

@@ -263,7 +263,7 @@ This is the result:
 
 What we’ve done is create a simple counter component inside a [QwikCity](https://qwik.dev/qwikcity/overview/) project, which is the meta-framework for Qwik. Basically, it’s like SvelteKit for Svelte, or [SolidStart](https://start.solidjs.com/getting-started/what-is-solidstart) for Solid. It is generally in charge of routing and the build.
 
-If you're coming from React (or Solid), you can see that a lot of the above looks familiar. As Qwik uses JSX, you should feel right at home. A [signal](https://qwik.dev/docs/components/state/#usesignal) is a reactive piece of state, similar to [Solid.js signals](https://www.solidjs.com/tutorial/introduction_signals), which consists of an object with a single property (`signal.value`) that when changed will update any component that uses it. Similarly, `useStore` is almost the same as a signal but accepts an object as a parameter, that then becomes reactive.
+If you're coming from React (or Solid), you can see that a lot of the above looks familiar. As Qwik uses JSX, you should feel right at home. A [signal](https://qwik.dev/docs/core/state/#usesignal) is a reactive piece of state, similar to [Solid.js signals](https://www.solidjs.com/tutorial/introduction_signals), which consists of an object with a single property (`signal.value`) that when changed will update any component that uses it. Similarly, `useStore` is almost the same as a signal but accepts an object as a parameter, that then becomes reactive.
 
 The second thing to notice is the `$` sign after `component$` and `onClick$`, which is [a symbol in Qwik.](https://qwik.dev/docs/advanced/dollar/) These are hints for the optimizer to break our code into pieces that can later be loaded intelligently. It’s important to note that only serializable data can be used in a lazy-loaded boundary.
 

packages/docs/src/routes/(blog)/blog/(articles)/the-qase-for-qwik-love-at-first-tti/index.mdx

@@ -108,7 +108,7 @@ Limitations of JSON that Qwik does not solve:
   - Although some built-in classes, such as [Date](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date), [URL](https://developer.mozilla.org/en-US/docs/Web/API/URL), [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map), [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set) are supported.
 - Serialization of Streams.
 
-For cases where serialization is not possible, code should run [on client only](https://qwik.dev/docs/components/lifecycle/#serverbrowser-only-task).
+For cases where serialization is not possible, code should run [on client only](https://qwik.dev/docs/core/lifecycle/#serverbrowser-only-task).
 
 ### Writing applications with serializability in mind