how the hell do you keep React docs useful once the project starts getting bigger
Hi everyone so glad I found this sub, I'm rlly confused about this so basically we’re a small dev tools startup with a React SDK that’s starting to get used in more projects. Our docs were fine when everything fit into a handful of examples now we’ve got setup guides, component examples, edge cases, and different integration paths depending on how someone’s app is structured but honestly the annoying part is people still end up asking engineers questions that technically should be answered somewhere in the docs.
About the teams maintaining React libraries or SDKs, how do you handle this as the docs grow? Do you keep everything close to the code or u have someone own documentation, use a dedicated docs tool, or just keep improving the examples as questions come in honestly trying to avoid ending up with 200 pages where nobody knows which example is still current. It's honestly driving me crazyyy
Posted Sep 22, 2026, 9:36 PM UTC