This content originally appeared on Hussein Al Hammad and was authored by Hussein Al Hammad
Without judgement: there are many developers who manually inline CSS in their HTML emails. This post is aimed at developers who choose or have to manually inline their CSS.
If you’re reading this and not in the world of HTML email development, the short explanation is CSS has to be inlined out of necessity and not by choise.
I’m not going to dive into the maintainabiliy issues of inlined CSS and why you should avoid it if you can. What I want to discuss is the readability of inlined CSS. Readble code is very valuable; particularly in a team environment. If you don’t put an effort to keep your code readable, you’re hurting yourself and your team.
When you write CSS in a ruleset, you probably use whitespace to keep it readable like so:
1.my-class {2 color: #000;3 fake-property: fake-value;4}
Besides the indentation, you most likely add a space between the property name and the value:
1property: value;
I see developers trying to do the same when manually inlining their CSS:
1<div style="color: #fff; property: value; fake-property: value;"></div>2<div style="color: #fff; property: value; fake-property: another-value; margin: 10px 0 30px; padding: 10px 20px;"></div>
The space between a property name and its value is equal in size to the space between a value and the following property. This makes it harder for you as a human to scan pairs. It simply takes your brain longer to parse the CSS.
A more readable alternative would be to stack the properties like you would when writing full rulesets:
1<div style="2 color: #fff;3 property: value;4 fake-property: value;"5>6</div>
I know this is not everyone’s cup of tea. It’s not the only approach though. You can keep everything in one line and omit the space between a property and its value:
1<div style="color:#fff; property:value; fake-property:value;"></div>
You end up with CSS that is a lot easier to scan and parse as a human. You can compare the readability of the two approaches below:
1<div style="color: #fff; property: value; fake-property: another-value; margin: 10px 0 30px; padding: 10px 20px;"></div>2<div style="color:#fff; property:value; fake-property:another-value; margin:10px 0 30px; padding:10px 20px;"></div>
This content originally appeared on Hussein Al Hammad and was authored by Hussein Al Hammad
Hussein Al Hammad | Sciencx (2022-07-12T00:00:00+00:00) Readable inlined CSS. Retrieved from https://www.scien.cx/2022/07/12/readable-inlined-css-2/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.