I have none of the above attributes, but I have secret attribute number 4: I am a busybody. So - my observation is your documentation could be split instead of by product, by theme (or by product then theme): • Ops - how to run things, do healthchecks, deploy things, configure things via env vars • Architecture - what Ory products to use in what scenarios, how to incorporate the Ory products into your own system (e.g "how to do mobile"; "how to do high availability" • Features and security concepts - e.g. "what flows do/don't we support and why", "when are we getting user migration?"

Agree with that

thanks, that is good feedback and goes hand in hand with how we planned to refactor the docs soon

Absolutely Robert, I think this is a great idea. We have scoped out to change the sections into topics such as “Identity”, “Permission”, “OAuth2”. We’ll tackle this early next year and restructure the sidebar. If you have more concrete ideas we’d love to hear them 🙂

Ah! I thought you meant my ideas were about concrete and you liked them.

Ok, let’s rephrase. My german tongue is coming through once again: The ideas are really good, if you have more like them please share 😄

Thank you. I will.

🙏

Thanks Robert 🙂