10

tl;dr: No, there's no rule against it. But, it will probably annoy a lot of users, and that's probably not the effect you were going for. Markdown syntax does not work in question titles, but people try to use it all the time. Whoever edited your post likely assumed you were trying to use markdown without realizing that it did not work, and was trying to "...


9

There is literally no difference. The example below shows two spoiler blocks – one with a newline, one without. The output HTML is the same in both cases. There is no difference between the two. As such, I think it comes down to personal preference. There’s no “better” way of doing it. I prefer having the empty line there, because I think it looks nicer, ...


9

According to this comment from eons ago, no one here can. However you can ask it on Meta Stack Exchange and they may help. As far as I can research, the mods (and certainly the users) are unable to change the formatting page specifically for SFF. It is set by the developers, although changes have been implemented from Meta.SE they won't add every example in. ...


8

"This is the regular blockquote". Is this what you want? Code for the above: >!This is spoiler 1. <!> >"This is the regular blockquote". <!> >!This is spoiler #2.


7

The easiest way to put blank lines and breaks into spoiler text (or any blockquote text) is to use the 'break' command >! My text goes here. <br> This text goes on the next line. <br> <br> <br> I can also use multiple breaks to create multiple line breaks.


7

I suggest that the reason is at least partly related to the official Markdown Editing Help page: When a user clicks on the advanced help link, the spoiler tag demo/example itself that pops up on the instructions page shows no spacing between the non-spoiler and spoiler segement.


3

There's no hard and fast guideline. What I've found works for me is what you've described as #6; placing script quotes into inline boxes (with the > key). I also bold the name of the person speaking, use italics to indicate speech and place square quotes to indicate non-speech directions: WORF: Captain, I recommend we fire photon torpedoes PICARD: Denied....


3

I do not think there is a universal “best” way to format quotes. But honestly I believe formatting of these things can get out of hand and the simplicity of the markdown formatting should be respected. In general—when it comes to markdown formatting—if you are feeling restricted by it’s limitations, many times the best solution is to rethink your overall ...


3

With the introduction of CommonMark this is now even easier to do, just use the following markdown: >!This is spoiler 1. >"This is the regular blockquote". >!This is spoiler #2. For the rendered output: "This is the regular blockquote". Continous spoilers still don't work, I don't think that has ever really been supported, ...


2

Spoiler markdown doesn't really work well with other markdown. This is pretty much by design as we don't want too much content being hidden. That said you can insert a list into spoiler markdown by using plain HTML like the below: >! The quick brown fox: >! >! <ul> >! <li>Jumped over the lazy dog</li> >! <li>And ...


2

It depends. There's not really a clear rule and some of that comes down to personal preference. However, there are some preferred general guidelines for the overall use of SE when it comes to quote blocks in general. When quoting a larger standalone block of text you should really use a quote block, as that is what quote blocks are made for and it ...


1

The only situation I can think of in which it would make a difference is when your question/answer is using bullet points or a numbered list. Without empty line: In film #1 we learn In film #2 we learn In film #3 we learn With empty line: In film #1 we learn In film #2 we learn In film #3 we learn You'll notice that, if you're making a list with ...


Only top voted, non community-wiki answers of a minimum length are eligible