At the time of writing, Jekyll’s performance is still actively being worked on by the Core Team for an upcoming version 4 release. One of the main complaints about Jekyll for users is often the build times of larger websites. I want to take this opportunity to see just how much I can expect to improve my current site’s build times by using the latest master branch. Sound good? Let’s get started.
Reaching an international audience means having international content. Having your content available in multiple languages is great for maximizing your potential audience. On top of that, ensuring your multilingual site’s content is easy to edit is especially important, to enable translators without development experience to work effectively and reduce the incidence of translation errors. In this post, I will explore how to set up a Jekyll site to support multiple languages, and use Forestry to provide an interface for creating translations.
Back in April we announced a feature that we believed was a game-changer for static site content managers. Blocks was here to introduce a way for you to put together sites using pre-composed site snippets inside Forestry. While we did our best to show you how to set them up and give you an idea of how powerful they could be, we noticed that getting to know Blocks and figuring out how to set them up from scratch wasn’t as self-explanatory as we had hoped.
What’s new in Jekyll 3.8 Jekyll 3.8.1 was released on the 1st of May 2018, just two weeks after 3.8.0. The project has come a long way since I last wrote a Jekyll update on Forestry. Olivia is now Jekyll’s new Lead Developer since Parker Moore decided to step down after four years leading the project. So what does Jekyll bring us this time? Performance optimizations Large sites containing a huge amount of posts are going to see a massive reduction in their total build times especially if they are doing multiple calls to the where filter with the same input and property parameter.
Choosing the right tools to build a website isn’t easy these days. There’s just too many options! Building a static site is one of these options, which comes with many advantages like top-notch security, blazingly-fast performance, and reduced costs. When it comes to building static sites, the two leading solutions right now are Hugo and Jekyll. So the question is, which is right for you? To answer that question, we’ll take a look at the features, speed, and extensibility of each, looking for the pros and the cons of both generators.
When I view an error log from Forestry I see: Could not locate Gemfile or .bundle/ directory What this error means Gemfiles include a list of project dependencies and where to find them. Bundler is a dependency manager for the Ruby programming language that can read Gemfiles, resolve the dependency graph and install those gems. Jekyll is a ruby application and can use Bundler to manage your project dependencies. Forestry requires that your Jekyll projects contain a Gemfile at the root of the repository.
For this week on Frontend Friday, we’ll be covering how to set up lightning ⚡️ fast search for your Jekyll site using Algolia, the SaaS (Search as a Service 😉 ) provider. Algolia’s self-proclaimed claim-to-fame is that they are “the most reliable platform for building search into your business,” and honestly, it’s hard to disagree. Forestry’s search is powered by Algolia (just try searching for Algolia in the search above!
We’ve also compared Jekyll & Hugo features across 6 dimensions. Learn More Hugo and Jekyll are the leading static site generators according to StaticGen.com, and both supported by our CMS. We’re often asked which tool performs better so we decided to do an analysis. TL;DR We ran two tests to measure build times with Hugo and Jekyll. The basic test used the default installation of Jekyll and Hugo to build sites with 10 posts,100 posts, 1,000 posts and 10,000 posts.
Jekyll 3.4.0 was release on the 27th of January 2017 with some noteworthy enhancements that I’d like to share with you. So what’s new? Add connector param to ‘array_to_sentence_string’ filter array - The list of strings to join. string - A string can be any text inside quotes. In this example I will use Jekyll tags. connector - The word placed before the last word in the array. The default connector Jekyll uses is the word “and”.
When it comes to the Internet, content is king. A site that has well written content concisely tells the story behind a brand, helps to inform customers about a business’ products or services and helps guide a user navigate to the information that they seek. I’ve worked with various organizations in helping them choose the technology that is used to publish content onto their sites. When it came down to making a choice, the publishing platform options were often slimmed down by the need for non-technical users to easily publish content.