-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
notifications in markup: info, success, warning, error #887
Comments
A simple hack (sans color) might be to use icons: or good list of more here: https://gist.github.com/rxaviers/7360908 |
rST has these kind of blocks officially (admonitions), but the HTML whitelist is way too aggressive and filters them out, in the worst case leading to misunderstandings because of the missing visual cue how to interpret the text. See also #905 (comment), namespacing could be a viable alternative to just kicking CSS out. |
The emoji hack is a good idea — we won't be expanding Markdown with new syntax, so we won't be adding it as a GitHub-specific feature. |
Except that it does not provide paragraph highlighting. One would have to use
Honestly such a hacking is IMO not exactly what was expected. |
Still a hack, but IMHO better…
|
How can I do that? |
I know it has been 4 years but anyways. I guess you wanted something like that: https://github.com/MuhammedBeraKoc/github-notification-markups. |
It is just a table...
|
@MuhammedBeraKoc thanks for the trick but it still looks quite hacky. I would really prefer an official inclusion in the markup. FYI my implementation of this in commonmark-java : commonmark-ext-notifications is now an official commonmark-java extension. |
Would be great to have some support both at markup and renderer level (CSS) for notifications panel. Something like (taken from Isabel Castillo blog)
Of course underlying markups libraries would have to support such a feature.
In mardown it could be for example:
It would ease a lot to have good rendered README when explaining how to use your project/library or whatever else.
The text was updated successfully, but these errors were encountered: