I just realized there's this fancy thing called https://512kb.club @kev, I wanted to join it and when I checked I realized my blog already qualifies for this 😄
So there we go: https://github.com/kevquirk/512kb.club/issues/95
@kev while at it, let's also join https://250kb.club 😏
Next step:
https://10kbclub.com
@bshah @kev
@wzqtparor @kev hmm there's 10KB of css... I wonder if I can keep slightly sensible look and kill that CSS at same time ...
@bshah @wzqtparor I think 10k is too far. I think you can easily have a 10kb site, but it wouldn’t leave much room for scope to make it interesting or unique.
@Seirdy @bshah @wzqtparor absolutely. The words are the most important thing. But it’s nice to be able to standout from the crowd a little so when people visit Jane’s the instantly recognise it, rather than it being just another white page with black text.
@kev @bshah @wzqtparor
when people visit Jane’s the instantly recognise it
I can understand the appeal, which is why my site’s nav link to the homepage says the site name (“Seirdy’s Home”) rather than just “Home”. Favicons can add some branding, and an <h1> tag can identify a page’s topic.
Links should be colored and underlined to stand out; since they stand out, they help personalize first impressions when skimming a page. If I see blue links to git repos and a PGP key, I know that the website belongs to a dev; if I see nav links to posts and notes, there’s a chance that this person is part of the IndieWeb.
I described setting up a simple layout that doesn’t require any significant mental resources for parsing in a recent update to my article on textual website best practices. The advantage of the simple textual layouts I describe is that they leave nothing in the way of reading, including the two seconds it takes to understand how to navigate a complex site. This makes it more likely that a reader’s first impression will be based on a site’s content.