Wipe away old docs, add a new TOC #3349
Conversation
|
Deploy preview for redux-docs-revamp ready! Built with commit 4da1f22 |
|
Mmm.... "wipe it away" is considerably more drastic than what I was picturing. I think I know what you're getting at, but I was figuring we'd start by shuffling the existing content around. Feel free to keep playing with things on this branch, though. |
|
I propose we merge this as this is a "baseline" branch. In the past I've worked on features where we built a prototype and then later built a production-ready version. When we did that we typed git init on a new repo. Even if parts of the prototype got copy/pasted over it forced us to rereview it and question if we were making the right decisions. From reading through the docs there are endless caveats and notes that may or may not be relevant anymore. I think it'll be easiest if we give the community a giant empty playground to start writing. Our goal here should be to empower individuals to contribute as much as possible and I think a clean slate is an effective way to do that. If you'd like, I'm happy to take a leadership role on this and manage this process. |
This deletes all of the previous documentation and creates a new table of comments based on @markerikson's suggestion in #3313.
I also deleted all of the content on existing docs that need to be reorganized. Even if we end up copy/pasting them back, I think it'll be valuable for us to go through the pull request process so that everything gets a new set of eyes.