Community Survey to Improve Docs

[christiannwamba]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Ory Network Project

No response

Describe your problem

Documentation needs improvement based on user feedback. Key signals include:

• Users report difficulty finding code examples
• Structure can be confusing
• Navigation between related topics is challenging
• Setup and implementation guides are mixed together
• API documentation needs enhancement

Describe your ideal solution

Create and distribute a comprehensive survey to gather user feedback on:

• Documentation structure preferences
• Content discovery patterns
• API documentation needs
• Feature vs solution-based navigation
• Overall satisfaction and pain points

Workarounds or alternatives

N/A

Version

N/A

Additional Context

No response

[vinckr]

To track distribution:

• newsletter @jfcurran
• announcement in community slack @vinckr
• pinned posts in community slack main channels @christiannwamba (you post, I pin them)
• pinned discussions on github for /kratos @vinckr
• pinned discussions on github for /hydra @vinckr
• pinned discussions on github for /keto @vinckr
• pinned discussions on github for /oathkeeper @vinckr
• pinned discussions on github for /ory org @vinckr
• banner on website? @jfcurran