Skip to content

Commit 79af1ae

Browse files
Closes issues #649 and #968 (#1251)
Co-authored-by: Sarah <hello@sarahgerrard.me>
1 parent 428b84d commit 79af1ae

File tree

2 files changed

+13
-8
lines changed

2 files changed

+13
-8
lines changed

src/routes/concepts/stores.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,9 @@ title: Stores
33
order: 6
44
---
55

6-
Similar to [signals](/concepts/signals), stores are a state management primitive.
7-
However, while signals manage a single piece of state, stores create a centralized location to reduce code redundancy.
8-
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.
6+
Stores are a state management primitive that provide a centralized way to handle shared data and reduce redundancy.
7+
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.
8+
They can produce a collection of reactive signals, each linked to an individual property, making them well-suited for managing complex state efficiently.
99

1010
## Creating a store
1111

src/routes/solid-start/building-your-application/route-prerendering.mdx

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,12 @@
11
---
2-
title: "Route pre-rendering"
2+
title: "Route Pre-rendering"
33
---
44

5-
SolidStart offers a way to pre-render pages at build time.
6-
The easiest way to accomplish this is by passing a list of routes to be pre-rendered to the `routes` option.
5+
Route pre-rendering powers Static Site Generation (SSG) by producing static HTML pages during the build process.
6+
This results in faster load times and better SEO, making it especially useful for content-rich sites such as documentation, blogs, and marketing pages.
7+
Static files are served without server-side processing at runtime.
8+
9+
Configure prerendering for specific routes using the `routes` option
710

811
```js { 6 }
912
import { defineConfig } from "@solidjs/start/config";
@@ -17,7 +20,7 @@ export default defineConfig({
1720
});
1821
```
1922

20-
When you wish for all your routes to be pre-rendered, you can pass `true` to the `crawlLinks` option:
23+
Or to pre-render all routes, you can pass `true` to the `crawlLinks` option
2124

2225
```js { 6 }
2326
import { defineConfig } from "@solidjs/start/config";
@@ -31,4 +34,6 @@ export default defineConfig({
3134
});
3235
```
3336

34-
For more information on prerender options, check out [Nitro's documentation](https://nitro.build/config#prerender)
37+
For advanced pre-rendering options, refer to [Nitro's documentation](https://nitro.build/config#prerender).
38+
39+
[SolidBase](https://solidbase.dev) simplifies SSG development with built-in support for fast, pre-rendered Markdown and MDX pages.

0 commit comments

Comments
 (0)