Jekyll is my new CMS, a static site generator actually. But, it does work the old Joomla way.

You can create standard blog posts using categories, and have permalinks the way you want. My main reasons to switch from Joomla to Jekyll are faster page load, easier content management, and love of going static again.

The way we are evolving to live on our planet, one day we’ll destroy it ourselves. That day, (you can say doomsday) there will be nothing but plain texts. I think, then a static website will be much simpler to decode compare to a site which uses dynamic languages and having several databases.

So far, I tried to customise minima (standard theme) the way I want to see it. But, I think, I’ll need a template of mine. I better start thinking about this seriously. What was the toughest issue for me? It was a bit time consuming setting disqus. In Jekyll 3.3, disqus comments are enabled by default in production mode. You just need to write your shortname in _config.yml file. Unfortunately, this didn’t work for me due to some sort of logical error.

I didn’t have that much time to tinker with the code and needed disqus to work right away, so I simply removed the liquid code from disqus_comments.html file which required disqus to work in production mode.

  if page.comments != false and jekyll.environment == "production"
    if site.url
      assign disqus_url = page.url | prepend: site.url
        elsif site.github.url
      assign disqus_url = page.url | prepend: site.github.url

And, it just worked like charm.

Here, I do not recommend offical method of disqus implementation on Jekyll because it would enable disqus on each and every page/post of your Jekyll website. And, each time you will have to write comments: true/false in your YAML front matter to enable and disable it.

Now, you have an issue: disqus creates a copy of comments whenever it loads on a page (here in my case, now Jekyll is loading in production environment). To avoid this, just go to your disqus advanced settings and limit disqus code to load on your domain.

That’s it. You hacked it!

No matter what, you’ll need to tweak a little code of any framework to suit your needs. After all, Jekyll is way better than any other framework to publish websites. I hope, I will spend next one decade with Jekyll.