Please bring back the less ugly alerts syntax #148220
Replies: 2 comments 1 reply
-
| 💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩ 
 Where to look to see what's shipping 👀 
 What you can do in the meantime 💻 
 As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ | 
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Body
The current syntax for alerts or notes or warnings in markdown documentation on GitHub looks like this:
How it looks like:
Warning
This is an example warning that works.
However, this syntax is in my opinion vastly inferior to the old way that used to work, which was this:
...but this no longer works:
I'm suggesting this removal of the old syntax is reverted, and the old syntax should be reintroduced, simply because it is a very intuitive way of writing it. In my humble opinion,
[!...]looks like a bracketed chaos and since it's not even a link it semantically doesn't seem to make much sense.Markdowns main advantage is that it looks intuitive and approachable, for most elements and where it is feasible of course, which is what a
**Warning**achieves and in my opinion, a weird-looking[!Warning]simply doesn't. Please keep the intuitive syntax around for those who prefer it.Beta Was this translation helpful? Give feedback.
All reactions