From 3124366f73f2300452b157ac58f034bca2809707 Mon Sep 17 00:00:00 2001 From: Thomas Date: Sat, 6 Sep 2025 08:57:28 +0200 Subject: [PATCH 1/6] Revise route pre-rendering section in documentation --- .../route-prerendering.mdx | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/src/routes/solid-start/building-your-application/route-prerendering.mdx b/src/routes/solid-start/building-your-application/route-prerendering.mdx index 34461ea25..9fb7d2f29 100644 --- a/src/routes/solid-start/building-your-application/route-prerendering.mdx +++ b/src/routes/solid-start/building-your-application/route-prerendering.mdx @@ -1,9 +1,10 @@ --- -title: "Route pre-rendering" +title: "Route Pre-rendering" --- -SolidStart offers a way to pre-render pages at build time. -The easiest way to accomplish this is by passing a list of routes to be pre-rendered to the `routes` option. +Route pre-rendering enables Static Site Generation (SSG) by creating static HTML pages at build time. This delivers faster page loads and improves SEO, making it ideal for content-heavy sites like documentation, blogs, or marketing pages. Static files are served without server-side processing at runtime. + +To pre-render specific routes, specify the routes option in your configuration file ```js { 6 } import { defineConfig } from "@solidjs/start/config"; @@ -17,7 +18,7 @@ export default defineConfig({ }); ``` -When you wish for all your routes to be pre-rendered, you can pass `true` to the `crawlLinks` option: +Or to automatically pre-render all routes, enable the `crawlLinks` option ```js { 6 } import { defineConfig } from "@solidjs/start/config"; @@ -31,4 +32,6 @@ export default defineConfig({ }); ``` -For more information on prerender options, check out [Nitro's documentation](https://nitro.build/config#prerender) +For advanced pre-rendering options, refer to [Nitro's documentation](https://nitro.build/config#prerender). + +[SolidBase](https://solidbase.dev) simplifies SSG development with built-in support for fast, pre-rendered Markdown and MDX pages. From 542d56f97dae6f955c768582408d987c4feae579 Mon Sep 17 00:00:00 2001 From: Thomas Date: Sat, 6 Sep 2025 09:11:54 +0200 Subject: [PATCH 2/6] Update phrasing for crawlLinks option explanation --- .../building-your-application/route-prerendering.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/routes/solid-start/building-your-application/route-prerendering.mdx b/src/routes/solid-start/building-your-application/route-prerendering.mdx index 9fb7d2f29..b181ed2a9 100644 --- a/src/routes/solid-start/building-your-application/route-prerendering.mdx +++ b/src/routes/solid-start/building-your-application/route-prerendering.mdx @@ -18,7 +18,7 @@ export default defineConfig({ }); ``` -Or to automatically pre-render all routes, enable the `crawlLinks` option +Or to pre-render all routes, you can pass `true` to the `crawlLinks` option ```js { 6 } import { defineConfig } from "@solidjs/start/config"; From 0de64a583a6b4ada032530c7c9ceff73223651f3 Mon Sep 17 00:00:00 2001 From: Thomas Date: Sat, 6 Sep 2025 09:32:54 +0200 Subject: [PATCH 3/6] Clarify prerendering configuration instructions --- .../building-your-application/route-prerendering.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/routes/solid-start/building-your-application/route-prerendering.mdx b/src/routes/solid-start/building-your-application/route-prerendering.mdx index b181ed2a9..c4d04638a 100644 --- a/src/routes/solid-start/building-your-application/route-prerendering.mdx +++ b/src/routes/solid-start/building-your-application/route-prerendering.mdx @@ -4,7 +4,7 @@ title: "Route Pre-rendering" Route pre-rendering enables Static Site Generation (SSG) by creating static HTML pages at build time. This delivers faster page loads and improves SEO, making it ideal for content-heavy sites like documentation, blogs, or marketing pages. Static files are served without server-side processing at runtime. -To pre-render specific routes, specify the routes option in your configuration file +Configure prerendering for specific routes using the `routes` option ```js { 6 } import { defineConfig } from "@solidjs/start/config"; From 8f1a9d45c4f0501feec98cd515397344d1c48583 Mon Sep 17 00:00:00 2001 From: Thomas Date: Sat, 6 Sep 2025 11:40:11 +0200 Subject: [PATCH 4/6] Enhance description of state management stores Revised explanation of stores for clarity and detail. --- src/routes/concepts/stores.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/routes/concepts/stores.mdx b/src/routes/concepts/stores.mdx index 748ada6ae..edc7121df 100644 --- a/src/routes/concepts/stores.mdx +++ b/src/routes/concepts/stores.mdx @@ -3,9 +3,7 @@ title: Stores order: 6 --- -Similar to [signals](/concepts/signals), stores are a state management primitive. -However, while signals manage a single piece of state, stores create a centralized location to reduce code redundancy. -Within Solid, these stores can spawn a collection of reactive signals, each corresponding to a particular property which can be useful when working with complex state. +Stores are a state management primitive that provide a centralized location to reduce code redundancy. Unlike [signals](/concepts/signals), which manage a single piece of state and re-render entirely when updated, stores retain fine-grained reactivity by updating only the specific properties that change. They can generate a collection of reactive signals, each tied to a specific property, making them ideal for managing complex state efficiently. ## Creating a store From ce2fe93897b01dfbc578d6a71f8585121b5c0634 Mon Sep 17 00:00:00 2001 From: Thomas Date: Sun, 7 Sep 2025 07:19:18 +0200 Subject: [PATCH 5/6] Update src/routes/concepts/stores.mdx Co-authored-by: Sarah --- src/routes/concepts/stores.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/routes/concepts/stores.mdx b/src/routes/concepts/stores.mdx index edc7121df..14041cf1e 100644 --- a/src/routes/concepts/stores.mdx +++ b/src/routes/concepts/stores.mdx @@ -3,7 +3,9 @@ title: Stores order: 6 --- -Stores are a state management primitive that provide a centralized location to reduce code redundancy. Unlike [signals](/concepts/signals), which manage a single piece of state and re-render entirely when updated, stores retain fine-grained reactivity by updating only the specific properties that change. They can generate a collection of reactive signals, each tied to a specific property, making them ideal for managing complex state efficiently. +Stores are a state management primitive that provide a centralized way to handle shared data and reduce redundancy. +Unlike [signals](/concepts/signals), which track a single value and trigger a full re-render when updated, stores maintain fine-grained reactivity by updating only the properties that change. +They can produce a collection of reactive signals, each linked to an individual property, making them well-suited for managing complex state efficiently. ## Creating a store From 6b058334988211f749856f97a47a264e52387f2d Mon Sep 17 00:00:00 2001 From: Thomas Date: Sun, 7 Sep 2025 07:19:28 +0200 Subject: [PATCH 6/6] Update src/routes/solid-start/building-your-application/route-prerendering.mdx Co-authored-by: Sarah --- .../building-your-application/route-prerendering.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/routes/solid-start/building-your-application/route-prerendering.mdx b/src/routes/solid-start/building-your-application/route-prerendering.mdx index c4d04638a..9a17813eb 100644 --- a/src/routes/solid-start/building-your-application/route-prerendering.mdx +++ b/src/routes/solid-start/building-your-application/route-prerendering.mdx @@ -2,7 +2,9 @@ title: "Route Pre-rendering" --- -Route pre-rendering enables Static Site Generation (SSG) by creating static HTML pages at build time. This delivers faster page loads and improves SEO, making it ideal for content-heavy sites like documentation, blogs, or marketing pages. Static files are served without server-side processing at runtime. +Route pre-rendering powers Static Site Generation (SSG) by producing static HTML pages during the build process. +This results in faster load times and better SEO, making it especially useful for content-rich sites such as documentation, blogs, and marketing pages. +Static files are served without server-side processing at runtime. Configure prerendering for specific routes using the `routes` option