Skip to content

Commit e34d67d

Browse files
Merge pull request cerebral#240 from trickydisco78/patch-1
Update 01_serversiderendering.md
2 parents d04f45c + 234adb2 commit e34d67d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

packages/overmind-website/guides/pro/01_serversiderendering.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Server Side Rendering
22

3-
Some projects requires you to render your application on the server. There are different reason to do this, like search engine optimizations, general optimizations and even browser support. What this means for state management is that you want to expose a version of your state on the server and render the components with that state. But that is not all, you also want to **hydrate** the changed stat and pass it to the client with the HTML so that it can **rehydrate** and make sure that when the client renders initially, it renders the same UI.
3+
Some projects requires you to render your application on the server. There are different reason to do this, like search engine optimizations, general optimizations and even browser support. What this means for state management is that you want to expose a version of your state on the server and render the components with that state. But that is not all, you also want to **hydrate** the changed state and pass it to the client with the HTML so that it can **rehydrate** and make sure that when the client renders initially, it renders the same UI.
44

55
## Preparing the project
66

@@ -40,4 +40,4 @@ h(Example, { name: "guide/serversiderendering/renderonclient.ts" })
4040

4141
```marksy
4242
h(Notice, null, "If you are using state first routing, make sure you prevent the router from firing off the initial route, as this is not needed")
43-
```
43+
```

0 commit comments

Comments
 (0)