Generally the docs are linked from the project wiki pages. So you can find say the docs for DynamoDB on their wiki page (I'm not sure that's true anymore but it's an example)
The docs are actually not as important as a legacy item as you would think. They're good to go back and look at for context. They're also good to hand to people as examples.
But their real purpose is for forming consensus / alignment around an idea and then choosing to pursue, iterate, or can the idea.
Thanks for sharing! This makes a lot of sense given my own experience -- my workplace is very document centered but the docs are fairly transient and disposable once the decision is made. My takeaway is that there's a high bar of institutional memory and personal processing time to engage with the history of docs, which is made higher when there isn't a curated index of some kind.
The docs are actually not as important as a legacy item as you would think. They're good to go back and look at for context. They're also good to hand to people as examples.
But their real purpose is for forming consensus / alignment around an idea and then choosing to pursue, iterate, or can the idea.