But the key, underlying point to ALL this stuff is that you do NOT NEED TO WORRY ABOUT PRESENTATION until you have the CONTENT.
A huge temptation is to spend hours and hours tweaking the presentation as a way of avoiding actually creating the content; this is the real danger.
(should mention https://thebestmotherfucking.website of course)
On the other hand, I was disappointed to see the unique one of those I think it is worth to follow the advice [1] was not cited.
For curiosity reasons, I found out about [1] on a well-known website [2] that definitely puts content in front of presentation, even though I like their website's design.
Of all of them, I think the one you linked is probably the best. It is still interesting to watch the progression.
Such drastic difference with basic adjustments, damn
Initiate rant mode:
- The gray on gray is like a joke, except it's not. I get the theory and alleged benefits. I get that some do prefer it, especially for IDEs. I get that some are happy to see (or at least apply) it all over the web. It just does not seem to apply here. Man alive. Literally making it harder to differentiate the text.
- I don't mind adjusting the browser width to get the lines exactly the right length for my screen and reading preference. Actually, I far prefer it over all the other options. This is like a tragedy-of-the-commons or lowest-common-denominator or dumbing-down-on-the-false-premise-of-being-smart issue. Instead of utilizing what we have, and encouraging people to learn and become capable with the simple and flexible tools, it's one size fits all (or, you pick the size you think I want). Only it's not.
End of rant. Sheesh.
I flipped over into reader mode and it's much improved, solely because of line length and dark mode.
I can't speak for other frameworks but tailwind only compiles the classes you actually use at build.
The balance between design & function can be at odds when the mission of the page is not clear.
For consumption, these are awesome, your brain almost relaxes as it's easier than the usual onslaught.
The CSS of the second website is wrong, as it uses 'color' without setting 'background-color'. Assuming anything about the default background color is not possible because it is user-configurable in most browsers.
At least http://motherfuckingwebsite.com remains readable when you change your color settings (the second one is completely unreadable on my browser).
The text was readable as designed on a white-background. CSS that considers accessibility or print friendly is always good to add.
Javascript test?
If it was a javascript that checked for the elements you want to ensure is there that would be neat too, I just wouldn't want it to be just me :)
If the whole point of your website is to brag about code to accomplish reasonable formatting.... can we at least have code formatting? I think I have enough bandwidth to afford some line breaks.
Client side GA????
An UI made of disintegrated, inconsistent and half-assed tries at writing CSS/JS. Not a rare problem in my experience.
Also happens to me when trying to write a "tiny web app for fun" where the CONTENT is interactive and created by myself.
So, to extend your comment: you do not need to worry about content if your website isn't even reachable. A GET request should never result in the client being bombarded with captchas. Unless you have a sure fire way to determine if said client is a human or an evil AI taking over the world (nobody does), just serve the damn page.
It's definitely not, there is something else doing that to you. But it's not this website.
<li><a href=""></a>
</li>
[0] example post from my blog https://mvexel.prose.sh/20230227-keeping-osm-database-uptoda...
Everybody finds their writing juices differently. Push where it means you'll write more.
same went for emacs I stopped using themes
Bold statement. Those look mostly terrible to me.
Mailing lists are still good for that I guess.