Post

We've had many complaints over the years that the 4 separate Redux docs sites (core, RTK, R-R, Reselect) makes it confusing to navigate. I'd always said "we aren't doing a monorepo, so no combined docs". Well, I now have a working prototype of a combined docs site :) github.com/reduxjs/redu...

github.com[DRAFT] Full prototype of a combined docs site by markerikson · Pull Request #4950 · reduxjs/reduxSupersedes #4792 Fixes #4789 (eventually) In #4792 , I experimented with a Git-based approach (using submodules, I think) to pulling in the other repos so we could use Docusaurus's multi-instan...

20/9/26, 1:53 am0 reposts6 likes

Mark Erikson

@acemarke.dev

20 Sept

The impl clones the other repos into core in CI, and runs a multi-instance Docusaurus site build. This seems to work surprisingly well! All four sites are there, with their setup quirks, and very little customization needed: deploy-preview-4950--redux-docs.netlify.app

deploy-preview-4950--redux-docs.netlify.appRedux - A JS library for predictable and maintainable global state management | ReduxA JS library for predictable and maintainable global state management

Mark Erikson

@acemarke.dev

20 Sept

This looks like the direction we'd want to go. Still a lot we'd have to do: set up infra in the other repos to still get PR previews; set up redirects; do a massive rethink of our docs content and organization to dedupe and make it easier to follow; and actually ship it. But, big steps forward!