Hi! I’m Dennis and I’ve been working at Linkbal as a software engineer since October 2017. In Part 1, we took a quick look at Jekyll and how to create and deploy a website to GitHub Pages. In this second and final part, let’s explore some of the customization features Jekyll provides us.
Layouts
In the previous example, you may have noticed the layout definition below in the front matter:
layout: post
While the markdown file provides the content of a page, the structure and appearance are defined in the layout file. We can create our own layout files, but because we are using an existing theme, we can customize the theme’s layout files instead.
First, let’s copy the layout files from the theme’s folder to our project (the specific folder to copy from will probably be different for you as it depends on the version of the packages installed).
Now that we have an idea of how layouts work, let’s customize our website a little bit.
Includes
In the default.html layout file, we can see the line below:
{%- include header.html -%}
Because the default.html layout includes the header and all other layouts uses the default layout, it is obvious that all pages in our website includes the content in header.html.
Let’s take a look at the contents of the header.html file. Because it is also part of the minima theme, we need to copy this file as well:
This include file is responsible for displaying the website header and shows many variables that Jekyll make available for us, as well as filters provided by the Liquid template language.
The line above, for example, shows the site.pages variable. It is an array of Jekyll’s Page variables (you can check the list of attributes a Page variable contains in Page Variables). Any .html or .md file in the root folder or a new subfolder that contains a front matter will be part of the site.pages variable. Then, we execute Liquid’s map filter on the site.pages to get an array of the paths of those pages.
The next line creates a variable called page_paths. It is assigned the value in site.header_pages, but can also be assigned the value in default_paths in the case the former does not exist, what is possible with the use of Liquid’s default filter. We are going to come back to site.header_pages later.
{%- for path in page_paths -%}
{%- assign my_page = site.pages | where: "path", path | first -%}
{%- if my_page.title -%}
<a class="page-link" href="{{ my_page.url | relative_url }}">{{ my_page.title | escape }}</a>
{%- endif -%}
{%- endfor -%}
This last snippet iterates over the page_paths variable created before and creates a link in the header for each page that has a title (defined in the front matter).
To test what was just shown, let’s create a new page notes.md in the project’s root folder. Now, let’s add the content below to the new file:
If we refresh our website, we are going to see a new “Notes” link in the header. Add another page called contact.md to the root folder with the content below:
A new link is created as well. The problem is that the links are created in the alphabetical order, but we may want a different order to put the “Contact” page last, for example. In that case, we can use the site.header_pages mentioned before. This currently does not exist, but we can easily create this variable by adding the following lines to the _config.yml file:
header_pages:
- about.md
- notes.md
- contact.md
You will notice the change will not be reflected immediately and will require the server to be restarted. After that, the header will look as expected.
The Resulting Header
Collections
Now, we are going to explore Collections that are a great way to group related content. Let’s use this feature to implement the “Notes” section in our website.
First, add the following content to _config.yml:
collections:
- notes
Then, let’s create a _notes folder and add 2 files in it. The /_notes/note1.md:
---
menu_title: Note 1 Menu Item
title: Note 1 Title
---
Note 1 content
> A nice blockquote
A **formatted** line of *text*.
And the /_notes/note2.md:
---
menu_title: Note 2 Menu Item
title: Note 2 Title
---
Note 2 content
> A nice blockquote
A **formatted** line of *text*.
Now, let’s create a custom layout listing all our notes. It will be the /_layouts/note.html file and will contain the following content:
I added the styles directly in the layout, to keep things simple, as that is not the main focus of the article. As Jekyll has built-in support for Sass, please refer to the Docs to know how to manage your stylesheets.
You can see we were able to access our notes through the site.notes variable and even use a custom variable background we added to the front matter.
Restart the server and we can now access those notes in the /notes/ path.
The Notes Page
The files we created in the _notes folder does not generate corresponding files in Jekyll’s build process. If you need, you can change this behavior as shown in Add content. This would generate files such as /_notes/note1.html in the build output. In our example, we could, for example, display only part of the content of the notes in the list and link each note to a page where the user can see their whole content.
Data Files
In this final section, we are going to take a quick look at Data Files. It allows us to create files with custom data to be used in our templates. Those can be YAML, JSON, or CSV files. Let’s do an example to illustrate its use.
This is enough to make our data accessible in our templates in the site.data.contacts variable. So, we can now edit our /contact.md file with the following content:
As we could see, we can use Data Files to remove repetition in our pages by separating data and configuration. A practical use is illustrate in Navigation where it is used to create custom navigation for a website.
Conclusion
In these article, we could learn and practice basic Jekyll concepts such as Layouts, Collections and Data Files. There are plenty of content was not covered in the articles, so I highly recommend reading the documentation, as it is very well written and easy to understand.
