This is different then in a code editor, where the whole 'page' can be in such a syntax. The aim of code examples should be allow people to understand the code, not to work with it, and therefore it needs to work with the rest of the descriptive text on the page, not against it. I suppose there is a difference based on the default settings of a browser, but for me the text just started blurring. I'm in favour of readable code snippets first of all, and the shades of grey, and green-grey in a smaller font size became even more unreadable when the text is in caps. This change introduced very real accessibility issues, and broke inline HTML snippets, which is central to the work of many people. Please don't dismiss those of us who have taken the trouble to voice our concerns as some kind of petty personal preference. "Note that I am not criticising the aesthetics of inverted designs, just their readability." This is a medium for discussing work, where code is largely provided to illustrate the narrative at hand.Īs outlines, most other code platforms also use a light background, and this is because research has shown it has superior readability. Yes, many people use a similar scheme in a code editor. Nibh tota minim mel te, no sea vidisse maiorum philosophia, sadipscing theophrastus ea mel. Affert consequat vel an, alterum imperdiet mei ex. Rebum diceret constituto cum in, esse ancillae ut vis. Nec an molestie deterruisset, te iisque sadipscing vis. Eu duo habemus philosophia, vix ut bonorum partiendo. Ea sed volumus fastidii, eu reque clita vis. Lorem ipsum dolor sit amet, malis recteque ea eum. Here's a code block with html in it, and a little inline CSS. Have your accessibility issues been resolved? Of those who have posted to this issue, a majority certainly seem to prefer the light background approach. Yes! Please do create an alternative code block colour scheme that has better contrast and readability. We're completely open to discussion about this, and I could work on changing the color scheme as part of our current documentation work. Has that design work been discussed on somewhere we can see mockups and provide also wrote: this was actually carefully planned and customized to match the upcoming design work that we have planned. It would seem the immediate bugs like that have now been fixed. Then I discover it was this syntax highlighting feature causing me to waste time and feel stupid. It was incredibly frustrating, made me feel stupid, and I ended up using a screenshot of the code instead. But perhaps I should also try a little inline I first noticed this issue when trying to post HTML and couldn't figure out what was going wrong. So - here's some inline HTML paragraph with strong text to see what the changes look like. "I like that it's closer to what I use in PHPStorm."Īll of that leads me to continue to view this as a very subjective matter. I will add that I've heard more positive feedback than negative for the dark color scheme. If we have some way to see what the majority of developers on the site prefer (light on dark vs dark on light), I'd be happy to update the styles either way. Color preference for light on dark vs dark on light seems to be a pretty subjective decision for developers, and I'm not sure that there is any way to make everyone happy. It's not one of the standard themes in Prism, and I don't think we'll want to switch to one of the default schemes. Here's my response from the previously mentioned issue:Īs for the color scheme, this was actually carefully planned and customized to match the upcoming design work that we have planned. I'm reopening this issue to consolidate discussion of code block color schemes to the appropriate place.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |