Bridgetown

Jeeeeeekyll? No, Hugo!

Jeeeeeekyll? No, Hugo!

As I was writing about my transition from WordPress to Jekyll, I knew I had to prepare for another change. From a technical point of view, Jekyll is a fantastic platform: it is easy to program, has impeccable documentation, and works perfectly during the development phase, with a limited number of pages and test posts. But, as I experienced firsthand, when Jekyll is asked to handle a real site with hundreds of posts, performance drops dramatically and response times become unbearably slow (and quite embarrassing, too).
From melabit to melabit: why Jekyll?

From melabit to melabit: why Jekyll?

– Source: Jametlene Reskp on Unsplash. As I mentioned in my last post, leaving the WordPress comfort zone wasn’t easy at all. Going from focusing solely on writing something interesting – while a team of system administrators and web programming experts handled everything else – to having to do it all by myself was a massive leap.