A few weeks ago I decided to engage in a project of building a blog. I was looking for challenges, I wanted to build something of my own, without using some of these well known platforms like Wordpress, Blogger, etc. It was more about the journey and satisfaction of dealing with a domain that I was never very familiar with: front-end development.
The result is this website you are seeing now. Although it may look very simple (that’s always the goal!), there has been many things I’ve been through during this project. I would like to share with you the major practices and tools I learned the past weeks. This way I hope I can help you if you are also interested on building your own website.
I’ll be brief, most of the topics deserve their own blog posts, and I’m looking forward to write more about them in the future.
The great deal about this website is that it is completely static. I use Jekyll to generate, from templates, the whole content on every source commit. This means no dynamic content, no databases, no CMS; just plain html. I reckon this makes development much simpler because I’ve established just enough architecture to solve my problem.
Here comes the magic! GitHub Pages has a wonderful integration with Jekyll. Everytime you push code to your pages repository/branch, GitHub will build your site. You don’t need to keep stored your generated web site, because GitHub will do that for you behind the scenes. In the end you get continuous integration, deployment and hosting for free.
I guess Google Analytics is de facto standard for this kind of thing. If you know better solutions, I’m happy to hear.
Time to setup a custom domain name. I’ve long used juliaaano as an online identity and I hope one day I can tell you the story why. DNS is provided by Amazon Route 53. All I had to do there was to create a couple of CNAME entries here and there.
I’m proud to say this website is powered by AMP. I stumbled upon this technology by accident and got immediately really excited about it. Besides ensuring your pages load super fast, AMP helps you to build better html. Other than that, it’s a step towards the Progressive Web Apps movement. It’s been designed to delivery content to mobile devices, but I see no reason why I wouldn’t use with desktops.
Content Delivery Network (CDN)
Getting the html optimised to be delivered over the network is a piece of cake with Jekyll Compress Html.
It has been challenging to learn a few CSS tricks to get this website look decent in different screen sizes. I assume you should always have this in mind.
I hope this blog is friendly to people who are visually impaired. I’ve favoured HTML5 tags (header, nav, section, etc.) instead of divs and I’ve tried to use WAI-ARIA best practices.
Why not have a deterministic approach to how your text will look like? I’ve noticed that major websites use their own typeface. Although I didn’t want to license ($$$) a paid web font at this moment, I liked the idea to self host the free fonts my blog is using. The benefits are a stronger visual identity and a more predictable behavior, since you don’t rely on the browser picking up the font for you.
How awesome is Font Awesome with its endless number of icons. You can setup a private account with their CDN where you are able to do some customisations as well as configure to asynchronously load the fonts in your page. Awesome!
Nowadays favicons go beyond the scope of displaying a nice little image in your browser when a web page is bookmarked. There are specific icons for Android, iPhone and so on. Therefore, if you want to look good in all different platforms, make sure you define them properly.
Atom Feeds (RSS)
I keep a RSS-like feed of all my posts. The jekyll-feed plugin does that seamlessly for me.
Meta Tags (Open Graph/Twitter)
This becomes relevant when someone shares a page from your website in a social network. You need to define which image, title and text to display when Facebook/Twitter render the post/tweet card, for example. I’m using a combination of Open Graph and Twitter Cards.
Jekyll SEO Tag to the rescue.
A sitemap makes easier for Google to find my pages (SEO++). The plugin Jekyll Sitemap creates a new sitemap.xml file on every build.
I often test my site against the W3C Validator. It helps me to spot malformed html and stay compliant with W3C standards.
Fantastic tool to validate generated html output: HTMLProofer.
It’s been a nice learning experience to go through this road. As a developer, I wanted to be a bit more professional by building my presence online with my own hands.