-
Notifications
You must be signed in to change notification settings - Fork 64.9k
Description
Code of Conduct
- I have read and agree to the GitHub Docs project's Code of Conduct
What article on docs.github.com is affected?
What part(s) of the article would you like to see updated?
Right now, we need to navigate across multiple pages to understand how the different configuration properties work. In some cases, we have dedicated pages for the more advanced options like groups
While the structure is thorough, it can be confusing, especially when we are trying to get up and running quickly.
Because example usage is separated from the property descriptions, it often leads to mistakes when writing a dependabot.yml file. Users need to constantly switch context between various parts of the documentation, and this slows down the on-boarding experience while increasing errors.
To make the documentation easier to use, I suggest embedding small, minimal examples directly in each configuration property. This would provide immediate clarity, particularly for properties with multiple sub-options or more complex usage. Having an example right where the user is reading ready to copy-paste and try would help them understand the intent and apply it correctly without jumping around.
We can still keep the more in-depth articles for further readings for people that need deeper dives.
I recognize that this would be a substantial change to the structure and content of the reference. I’m not proposing we make the change right away, but I would like to open the discussion to see whether this approach could make the documentation more approachable and reduce mistakes for new users.
Thanks!