Inconsistency in Docsify flexible alerts
See original GitHub issueWe are currently using the flexible-alerts plugin for our Docsify-powered contributing documentation.
One of the alert types, attention
, also accepts the danger
keyword to render.
We currently render one of these boxes with attention
and four of them with danger
. For consistency sake, we should use the same keyword to render these.
IMHO, with the displayed text being “Attention” we should use the attention
keyword, but I wanted to get some feedback before opening this up to first timers.
As an alternative, if we prefer the danger
text, we can modify the plugin config to render Danger
on the end-user view instead of Attention
.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
fzankl/docsify-plugin-flexible-alerts - GitHub
docsify plugin to convert blockquotes into beautiful and configurable alerts using preconfigured or own styles and alert types.
Read more >docsify-plugin-flexible-alerts - npm
docsify plugin to convert blockquotes into beautiful and configurable alerts using preconfigured or own styles and alert types.
Read more >docsify-plugin-flexible-alerts CDN by jsDelivr
A free, fast, and reliable CDN for docsify-plugin-flexible-alerts. docsify plugin to convert blockquotes into beautiful and configurable alerts using ...
Read more >docsify
A magical documentation site generator. Simple and lightweight; No statically built html files; Multiple themes. GitHub Getting Started.
Read more >Search Results - CVE
CVE-2022-36533, Super Flexible Software GmbH & Co. ... In affected versions inserting code like `<script>alert("XSS")</script>` in the field marked with ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yup I got that. That’s why I commented so if they are unable then I can pick that up
@kaiwalyakoparkar I also thought of that, but as this issue has been already received by someone, let’s give them some time! If it is more than a week without no response, you can grab this!