Is love at first sight even a thing? I believe it is! And our new site is a result of that love.
We’ve started thinking about new site quite some time ago but from the start we had some ideas of what it should look like. Here’s what we wanted:
- super fast loading time,
- scalable architecture,
- reliable hosting,
- easy to develop and flexible.
The decision to go static was obvious, but just having a static HTMLs won’t cut it as we wanted blog to be a major part of our site. The next decision to make was to pick a static site generator. Of course, there were a few popular candidates on the horizon such as:
But let’s face it, with our background, and the fact that Ruby has been dear to our hearts for years, the choice was obvious that it had to be Jekyll. We also, however, provide web development services with use of many various Static Site Generators and other tools that are part of Jamstack architecture.
What is Jekyll?
Now what is Jekyll exactly? Jekyll is a static site generator written by a co-founder of Github, Tom Preston-Werner. Blog focused generator, super easy to operate, gives us power of Ruby in form of plugin system for creating custom content for our site, and many more. You can read about that on the Jekyll site.
CMS for Jekyll: Netlify. Why?
At first, we wanted to use Jekyll exclusively with jekyll-admin gem and just host it on our server, but after rethinking this a little we opted for hosting our site on Netlify, as it gives us some really cool perks. To name a few:
- Continuous Deployment - hands free project deploying based on github/gitlab/bitbucket activity.
- SSL - Out of the box HTTPS for default domain, you know what not having that means today, right?
- Redirects - that one was big for us, as lot’s of old site urls were long and not so SEO friendly, so we had to change them, and redirects are a blessing. Git gateway - GitHub/GitLab accountless access to repo? Aww yiss!
So choosing Netlify seemed like a good idea though there still was the case of jekyll-admin, it wasn’t exactly what we needed. Fortunately guys from Netlify also created Netlify CMS and after reading through the documentation, we thought “yeah, this is what we want”, and what exactly was that we wanted? Well, let me tell you.
What’s this Editorial Workflow all about actually? It gives our content creators ability to write content (posts, case studies, testimonials and such), request changes, edit it and then, when it’s ready, publish it. Thanks to the way NetlifyCMS implements that, each post, testimonial, etc. can be published without any involvement from a developer, but the cool thing about this is that before going live our changes can be previewed on a separate site which is deployed by Netlify out of the box.
To fully utilise Netlify and for Editorial Workflow to actually work we have to first make NetlifyCMS work and making that happen can’t be simpler. We just have to add
In my opinion widgets are the main awesomeness of using NetlifyCMS. They give use power to make any page editable through the admin panel, pretty much anything can be edited there. It gives our content creators an ability to set name of url, title and description, add images, change layouts, and anything else you may think about.
Jekyll & CMS: Is That All?
Of course not, there are many more features that Netlify along with NetlifyCMS offer that we haven’t used like Forms, Prerendering for single page applications, Split Testing, Lambda functions for thoese who want more, we can even create custom Widgets and remember that features are constantly added so you can check and test (or use) some Beta Features. You can check all that on Netlify Documentation page, as well as Netlify CMS Docs page
Looking for Netlify alternative? You can go to our comparison of 15 Headless CMS and learn more about NetlifyCMS and other headless Content Management Systems.