Write the "Next Steps" docs page

[markerikson]

It was just pointed out to me that the Redux docs have a TOC entry labeled "Next Steps", but that page has never actually been written, so the link doesn't work. This would be an excellent topic to add.

This HN comment subthread describes some of the topics that would be helpful to have in a "Next Steps" doc:https://news.ycombinator.com/item?id=15343001 , and this tweet is relevant as well: https://twitter.com/Will_Faurot/status/936792737680048128 .

In general, we ought to:

• Provide suggestions for things to do after going through the tutorial sections
• Give advice on how to handle situations that a user may be dealing with trying to build their first "real" app
• Cover that gap between writing a TodoMVC app and building something "real-world"

[ktrysmt]

How about practicing DDD with redux and some libraries (such as immutablejs).
I'm personally interested in it.

[markerikson]

@ktrysmt : that sounds like it might be an interesting blog post, but I'm not sure it's something we'd want to add to the docs directly.

[nicobarray]

It may contains a section on how to use Redux with server-side project? It is often shown as part of a front-side, react-based, application. I professionally use Redux a the model of node apps (apis, microservices, etc.) and had to come up with ways to structure the project around Redux.

[markerikson]

@nbarray : also not exactly what I'm thinking of for this topic. We do have an existing docs page for server rendering with Redux, and my React/Redux links list's section on React and Server Rendering has several articles that deal with Redux as well.

Hmm. Re-reading your comment, are you actually talking about using Redux inside a longer-lived server app, rather than just for server-rendering HTML?

[nicobarray]

@markerikson yes exactly :) No server-side rendering stuff. Just as the "model" for, let's say, a worker or api that needs to handle some kind of state. I just think it is somewhat sad that the excellent redux/flux philosophy is not applied (or not that much talked about) to a node app too.

[ishankbahl]

@markerikson , can I give it a shot?

[markerikson]

@ishankbahl : sure!

[ishankbahl]

@markerikson , can you point me to the articles in your React/Redux links list which would be helpful in giving advice about issues involving real world apps?

[markerikson]

@ishankbahl : Perhaps some of the info from the Redux Architecture section?

See the couple links in my original comment for this issue for discussion on the kind of information that would be helpful to have.

[codedavinci]

@markerikson,

What about presenting a real use case where we have an app with components that share of the same data /state , but they're not close (even not related at all), and Reduxify it? avoid Props-drilling..

To show the real need of having a State Management lib like Redux.

[markerikson]

@codedavinci : Hmm. That might be a useful addition, although it's not quite what I'm picturing for this page.

[codedavinci]

@markerikson Can I draft up something based on the roadmap above ?

[markerikson]

@codedavinci : please do!