Docs: improve guides on context usage

[TkDodo]

As discussed on twitter, let's think about re-structuring the docs to make some patterns more prominently available, like scoping stores to a component subtree with React Context. I recently wrote a blogpost on exactly that topic, and got a lot of questions why this pattern isn't encouraged in the docs.

[dbritto-dev]

Let's create a list of all the them:

• createStore + Context API (name TBD)
• slices pattern
• namespaced slices pattern
• persist w/o ssr
• lazy load slices
• react query
• dynamic stores
• async actions
• tutorial
• getting started
• typescript patterns
• react native

and more

[dai-shi]

If there are many patterns (and it looks like so), we should probably separate into levels? Like "Basic guides" and "Advanced guides". That way, people who first read those docs don't have to read everything at once.

[dbritto-dev]

yeah, I'm down with you

[dai-shi]

Apart from "context usage" which this discussion is aiming at, I see the overall structure has room for improvements:

getting-started/
guides/
integrations/
migrations/
previous-versions/

[dai-shi]

So, I'm not sure if we should separate a) overall doc improvements and b) improve the guide for context usage.

[dai-shi]

I think @dbritto-dev is the right person to take the lead on improving docs. So, I'd like to nominate him as one of the maintainers for docs.

[dai-shi]

I don't think we can do that, since the new docs follow the new syntax supported by vitepress and wouldn't work on the current setup

Isn't it just ignored? Or, can you avoid incompatible syntax for the start? The whole point of separating docs and website is to make docs agnostic to website.

[dai-shi]

And, docs should be browsable on GitHub too.

[dbritto-dev]

@dai-shi the docs would be browsable on GitHub, we don't have issues with that

[dbritto-dev]

@dai-shi but let me work on updating our current docs to follow the new structure to support the new website

[dbritto-dev]

@dai-shi I'm going to create two discussions and two PRs as you are suggesting