I am lacking inspiration for today’s blogpost, so it is going to be a website update. Since launching at the beginning of the month I haven’t touched any of the code or infrastructure. Today I had some time to make a few minor changes.
User research results
I haven’t told a lot of people about the recent re-launch of my website, however the small group I did show it to all experienced the same “flaw” in the design of my landing page. As it turns out, the latest blog post, featuring a “wood” background pattern, is ignored and people click on the first blog post of the overview below. Not the behaviour I was looking for, so I decided to reduce the background effect and make the post a little more prominent.
HTTP/2 and a SSL certificate
What is HTTP/2 you might ask, or a SSL certificate? HTTP stands for Hypertext Transport Protocol, which is the protocol used to deliver pages from the server to your browser. HTTP/2 is the latest version of the protocol and the first major update of HTTP in almost two decades. The previous protocol HTTP1.1 was introduced to the public back in 1999.
Anyway, as HTTP/2 is what everyone is doing right now I decided to install it on my NGINX. The thing I forgot was that HTTP/2 requires a SSL certificate. SSL certificate? You sometimes see those green locks before a website url in your browser? Bingo, that’s the SSL certificate, it means the connections between your browser and the server is encrypted.
Letsencrypt.org/ offers free SSL certificates and by using certbot.eff.org it didn’t take long to setup. Now this website is a little bit more secure and faster.
For the next update, #3, I want to publish my /projects page, which features my Arduino “air quality” project. I am trying to apply for some subsidies and free sensors, and as it turns out having a website is a requirement.