Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/routes/concepts/stores.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,9 @@ 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 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

Expand Down
Original file line number Diff line number Diff line change
@@ -1,9 +1,12 @@
---
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 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

```js { 6 }
import { defineConfig } from "@solidjs/start/config";
Expand All @@ -17,7 +20,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 pre-render all routes, you can pass `true` to the `crawlLinks` option

```js { 6 }
import { defineConfig } from "@solidjs/start/config";
Expand All @@ -31,4 +34,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.