This PR does a bit of clean up and modernization of the Kinto website. I tried to keep the design/content exactly the same, except for the few small tweaks mentioned below.
Removes support for Internet Explorer. It's 2020, and the modern web is a wonderful place. Dropping support for Internet Explorer allows us to use nice things like CSS variables and CSS grid.
Replaces Font Awesome with an inline SVG containing just the icons used. Font Awesome clocks in at 77 KB, whereas the inlined icons only increased the size of index.html by 4.3 KB.
Replaces the webfont with a reasonable default font stack. This saved 20 KB, and also increases perceived load time since the browser can instantly render text as opposed to waiting for the webfont.
Removes the nav link to the blog and replaces it with a link to the documentation. The blog only has one post, and it's a bit strange to give it such a prominent location. The blog link has also been removed from the footer (but the post is still there, so anyone who has an old link should still be able to get to it).
Changes the CTA in the hero to "Install Kinto" as opposed to a link to the section that's immediately under the CTA.
Adds a link to the tutorial in the hero.
Replaces the raster code screenshots with SVG versions. These are over 50% smaller and look perfect at any resolution.
Adds a sample curl invocation (fixes #12).
Fleshes out meta tags with support for Twitter cards.
Replaces the vast majority of the CSS with a modern, CSS Grid powered version.
The Numbers
This new version uses 62% less bandwidth, loads 24% faster, and makes 41% less network requests. It's now one HTML request, one CSS request, and eight image requests.
This PR does a bit of clean up and modernization of the Kinto website. I tried to keep the design/content exactly the same, except for the few small tweaks mentioned below.
You can preview the site here.
Highlights
index.html
by 4.3 KB.The Numbers
This new version uses 62% less bandwidth, loads 24% faster, and makes 41% less network requests. It's now one HTML request, one CSS request, and eight image requests.
It also scores a perfect 100 in Lighthouse.
Potential Future Improvements
I wanted to get this out there for feedback, but there's a few more things I have in mind: