12

I think We should adopt the color background quote style with the vertical rule as: It is clearly different It would help with the confusion of formatting code as a quote. We could use a light aubergine consistent with Ubuntu colors: These might be too dark.


9

There's an app for that! https://stackapps.com/q/3341/17253 And an extension, too: https://chrome.google.com/webstore/detail/kbd-button-for-stack-exch/ignlodfdkifdjomipiamkaaoiokkjlok And here's the extension's Git page: https://github.com/oliversalzburg/se-kbd-button One of those two should work for you.


8

Two points: I can see the merits to the style you are proposing. But we're not going to change our Markdown implementation to support them. For one thing, most posts don't need (or benefit from) deeply nested outlines, so this is a rather rare edge case at best. a. We aren't writing U.S. Code here. b. Maybe use actual code blocks instead. For another, ...


7

If you're talking about per-text size changes, there's some basic things you can do. For large text, you can use a # before the text. #Hello_World goes to Hello_World It needs to be on its own line. The small text you see in Oli's answer was produced by putting <sup></sup> or <sub></sub> around the text. <sup>I know, I know. You ...


6

I doubt this is intentional – it‘s syntax highlighting, which in this case was added automatically when the question was tagged python, see its Tag Info page: Code Language (used for syntax highlighting): lang-py The syntax highlighting help page explains how one can add this highlighting to one or all code blocks. Further reading: Help on syntax ...


5

I suggest positioning the keyboard shortcut icon right after the Emphasis icon, also called the Italics icon, which looks like this: I think it would look a little bit ugly there, but I don't care about that. What I do care about is the user experience factor. The proposed keyboard shortcut icon would look a little bit mean there, which would give users a ...


5

We don't need to enforce a style policy about exactly how people should use bold and italics. It is okay for different posts to use different styles. There is no one proper way, nor probably even just a few. Trying to mold authors to one style would make it artificially hard for people to contribute to the site. Having a policy about bold or italics that ...


4

I would suggest that we keep the same colour for the quote, but instead just add the rule along the side. I took the line colouring from the yellow one on Meta.SE- it goes from (33,255,241) to (35,255,199), a change of (2,0,-42) so I did the same with the grey, from (0,0,238) to (2,0,196). These are all HSL colour numbers. I also think that the code should ...


3

Doing something like this leads down a path I will (lovingly) refer to as formatting hell. In my personal opinion, not everything needs to be a list, and we shouldn't be encouraging sublists any more than necessary. We have better ways of splitting answers - those would (ideally) be better to use. Compare the following: In order to summon a unicorn, one ...


2

I think having a different color for blockquotes and code makes sense, because they serve two different purposes. As you've shown sometimes you may have code inside a blockquote, and it would be nice to be able to visibly distinguish it. I would suggest staying away from highlighter colors since to me they say this is the important part not this is the quote,...


1

This could be done using Stylish, say with CSS (in Mozilla-compatible format for Stylish) like so: @-moz-document domain("askubuntu.com") { ol ol li { list-style-type: upper-roman; } ol ol ol li { list-style-type: upper-alpha; } } giving:


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