Skip to content

admonition support: warnings/hints/notes, etc. #3153

@skshetry

Description

@skshetry

Having a proper visually distinguishable box for admonitions would make it easier to read the documentations. Right now, we misuse markdown blockquotes and (sometime) use emojis for variants. But they are mixed in between other documentation paragraphs, that it is quite easy to miss (and does not look good to be honest).

Some screenshots where I found it confusing:
Screen Shot 2022-01-06 at 16 19 59

Screen Shot 2022-01-06 at 16 19 26

Screen Shot 2022-01-06 at 16 19 12

Screen Shot 2022-01-06 at 16 19 02

These are only a few examples that I quickly scanned through.

We can take some inspirations from spacy's and thinc's docs:
Screen Shot 2022-01-06 at 16 23 30

Screen Shot 2022-01-06 at 16 25 55

Screen Shot 2022-01-06 at 16 25 31

Screen Shot 2022-01-06 at 16 24 29

Screen Shot 2022-01-06 at 16 26 51

Screen Shot 2022-01-06 at 16 27 52

Screen Shot 2022-01-06 at 16 27 45

Screen Shot 2022-01-06 at 16 28 57

Metadata

Metadata

Labels

A: websiteArea: websitep2-nice-to-haveLess of a priority at the moment. We don't usually deal with this immediately.type: feature-requestDEPRECATED New feature or requestwebsite: designWebsite graphic designwebsite: eng-docDEPRECATED JS engine for /doc

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions