-
Notifications
You must be signed in to change notification settings - Fork 12
[Discuss] Definition lists #109
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
Comments
The markdown library we use has optional support for definition lists in the following format: Term 1
: This is a definition item
With a paragraph
> This is a block quote
- This is a list
- with an item2
```java
Test
``` What I really don't like is that this introduces space indentation sensitive formatting to the source documents for the benefit of the output. If we can capture all valid use cases for this with more specific directives we will create a more prescriptive writing experience and a more uniform UX on the user facing docs. |
Added as a question to follow-up with during bug bash next week. |
Given how pervasive definition lists are in docs openend: To add support for vertical definition lists. |
Summary
(AsciiDoc - Description Lists)
For Asciidoc’s description list, we use MyST’s definition list. Note that this feature is not enabled by default and one needs to add deflist to myst_enable_extensions.
The Elastic Asciidoc engine defines multiple types of description lists which are formatted differently. The different types are specified by an attribute before the description list. For example, this specifies that the description list is of type ‘horizontal’:
For now, they will all be converted as the standard MyST definition list.
To do
The text was updated successfully, but these errors were encountered: