In this post, I’ll introduce a technique for creating navigation for a Jekyll-powered website. After working through the basic example, I’ll show how I’ve extended it for use in a multi-lingual site.
In these examples, I’ll use data files to hold the list of navigation items, then a Liquid
for loop to build the navigation list. Jekyll data files hold additional data for Jekyll to load while generating your site. They’re a great place to store strings, common URLs, and more.
The Basic Nav
First, create a list of items in
_data/nav.yaml, each with ‘text’ and ‘url’ properties to hold the necessary information.
Now that the data file is ready, assign the current page’s URL to a variable. “Current page” in this context refers to the page being processed during Jekyll’s build.
So as Jekyll iterates through the pages in the site, each page’s URL will be captured and used for building the rest of the navigation.
One Small Problem
The home page doesn’t need the ‘home’ link, so the loop should skip over the first list item when Jekyll builds the home page. Liquid provides a handy
offset property, available inside
for loops, for which this is a perfect use-case.
To set the
offset, test whether or not the current page is the home page. If it is, set the offset to 1, which will skip over the first list item (‘home’). Otherwise, let the loop start at the first item, as it would by default.
Now that all the pieces are in place, add the loop to build the navigation list.
for loop to iterate over the items in
site.data.nav, comparing each item to the current page’s URL. If the item matches the page’s URL, mark the navigation item as “current” for styling purposes.
The Multi-Lingual Nav
I’m in the process of building a website that needs to be translated into Spanish, including the navigation, which proved to be a bit tricky. Here’s my approach to a multi-lingual navigation, which builds off of The Basic Nav idea above.
The Data Files
For this site, the data files also serve to hold translated strings. As such, there are two data files:
other will be used to tell the loop which site is being built. More on that later…
As with The Basic Nav example above, the current page’s URL needs to be captured for use in the loop.
Next, tell Jekyll which data file to use by checking the URL for the language-specific directory. If the URL contains the directory name — in this case ‘
/es/’ — use the translated strings. Otherwise, use the english strings.
For the offset, the only difference is checking for the translated home page URL in addition to the english home page URL.
The Problem, Part Deux
As with The Basic Nav above, the home pages — both the translated site and the english site — shouldn’t show a home link. We solve this by conditionally setting the
offset. But on the home page, the link to the translated home page should show.
So the loop essentially says, for items in this list, if the item is not the home page, skip the translated home link. Otherwise, build the list normally. And, of course, the list may or may not be offset, based on the page’s URL.
In this post, I introduced a technique for creating site navigation using Jekyll data files and Liquid conditionals and loops. I then showed how I’ve extended this approach for use in a multi-lingual site I’m building. I hope you’ve found this exercise helpful.