As I wrote in my previous blog article, recently I became quite hooked by the web and all that’s orbiting around it.
This time I’m going to show you a simple project developed following Jamstack guidelines:
- HTML5 for responsive and accessible markup
- CSS3 to lay out the presentation
- Hugo to statically generate the content
- GitHub for source hosting
- Netlify for content hosting and (fast) delivery
In the past I’ve been relying on a free offer from VisualCV to host my curriculum vitæ online. Recently though (end of 2019) they changed their terms and removed the free offer, so no more CV online for free.
For a while I wanted to manage my CV in a more flexible way than VisualCV or any other job platform like LinkedIn offer. Almost at the same time of VisualCV move I stumbled upon this great article on CSS-Tricks by Ali Churcher, I liked it quite and made me think I had no more excuses to procrastinate.
I thought a while about how to best approach the issue and then put in practice my new acquired skills as a web developer (while having quite some fun in the process).
CSS-Tricks’ article is showing flawlessly how to setup the layout, and that’s exactly what I’d expect from an article by CSS-Tricks, but to me it is missing a few key features to make it really shine.
One feature I definitely want to have is a comfortable way of managing the CV content. In the end what’s the point of having it online if I can’t keep it up to date with ease?
In practice I just want to open my IDE, edit some Markdown, run
git commit && git push and have the new changes deployed online asap.
To add my features I pair the cited HTML5+CSS3 tricks with Hugo and its powerful content management features.
A couple of more clicks in the Netlify app (plus a few new DNS records in my
l3x.in domain) and everything is live at https://cv.l3x.in, replacing the old HTTP redirect to VisualCV.
I take the chance to highlight a couple of more things:
- differently from the layout proposed by CSS-Tricks, I opted for keeping the header (name, title and photo) outside the main grid. To me it makes more sense to have it decoupled from the content (i.e. from the grid) because the likelihood I’ll put it anywhere else than the top is close to zero, and having picture and text box swap relative position with
display: flexis trivial
- in layouts/partials/head.html there are a few tricks to make the site load faster, thanks to Google Insights. At the time writing the live site scores above 99% for both mobile and desktop
- Hugo makes it fun to add all sort of functionalities, for example the copyright and last modified info in the footer
- another cool thing when using Hugo, you might think of partials as sort of web components, that might help structuring your markup in a way clean and easy to maintain
I’m quite happy with the results and I don’t think I’ll change the layout for a while (I always need to improve the content but that’s out of scope eheh).
I list here a few of the possible improvements that came to my mind so far:
- I’ve used SCSS (in assets/ folder) to keep the style DRY but I’m pretty sure there is a lot of room for improvement
- The scroll to top icon should appear only after some scrolling, I don’t know if that’s possible in pure CSS alone and I’d like to keep the project JS free. If you know how to do it in CSS please let me know, thanks!
- The footer could appear at the very end of the viewport even when content is not filling up the page completely (e.g. https://cv.l3x.in/programming/). It should be easily done with flexbox, I’m ok as it is for now
Feedback always welcome
I hope you like it and hopefully find it useful too.
As usual I’m more than happy to hear what you think, especially if you have something critic to say about it: for sure it will hurt a bit but so far I don’t know any better way to improve my skills ;)