What could a "spoiler tag" extension look like?

Extensions
86

To summit it up we have 3 live versions where two of them is very similar

This make me wonder will it make sense to change the blockqoute standard a little and add a required space after > In that way we could use >! for block spoilers and make it act in the same way as a blockqoute. then we could use >!spoilers!< for inline.

This >!spoilers!< is inline

>! This is a block spoilers 
and it works the same way as blockqoute it can contain other tags inside it.

>! It can also continue just like a normal blockqoute

I personally find it a good solution as the pros and cons are good.

Pros:

  • Big platforms like Reddit and Stack can keep their current solutions.
  • It is a syntax that people are familiar with.
  • It feels like markdown and easy to use as it reminds people of blockqoutes.
  • The syntax of inline and block is familiar.

Corns:

  • We would have to change the blockqoute standard by adding a required space. However the impact of this is very little as it is already good practice and used in most editions.
  • Discord would have to change their syntax, but as most user on the platform doesn’t use markdown when chatting it should not be a bigger problem.
1 Like