diff --git a/src/routes/(0)concepts/(4)context.mdx b/src/routes/(0)concepts/(4)context.mdx index db22290201..7a0452809d 100644 --- a/src/routes/(0)concepts/(4)context.mdx +++ b/src/routes/(0)concepts/(4)context.mdx @@ -67,7 +67,7 @@ const Provider = (props) => ( ``` :::tip[Complex Types] -When passing multiple values (as an `array` or `object`), it is recommended to use a [store](/reference/component-apis/create-context#usage). +When passing multiple values (as an `array` or `object`), it is recommended to use a [store](/concepts/stores). ::: ## Consuming context diff --git a/src/routes/(2)guides/(1)deployment-options/zerops.mdx b/src/routes/(2)guides/(1)deployment-options/zerops.mdx index 6bb2371145..1c00ae9cda 100644 --- a/src/routes/(2)guides/(1)deployment-options/zerops.mdx +++ b/src/routes/(2)guides/(1)deployment-options/zerops.mdx @@ -139,7 +139,7 @@ Push the changes to your GitHub/GitLab repository (necessary if you are planning ### Triggering the pipeline automatically by connecting Github/Gitlab repository -You can push your project by [Triggering the pipeline using Zerops CLI](#triggering-the-pipeline-using-githubgitlab) or by connecting the app service with your [GitHub](https://docs.zerops.io/references/github-integration/) / [GitLab](https://docs.zerops.io/references/gitlab-integration) repository from inside the service detail. +You can push your project by [Triggering the pipeline using Zerops CLI](#triggering-the-pipeline-manually-using-zerops-cli) or by connecting the app service with your [GitHub](https://docs.zerops.io/references/github-integration/) / [GitLab](https://docs.zerops.io/references/gitlab-integration) repository from inside the service detail. ### Triggering the pipeline manually using Zerops CLI diff --git a/src/routes/reference/jsx-attributes/classlist.mdx b/src/routes/reference/jsx-attributes/classlist.mdx index 39367bc276..6f8ecc5f4a 100644 --- a/src/routes/reference/jsx-attributes/classlist.mdx +++ b/src/routes/reference/jsx-attributes/classlist.mdx @@ -63,4 +63,4 @@ Object whose keys are class names and whose values control whether each class is ## Related -- [`class`](/reference/jsx-attributes/class) +- [`class`](/concepts/components/class-style) diff --git a/src/routes/solid-router/(1)concepts/(0)navigation.mdx b/src/routes/solid-router/(1)concepts/(0)navigation.mdx index 82a21ae3c4..c3c7610069 100644 --- a/src/routes/solid-router/(1)concepts/(0)navigation.mdx +++ b/src/routes/solid-router/(1)concepts/(0)navigation.mdx @@ -15,7 +15,7 @@ description: >- redirects for seamless user experiences. --- -When using Solid Router, you can use the standard standard HTML [`` elements](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a), which triggers [soft navigation](/solid-router/reference/components/a#soft-navigation). +When using Solid Router, you can use the standard HTML [`` elements](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a), which triggers [soft navigation](/solid-router/reference/components/a). In addition to using this, Solid Router offers other options for navigating between routes: - The [`` component](/solid-router/reference/components/a). diff --git a/src/routes/solid-router/(3)data-fetching/(0)queries.mdx b/src/routes/solid-router/(3)data-fetching/(0)queries.mdx index 0f43335a6a..9aa87564b2 100644 --- a/src/routes/solid-router/(3)data-fetching/(0)queries.mdx +++ b/src/routes/solid-router/(3)data-fetching/(0)queries.mdx @@ -8,7 +8,7 @@ They provide an elegant solution for managing data fetching. ## Defining queries They are defined using the [`query` function](/solid-router/reference/data-apis/query). -It wraps the data-fetching logic and extends it with powerful capabilities like [request deduplication](#deduplication) and [automatic revalidation](#revalidation). +It wraps the data-fetching logic and extends it with powerful capabilities like [request deduplication](#deduplication) and [automatic revalidation](/solid-router/concepts/actions#automatic-data-revalidation). The `query` function takes two parameters: a **fetcher** and a **name**. diff --git a/src/routes/solid-router/(3)data-fetching/how-to/(0)preload-data.mdx b/src/routes/solid-router/(3)data-fetching/how-to/(0)preload-data.mdx index 39215abe63..ca67e743dd 100644 --- a/src/routes/solid-router/(3)data-fetching/how-to/(0)preload-data.mdx +++ b/src/routes/solid-router/(3)data-fetching/how-to/(0)preload-data.mdx @@ -15,7 +15,7 @@ Preloading is configured using the [`preload`](/solid-router/reference/preload-f This prop accepts a function that calls one or more queries. When triggered, the queries execute and their results are stored in a short-lived internal cache. Once the user navigates and the destination route’s component renders, any `createAsync` calls within the page will consume the preloaded data. -Thanks to the [deduplication mechanism](#deduplication), no redundant network requests are made. +Thanks to the [deduplication mechanism](/solid-router/data-fetching/queries#deduplication), no redundant network requests are made. ```tsx {18-20,27} import { Show } from "solid-js"; diff --git a/src/routes/solid-router/(4)advanced-concepts/(0)preloading.mdx b/src/routes/solid-router/(4)advanced-concepts/(0)preloading.mdx index 73b9492878..3ccb1f123f 100644 --- a/src/routes/solid-router/(4)advanced-concepts/(0)preloading.mdx +++ b/src/routes/solid-router/(4)advanced-concepts/(0)preloading.mdx @@ -41,4 +41,4 @@ Calling both the route preload and the nested component preload can keep large d Balancing manual preloading requires observing real user flows so you avoid prefetching large bundles that the user never requests. Profiling tools help you spot whether preloading reduces long tasks or simply shifts work earlier without net gains. -To learn more about lazy loading components, see the [lazy documentation](/reference/component-apis/lazy#preloading-data-in-nested-lazy-components). +To learn more about lazy loading components, see the [lazy documentation](/reference/component-apis/lazy#preloading-nested-lazy-components). diff --git a/src/routes/solid-start/v1/(2)guides/(2)data-mutation.mdx b/src/routes/solid-start/v1/(2)guides/(2)data-mutation.mdx index 5a9406e27b..bb63db505e 100644 --- a/src/routes/solid-start/v1/(2)guides/(2)data-mutation.mdx +++ b/src/routes/solid-start/v1/(2)guides/(2)data-mutation.mdx @@ -24,7 +24,7 @@ This guide provides practical examples of using actions to mutate data in SolidS To handle [`
`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/form) submissions with an action: 1. Ensure the action has a unique name. - See the [Action API reference](/solid-router/reference/data-apis/action#notes-of-form-implementation-and-ssr) for more information. + See the [Action API reference](/solid-router/reference/data-apis/action) for more information. 2. Pass the action to the `` element using the `action` prop. 3. Ensure the `` element uses the `post` method for submission. 4. Use the [`FormData`](https://developer.mozilla.org/en-US/docs/Web/API/FormData/FormData) object in the action to extract field data using the native `FormData` methods. diff --git a/src/routes/solid-start/v2/(2)guides/(0)security.mdx b/src/routes/solid-start/v2/(2)guides/(0)security.mdx index 88feed732d..e3ca2eaa35 100644 --- a/src/routes/solid-start/v2/(2)guides/(0)security.mdx +++ b/src/routes/solid-start/v2/(2)guides/(0)security.mdx @@ -46,7 +46,7 @@ If you want to use a [strict CSP](https://developer.mozilla.org/en-US/docs/Web/H 1. Create middleware that generates a nonce and configures the CSP header before calling `next()`. 2. Create a nonce using a cryptographic random value generator, such as the [`randomBytes`](https://nodejs.org/api/crypto.html#cryptorandombytessize-callback) function from the `crypto` module. -3. Store the nonce in the [`locals`](/solid-start/v2/advanced/middleware#locals) object. +3. Store the nonce in the [`locals`](/solid-start/v2/advanced/middleware#request-scoped-locals) object. 4. Configure SolidStart to use the nonce in your [`entry-server.tsx`](/solid-start/v2/reference/entrypoints/entry-server) file. ```tsx tab title="Middleware" diff --git a/src/routes/solid-start/v2/(2)guides/(2)data-mutation.mdx b/src/routes/solid-start/v2/(2)guides/(2)data-mutation.mdx index ba213e3b18..ddb80bfc80 100644 --- a/src/routes/solid-start/v2/(2)guides/(2)data-mutation.mdx +++ b/src/routes/solid-start/v2/(2)guides/(2)data-mutation.mdx @@ -24,7 +24,7 @@ This guide provides practical examples of using actions to mutate data in SolidS To handle [``](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/form) submissions with an action: 1. Ensure the action has a unique name. - See the [Action API reference](/solid-router/reference/data-apis/action#notes-of-form-implementation-and-ssr) for more information. + See the [Action API reference](/solid-router/reference/data-apis/action) for more information. 2. Pass the action to the `` element using the `action` prop. 3. Ensure the `` element uses the `post` method for submission. 4. Use the [`FormData`](https://developer.mozilla.org/en-US/docs/Web/API/FormData/FormData) object in the action to extract field data using the native `FormData` methods.