We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It's usually a good idea to avoid mixed-case directory names and names containing spaces for content sections (or just in general for code or doc related projecqts). All of the directories under https://github.com/google/docsy/tree/master/userguide/content/en/docs fall into this category.
I propose that we rename these to correspond to the section-path names used by the deployed site. For example, rename
userguide/content/en/docs/Adding content
userguide/content/en/docs/adding-content
Thoughts @emckean @LisaFC?
The text was updated successfully, but these errors were encountered:
SGTM!
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
It's usually a good idea to avoid mixed-case directory names and names containing spaces for content sections (or just in general for code or doc related projecqts). All of the directories under https://github.com/google/docsy/tree/master/userguide/content/en/docs fall into this category.
I propose that we rename these to correspond to the section-path names used by the deployed site. For example, rename
userguide/content/en/docs/Adding content
touserguide/content/en/docs/adding-content
, which corresponds to https://www.docsy.dev/docs/adding-content/Thoughts @emckean @LisaFC?
The text was updated successfully, but these errors were encountered: