14

The keyboard on Apple.SE also looks much better than the one on MSO:


11

You need to indent by an additional four spaces for code blocks to be considered so under list item.


8

Fundamentally - we didn't have code fences then. We do now. Essentially - the conversion from markdown to rendered markup happens once - when the post is posted. For extra fun - since its an odd number of backticks, the first pair in the opening code fence was "one" set of unformulated characters, the last and the first of the closing pair, and the 2 at the ...


8

The backticks (`) are a Markdown shortcut for what will later be rendered as <code> in HTML. Needless to say that this tag should be used to highlight actual code (or commands), not arbitrary words. To highlight keywords, the <em> tag should be used. This again will often be displayed as italics, so you get the same result by wrapping text with ...


6

The padding of the <code> element is set to 1px 5px 1px 5px, thus indenting the left and right by five pixels. This makes sense because inline code needs to be properly spaced and it'd look weird without the padding. Why does it look weird when using it for multiple lines? Because <code> is not meant for that. <code> is for inline ...


6

Just use the escape character: \


6

YouTube embedding is enabled only at Gaming and Audio-Video Production, IIRC due to the high reliance on videos to show tips etc. Not available on Super User. YouTube and SoundCloud embedding is now enabled It is now possible to embed YouTube and SoundCloud content in posts here. […]


5

Write [tag:tagname]. Renders as: tagname. For tags from the Meta site, use [meta-tag:tagname] instead.


5

It's useful to bold key points, but I think doing it to whole sentences is too much, maybe even counter-productive. What @JakeGould did on this question of mine is a great example of how to use bold to add value: Are some USB hard drive enclosures unsuitable for system drive use? The key is a short bold heading, because it: draws your eye to the key ...


5

Headers aren't used to summarise content. Headers are used to create section breaks. Topic sentences are more suitable as the summary slug. Your first sentence in a post should not be bold, or a heading. If you need to call out the first sentence, and you need to go beyond normal body text formatting (i.e. none), then your sentence is not as clear or ...


4

If the error is mostly human-readable text, I would suggest double quotes. "Error: file not found" looks natural because it's laid out more or less like a standard human sentence. Code formatting should be reserved for (surprise!) code, or things that are generally displayed as monospace, especially if they're not English-like. For example, "...


4

Not sure what the fix is supposed to be but: >Hello <!-- This is a comment --> >world! resolves to Hello world! For a neat break between quote blocks. Apparently this is also the suggested fix as of 2012. It looks like any non-whitespace characters will cause the markdown formatter to trigger a break, so you can use a <br/> ...


4

You can format raw data by indenting it by 4 spaces, or pressing the CtrlK shortcut after selecting the text, or clicking the {} button in the editor, or wrapping your text in <pre></pre> tags Please use the preview window below the editor to check if the formatting looks right. Alternatively, format your tables with a web application as ...


4

File system paths are intended to be used by programs. A standardized format and separator is essential. Our explanations are read by humans capable of handling a computer. There's just no need. What the separator is is obvious in context. Let's just make sure the description is readable, and keep our hands off each others' posts for what is pretty much ...


4

The next build will fix* this, we weren't encoding items titles properly for the email (and only the email it looks like). *Should be within the hour.


2

The editing help page that you're looking at is for the most part only relevant to post bodies, the Comment Formatting bit at the end is what you need. And, you'll see that comments use a very limited sub-set of markdown. You can also see the basics by pressing the "help" link that is available under the Add Comment button. So, the style options you have ...


2

Comments are treated as second class citizens throughout the network, as such the formatting options in comments are limited. You could you could italicize them or use backticks to highlight the points


2

I don't think there is a standard way to represent steps (GUI actions) needed to perform a certain task. However, I just checked Windows help, and they use numbered lists to explain how to do things. I suggest you do the following: if the steps are sufficiently long, write a numbered list, e.g.: Open Window A. Select option B. Press button C. If the ...


2

The moral of the story is: Don't intimately mix Markdown and HTML in the same narrow block of code, because Markdown being a regex based solution will not know how to treat some elements. Which should tell you exactly what happened to the post in question. The parser got confused. Technically when the markdown parser encounters HTML it should quit ...


2

The help centre page How to reference material written by others gives a suggested format that quitations should take. It shows blockquoting being used for copied text. It states Provide a link to the original page or answer Quote only the relevant portion Provide the name of the original author The fact that the word "quote" links to our help ...


2

I'd go with a self contained answer referencing the tweet. A screenshot would be nice, but it would be as simple as "I contacted the discord team via twitter - and they responded, that it was currently...." Of course if it got fixed its nice to follow up your answer.


2

In my comment, it is not formatted and the backticks are visible. In a comment you need to double the backticks to prevent the \ escaping the closing backtick: ``\\?\``


1

Is this the standard of formatting answers now, or am I right to question this decision? Yes it is the standard, and you are wrong to question it. Note the use of block quotes above where I am quoting you. From How to reference material written by others: When you find a useful resource that can help answer a question (from another site or in an ...


1

I think it's fine to use headers the way you did there, but not when the header spans 3 lines.


1

The client-side and the server-side Markdown implementations differ. This, combined with the fact that the list wasn't formatted using Markdown, broke the image, I guess.


1

I'd personally prefer italics over bold or code spans, and single characters (like →, », ›, ▸, >, -, or |) over something like ->. I don't know about other platforms, but Apple's documentation tends to use > (usually without any emphasis) to separate different actions. I've settled on this format myself: Dashes for hierarchies of menu items: *...


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