-
Notifications
You must be signed in to change notification settings - Fork 343
New issue
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
Add preferred terms list to style guide #386
Conversation
.. glossary:: | ||
|
||
Ansible | ||
Use on all occurrences or ``ansible`` if referring to the CLI command. Preference is to use this to refer to the Ansible community package. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The definitions under each term should have extra indentation per https://www.sphinx-doc.org/en/master/usage/restructuredtext/directives.html#glossary
Use on all occurrences or ``ansible`` if referring to the CLI command. Preference is to use this to refer to the Ansible community package. | |
Use on all occurrences or ``ansible`` if referring to the CLI command. Preference is to use this to refer to the Ansible community package. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok thanks. Frankly I was so mortified by all my spelling errors I forgot to take a closer look at how the glossary works. Thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tend to use https://github.com/sphinx-contrib/spelling for detecting typos...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personally I like codespell https://github.com/codespell-project/codespell
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't know it can check RST.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok now I have a duplicate term definition problem because we already have an actual glossary in the appendix. I'm inclined to remove the glossary from this section because it's not really defining the terms, just how to type them in documentation.
Co-authored-by: Sviatoslav Sydorenko <wk.cvs.github@sydorenko.org.ua> Co-authored-by: Don Naro <dnaro@redhat.com>
Co-authored-by: Don Naro <dnaro@redhat.com>
f11a62b
to
fec960c
Compare
@leogallego @Andersson007 @gotmax23 @felixfontein @oraNod - I think I got it right finally. Please take another look at the preferred terms... thanks! |
Co-authored-by: Felix Fontein <felix@fontein.de>
Backport to stable-2.16: 💚 backport PR created✅ Backport PR branch: Backported as #515 🤖 @patchback |
Backport to stable-2.15: 💚 backport PR created✅ Backport PR branch: Backported as #516 🤖 @patchback |
(cherry picked from commit 20f43ca)
(cherry picked from commit 20f43ca)
Fixes #152