Hello all! :wave: Just wanted to give a warm welco...
# general
m
Hello all! 👋 Just wanted to give a warm welcome to @great-microphone-75721, our new lead for technical documentation at Ory! 🎉 He's here to make sure you have the best possible experience with Ory docs. Already he's diving deep into our docs, but your input is invaluable. We will follow up with a short survey on how we can improve the Ory documentation shortly. Welcome to the team, Christian! 🙌 ❤️
g
Thank you for the warm welcome @magnificent-energy-493! 👋 I'm excited to join the Ory team and work on improving our documentation. Speaking of which - I'd love to hear everyone's thoughts on how we can make the docs more helpful for you. We've put together a quick 5-minute survey that will help shape our documentation improvements: https://forms.gle/zjnCin8RBuV2pFd79 Your feedback is incredibly valuable as we work to make Ory's documentation more effective and user-friendly. Thank you in advance for taking the time to share your insights! Feel free to reach out if you have any specific feedback or suggestions - I'm here to help!
r
"How important is it to see these topics in the documentation?" 1 = Very dissatisfied 5 = Very satisfied. -- is this about the current state of the docs, or how important is to to have these topics covered in the docs
g
how important it is to have the topics covered in the docs.
Thanks for pointing that out. Just updated the text to clarify
a
Welcome 🙂 As a first feedback, I don't really understand the provided responses of the second question of the survey… Could you detail what they mean?
g
Thanks for the feedback @ambitious-notebook-80494 I should have made that clearer. I have re-worded to make it easier to understand.
a
Also, reading the doc I miss one approach: people who explore the app and access the doc from the app. Ex: I go in identity schema page, I want to easily find the related doc. Most questions assume I went to the doc first to explore.
g
This is a very insightful feedback. I am assuming you mean the Ory Console right? Will add that to the form
a
Yes 🙂
g
I got you covered. Thanks
a
Also, not directly related to the form,but I remember two years ago or something, Ory had a very complete doc on the OAuth / OpenID protocol and related stuff. At that time, it really helped me to understand how the protocol works under the hood and the right use cases, as I only experienced using it with libraries and as a client. I couldn't find it when I restarted to use Ory, which is a bit sad. This kind of doc is not very product related, but it ensure people new to authentication can learn / feel reassured about the topic they explore. Otherwise, they either go to competitors' doc (like Okta' doc) or blog posts/videos unrelated to Ory, which risk showcasing other products and therefore direct the user away from Ory.
g
I am glad to hear this, Gauthier. I am actually brainstorming how to prioritize content like this. Hope you don't mind me asking, do you prefer this kind of content in a blog, the docs, or a mini online free book?
a
In the doc. In a blog, I may look at the post date (oh, it was written 3 years ago, maybe I can find something more up-to-date?), or just miss it because I don't know I should search somewhere else (I usually focus on the doc as it seems the most maintained / central knowledge hub). I never consumed a mini online book, so… However, often these guided tutorials work well both in doc and blog, so I guess they could be reused both in blogs and docs.
However, I have experience with doc scattered in many sources (doc, knowledge hub, blog posts, …) and I usually find it harder compared to products that keep everything in their doc / searchable from the doc.
g
Gotcha. Thanks for clarifying.