-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Document available lexers #51307
Comments
Files identified in the description: If these files are inaccurate, please update the |
This content belongs somewhere in the style guide. Probably in the section on rST. |
Files identified in the description: If these files are incorrect, please update the |
Fixes: ansible#51307 Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
resolved_by_pr #71458 |
* dev_guide: Add Pygments Lexer examples Fixes: #51307 Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com> * adds ansible-output lexer, remmoves unsupported lexers Co-authored-by: Alicia Cozine <acozine@users.noreply.github.com>
* dev_guide: Add Pygments Lexer examples Fixes: ansible#51307 Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com> * adds ansible-output lexer, remmoves unsupported lexers Co-authored-by: Alicia Cozine <acozine@users.noreply.github.com>
SUMMARY
The Ansible documentation supports a range of Pygments lexers for Sphinx to make our code examples look good. Examples include YAML, python, Jinja2, and more. Each lexer parses a particular type of text and adds color-coding and formatting to the HTML based on the rules of that text type.
Document which lexers we support, the correct syntax (for example,
YAML+Jinja
oransible-output
) for each one, and how to choose the best lexer for each code example or block of text.Related to #50836.
ISSUE TYPE
COMPONENT NAME
docs.ansible.com
ANSIBLE VERSION
2.8
CONFIGURATION
N/A
OS / ENVIRONMENT
N/A
The text was updated successfully, but these errors were encountered: