I always love websites with custom fonts that don't render correctly. When I see a website with great typography, most of the time it turns out to be Georgia or Arial, or sometimes even Timew New Roman (which his a good font, but simply overused). I've yet to see a custom font that reads better than correctly applied default fonts.
When a site like kernel.org goes online with a broken font, something must be fundamentally wrong in the world of programmers and people generating content for displays. What would be the situation like, if we were printing millions of books with 20 dpi technology? Would this be ignored by the masses and people who are annoyed by the eye-hurting results would be trolls?
We should see this as a clear (cough) signal, that it is time to start some major broken-font-campaign - more and more web developers seem to be so overloaded with CSS and JS framework learning, they totally forget about the most basic things - IMHO it is still the first and most noble duty of a real webdev to make a site nicely readable on all displays.
This annoying font-disease must be taken very seriously - it is ignoring the most important aspects of life: health. I feel offended if somebody forces me to read a website with such a broken font - it hurts my eyes, and as a computer guy I need my eyes for work, so it is a serious attack.
I was humbly accepting it as a personal disability for years, that I needed WinXP fonts on every Linux distro to have a satisfying font display. But I kept wondering about how the creators of thousands of Linux tutorial screenshots could not realize that they were looking at a broken font and destroying the functionality of their most important input devices.
Luckily in the last years it got much better on Linux, but then came the iFlood, Win7, and finally the ultimate weapon of ophthalmologists for generating an endless income stream: webfonts.
Now I am confronted every single day with websites with broken fonts. This is a serious regression and every web designer and every programmer involved in font rendering code should stop working on anything else until this problem is fixed.
Yes, I know there are many reasons for this problem, it is not only the web developers - anyway, please let us fix it now.
It would be nice if the people who encounter these text-rendering problems mention what setup they use.
Probably you are using some Linux distribution with misconfigured freetype.
Are you able to realize that it is, of many options you have, the dumbest possibility to just burp a simple "it works here". Would you answer this on a bugreport?
I assume, it was an ironic answer, in this case I congrat you for holding the mastership of the highest art of subtile trolling, very inspriring.
In fact you are simulating the typical xtreme-dumb answers perfectly, that are received on "bad-font-whining" regularly - this is exactly the reason why we need a major bad-font-campaign, because this is not only a technical problem, but the roots seem to be hidden in a deeper socio-techno-cultural level of our brains - that "systems are getting too complex"-stuff leads in the end to the human brain regressing strongly in certain areas to amoeba-state.
Those of us in the #pelican IRC channel had a rousing cheer and virtual clinking of the glasses. :^)
If anyone has questions about Pelican, please feel free to ask here or on our IRC channel.
Edit: And if you're going to PyCon in Santa Clara, CA this month, hit us up on Twitter (@getpelican) to get info about our pre-PyCon meetup.
With this in place, you should be able to populate your site with pages (e.g., /content/pages/{index.md,about.md,portfolio.md,contact.md,etc}) without any chronological blog content.
My webspace could not run ruby so i took the approach 3 times to write a static site generator. For me, i would take that route again. I have my favourite editor to write stuff and who the hell needs a database for a blog or something small?
I use the last system i wrote still, but I take notes with it and save images to a local repository.
OTOH if you have a database, scaling's going to be a pain.
Granted, it's not "complicated" but it's also the same colors...
Edit: Smashing Mag is mentioned on Pelican blog: http://blog.getpelican.com
Yeah they have more style rules, but disabling them doesn't visibly change anything so they're the defaults.
1. I typed in www.kernel.org
2. I looked for the new kernel on the page that loaded.
3. I clicked on the link and my download started.
On the new kernel.org:
1. I type in www.kernel.org
2. I look for the new kernel on the page that loads.
3. I click on the link and my download starts.
Conclusion: Good job. You made the site look more modern without disrupting the most common workflow.
The only 2 suggestions I have are
1. The entire container for "Latest Stable Kernel" should be the hit point; yes, all of it, including those words.
2. When I hover over the tabular download links, my eye can get confused on which row I'm on. Something purely css and really subtle would alleviate that; for instance:
* changing the row background color
* changing the color of the font for the row
* prepending a UL style dot to the LHS of the row
* making the bordertop and borderbottom more distinct
* underlying or italicizing the words
* etc...
any of these things would help and I'm totally agnostic to what is done; it would be a quick fix that would really make the thing less prone to human error.
https://www.kernel.org/theme/css/main.css
that style was made on 2009!!!
Please somebody fix that fonts
