Building static sites with Contentful and Ruby
Not every web project needs a complex tech stack behind it: sometimes a handful of static pages is just enough. Blogs, personal websites and landing pages are the most common examples that come to mind.
For the Ruby world, we've built Contentful integrations for Jekyll and Middleman, which conveniently happen to be the most popular static site generators.
Why static, really
A quick recap on what we really like about static sites and what some of the drawbacks are (if you want to go into little more details, see our CMS for static sites guide):
Pros
No databases. Host the entire site in plain HTML+CSS+JavaScript.
It's fast. No server processing means that a site can be fully cached.
Inexpensive hosting. Serve your site from mostly anywhere at surprisingly low prices. (There are free hosting providers, too.)
Cons
Content remains the same. Every content update requires a new build and deploy.
No server, no logic. Since there is no server, any kind of extra logic (authentication, logging, and so on) needs to be handled by an external service.
Static but dynamic
Normally running a static website means having to manage content manually – for instance, in plain-text, Markdown-formatted files – which is probably not the most elegant approach in the world. Contentful fixes this by offering an authoring environment that feels like an ordinary CMS (without the noise, though): write your thoughts in the Contentful Web App, enjoy the speed and simplicity of a static setup. It's a clear win-win.
Integration for Middleman
Add
contentful_middlemanto theGemfileand add this block to theconfig.rbfile:
Run the
contentfulcommand:
You're done! All your Contentful data is in the
datafolder, and can be accessed from the templates.
If curious, you're welcome to take a look at some more detailed tutorials.
Integration for Jekyll
Add
jekyll-contentful-data-importto the:pluginsgroup in theGemfile, and add this block to the_config.ymlfile:
Run the
contentfulcommand:
You're done! All your Contentful data is in the
_datafolder, and can be accessed from the templates.
If curious, you're welcome to take a look at some more detailed tutorials.
What's next
As I said before, this is not the perfect setup — there are some cons to it. Nevertheless, it's a good fit for a lot of use cases, which I encourage you to try and explore.
In a future post I'll show how to automate this process using webhooks and CircleCI to have a free automated deployment service. Fun times ahead!
