Alex Krolick
Alex Krolick
I don't want to maintain a Gatsby site, Docusaurus works pretty well for everything we need
Open to discussing a better organizational scheme though, as it seems this question isn't really about Gatsby per-se but the overall hierarchy and overlap between the libraries
- I think it would be good to do this as part of exploring a monorepo for the packages, to make it easier to update downstream packages and docs all...
So the issue here is that the example imports from `history`, which is a dependency of `react-router`. Typically importing from a nested dep is discouraged and a lot of people...
Cool, nice to see it. Is this a framework type of integration (which has its own package), or more of a pattern like the ones for Redux and React Router...
Most of the other libs are in the `@testing-library` org & namespace, which allows the TL contributors to maintain them (propogate breaking changes, etc), but it's _probably_ ok if you...
What we have done in the past is bring in the packages and then create a sub team for maintaining that framework, so we would just do that for any...
My only comment here is that 3rd party content becomes stale quickly, so we should try to avoid relying on it too much
Docusaurus supports translation: https://docusaurus.io/blog/2021/03/09/releasing-docusaurus-i18n#translate-your-site
You mean rename the Docs link in the top left?