redmaniack
HTML Replaced vs. Void Elements
How to use an SVG as a favicon for your website
The current DOM node in the browser's console
Visually validate an input field using CSS
CSS Writing-Mode Experiment
Hoisting in JavaScript
The 3-in-1 full-stack developer
CSS resize none on textarea is bad for UX
I wrote some lines about technical SEO and stuff after I analyzed ~8M web pages
An SEO Story on the Website Name from the Google SERP
The 3-in-1 full-stack developer
Fancy New Selectors Within Groups Can Break Your CSS Rule
CSS utility classes for sizing and naming conventions
I wrote about how to include a production-ready SVG icon system within Pug/Jade
How to convert an array-like object as NodeList to a real JavaScript Array
ES6 const is not constant or immutable
Besides that, what I was really trying to say was that a tool like Normalize.css or Bootstrap's Reboot may be more helpful than the classic CSS reset.
I agree my findings are far far away from a specialized audit, but nor did I intended to do one.
I just wanted to check out some of the best practices & stuff, based on my daily experience as a web user and developer.
.compose-form .compose-form__modifiers .compose-form__upload-description input::placeholder { opacity: 1; }
e.g. I do like how Sass makes it easier to write BEM-like code similar to the below:
// style.scss .btn { ... &--success { ... . } }
// style.css .btn {...} .btn-success {...}
But when abusing Sass nesting and choosing a weak naming convention, the resulted CSS selectors can go wild. Here's an example: https://github.com/tootsuite/mastodon/blob/995f8b389a66ab76e...
A while ago I made an HTML study on around 8 million web pages: https://www.advancedwebranking.com/html/
Also, I wrote about this journey on CSS-Tricks: 1. https://css-tricks.com/average-web-page-data-analyzing-8-mil... 2. https://css-tricks.com/random-interesting-facts-htmlsvg-usag...
On accessibility, I'd have loved to try out some screen readers but at the moment I write this article, I thought this accessibility analysis would deserve its own separate topic/article. A11Y is always hard.
https://catalin.red/thoughts-on-accessibility/
Sorry for all these plugs.
I'd love to contribute and try to improve things but this task might become gigantic on long-term, as the Mastodon project itself :)
The thing is there are so many good reasons to use an SVG icon font system nowadays: pure vector, control over the individual shape symbols, positioning is easier thanks to knowing its exact size etc.