Top Reasons why we choose Jekyll

Jekyll-hero

Hello and thank you for reading our very first blog post from our new and improved website!

As you may or may be realise our website was built and is maintained using a static site generator - more specifically Jekyll the blog aware engine.

So why I hear you ask would we want to take step backwards and move away from a more traditional CMS setup? well the answer is simple and is just that we wanted to keep things simple. We are firm believers in simplicity in all aspects of design and development and any good engineer, designer, developer or logical vulcan will tell you that the less components/ parts to a machine or system the easier it is to produce, maintain and update it.

We went back to the drawing board when thinking and designing the site and actually asked the key question we ask our clients to ourselves which is how can we keep it simple? It quickly became clear that we don’t really need a complex system or CMS to manage the site as the main purpose of our site is showcasing what we can do and all other activities, project management for example can be moved to other areas/resources. This is why we trimmed down the site and cut out the fat to just get to the heart of what it is we want to say and show.

We also wanted a website which was super fast and so taking all of this into consideration a “static” site seemed like a good idea. I use the word static - somewhat loosely as you will notice the website is not completely a flat site with everything hard coded and I believe that the modern day engines like jekyll open a world of options in terms of having cool functionality whilst keeping the backend simple - so really it’s more like a halfway house been a flat static site and full CMS system and beyond.

Jekyll offers powerful support many features and plugins and as an example for code snippets:

def print_hi(name)
  puts "Hi, #{name}"
end
print_hi('Team')
#=> prints 'Hi, Team' to STDOUT.

Check out the Jekyll website for more information and be sure to see the Github repo at Jekyll’s GitHub repo.