Jekyll tutorial – all you need to know

In November 2008, Tom Preston-Werner, one of the four founders of the developer platform, GitHub, released the website generator, Jekyll

under the free MIT license. Written in Ruby, it accesses a template directory that contains a set of struc­tures and static text files – markdowns – of different formats. These determine the layout on the one hand, and the content of the web project on the other hand, and can be adapted in­di­vidu­ally for this purpose. The generator does not provide a WYSIWYG editor, but requires classic code writing. Therefore, the content editor, Prose, is re­com­men­ded, which sim­pli­fies markdown editing and is optimiesd for Jekyll.

Before changes to the code are in­cor­por­ated into the live version of the developed web ap­plic­a­tion, they can be viewed thanks to Jekyll’s own de­vel­op­ment server. The im­ple­men­ted rendering engine, Liquid, then converts the files into a static website that can be delivered with any standard web server. This auto­mat­ic­ally generates the HTML code in the back­ground when changes are made to the text files.

Here’s how to quickly create a Jekyll website:

But it’s just as easy to create graph­ic­ally more advanced websites:

Using Jekyll for blogs and other static web projects is a superior al­tern­at­ive to content man­age­ment systems, con­struc­tion kits, etc. for a variety of reasons. The main advantage of this solution is the sim­pli­city that can be seen in both the work with the website generator and the created projects. Thanks to the pos­sib­il­ity of foregoing a database, you save time and effort on the set up and con­fig­ur­a­tion. In addition, the necessary database access is no longer needed, which has a positive effect on the website’s loading time. The min­im­al­ist code, which is reduced to important functions and features, is present in all Jekyll themes, and con­trib­utes to good per­form­ance and easy project de­vel­op­ment and main­ten­ance. Compared to classic CMS, Jekyll generates a de­liv­er­able markup after each amend and not only when a user accesses a page.

Jekyll also scores well when it comes to stability and security. Since the web server only has to deliver text files, Jekyll’s potential for error is con­sid­er­ably lower than for websites that have several different com­pon­ents in­ter­act­ing with each other. And because no regular updates are necessary, the stable code framework also ensures high avail­ab­il­ity of the website in the long term. The security results from the fact that it doesn’t make much sense to attack Jekyll, since it doesn’t have CMS, databases, and scripts with dynamic elements (PHP, JavaS­cript, etc.).

While the highly-re­stric­ted code base is no obstacle for ex­per­i­enced de­velopers, newcomers will find it difficult to use the website generator. In the standard version, Jekyll does not have a graphical user interface, so in­stall­a­tion and setup must be carried out via the command line. Jekyll is also clearly inferior to many CMS and website de­vel­op­ment tools when it comes to the theme selection, since it lacks choice; other tools have hundreds or even thousands of design and layout templates. The same is true for the support, which isn’t very developed due to its small community and low dis­tri­bu­tion.

The following table sum­mar­ises Jekyll’s most important ad­vant­ages and dis­ad­vant­ages:

First, you need a GitHub account. To do so, go to the GitHub website and enter a valid email address, username, and password for your future account.

Then select the package you want to subscribe to – the free version for an unlimited number of public dir­ect­or­ies or the fee-based one for an unlimited number of private dir­ect­or­ies. Lastly, you can op­tion­ally provide in­form­a­tion about your pro­gram­ming skills and interests. You will then receive a con­firm­a­tion email from GitHub and can then activate your account by clicking on the link in it.

Now that you’ve created an account, you can log into GitHub. The user dashboard gives you an overview of the in­di­vidu­al dir­ect­or­ies, but doesn’t provide any in­form­a­tion at the beginning. To change this and to lay the found­a­tions for using GitHub Pages, you first have to create a new re­pos­it­ory.

Until now, the directory is a common GitHub project directory. To convert it into your web re­pos­it­ory, you’ve got several options.

• Start from scratch and build your website without a template using Jekyll. For in­form­a­tion on how to do this, see the official doc­u­ment­a­tion.
• If you use a ready-made Jekyll theme, it’ll be even easier to get started.
• The Jekyll example from Deploy Now is also a great starting place to create your website using the Static Site Generator.

During the theme selection, a con­fig­ur­a­tion file (config.yml) and an index page (index.md) are auto­mat­ic­ally generated. By default, the latter is the preview example for the selected Jekyll theme, which is why it is already available in markdown format. You can edit both the start page and the con­fig­ur­a­tion file by selecting the cor­res­pond­ing file and then clicking on the pen icon on the menu bar.

If the setup has worked as described in the previous steps, you can continue designing your blog or website. All the files you need for this purpose, such as CSS sheets or JavaS­cript codes, can be created using the 'Create new file' button. This way, you can also create ad­di­tion­al sub-pages for your web project. Via 'Upload files', it is also possible to upload files directly. You can either specify the location or drag and drop the file you want to insert.

Desktop Client

It is possible to manage a Jekyll website com­pletely via the GitHub web interface. With the desktop client, which is available for Windows and macOS as already mentioned, there is also an offline solution. If you have not yet installed it, simply click on the button “Set up in Desktop” in the created re­pos­it­ory and you will auto­mat­ic­ally be taken to the download page.

After you have down­loaded and installed the client, you can use it to make a local copy of your website. To do this, simply log in with your GitHub login and select the entry 'Clone a re­pos­it­ory' from the start menu. You now have the option of spe­cify­ing which re­pos­it­ory you want to clone. The storage location can be specified under 'Local path'.

You can access different branches in your re­pos­it­ory. These are in­di­vidu­al branches in the project that allow de­velopers to work on the code sim­ul­tan­eously or to focus on specific de­vel­op­ment areas sep­ar­ately. IONOS Deploy Now displays the in­di­vidu­al branches of the cloned re­pos­it­ory. As soon as you create a new branch, it is auto­mat­ic­ally displayed using Deploy Now. This way you can always keep an eye on your entire web project and the progress within the in­di­vidu­al de­vel­op­ment branches.