jekyll-nagymaros

Nagymaros is a Jekyll theme designed for conferences, workshops, meetings, and similar events. It has a simple and intuitive structure featuring four pages that provide key information about the event:

An index, meant for basic details and links to external sources, such as submission systems.
A program, allowing for single or multi-day schedules and color-coded event categories.
A map of conference locations, customizable with markers, areas, and tooltips.
An alphabetical list of contributors, with optional roles and email addresses.

The theme is based on Bootstrap 5, which makes it mobile-first and fully responsive. Body text is set in Inter, a clean sans-serif typeface that guarantees readability at small screen sizes. A slab-serif typeface, Zilla Slab, is used instead in display headings. The layout is adapted from jekyll-conference-theme and remains quite similar to it, but compared to this theme, Nagymaros aims to be simpler and easier to customize.

See the demo to find out what the theme looks like.

Installation

The theme can be installed as usual by cloning this repository and editing the files. However, it is far more convenient to install it as a gem, in which case all the files you do not want or need to customize remain hidden from view, but will still be read and processed during build.

If you choose to install the theme as a gem, your site should include at a minimum the following files:

.
├── 404.md
├── _config.yml
├── contributors.md
├── _data
│   ├── contributors.yml
│   ├── index.yml
│   ├── locations.yml
│   └── program.yml
├── Gemfile
├── index.md
├── locations.md
└── program.md

To install the theme, you can then add this line to your Gemfile:

gem "jekyll-nagymaros"

And this line to _config.yml:

theme: jekyll-nagymaros

The easiest way to set up a new website in this way is to clone the contents of the demo folder. This provides a working set of files to get you started.

After you are done creating the basic files, create a local gem library and run bundler:

bundle config set --local path 'vendor/bundle'
bundle install

To customize hidden files, you can create new files with the same names and paths. For example, to change the layout of the index page, you can create a _layouts folder and a file index.html within this folder that contains your custom code. During build, Jekyll will give priority to your files over the theme's.

Usage

Core customization occurs in _config.yml. Aside from the usual configuration variables, you can set a value for copyright, which corresponds to the name of the copyright holder in the notice within the theme's footer. If no value is provided for this variable, the whole copyright notice is suppressed (this is the default). Finally, you can set a value for indexing, which tells search engine crawlers whether to index your site. The default value is false, and in this case the following code is included in the head of every page:

<meta name="robots" content="none">

If you set the value to true, however, the above code will not be included, crawlers will be allowed to index your site, and Jekyll will populate the head of every page with SEO tags through the jekyll-seo-tag plugin.

Data that appears in the theme's four default pages must be configured via YAML files located in the _data folder. See the corresponding files in demo/_data to understand how to write your own YAML, or better yet, clone these files and edit them.

The order of appearance of pages in the theme's navigation bar is determined by the value of navorder set in each page's front matter. For example, setting navorder: 1 will make the page appear first in the list. Note that a page will only appear in the navigation bar if the navorder variable is set, so it is possible to hide some pages from navigation simply by not giving this variable a value.

Customizing the CSS is possible by creating a file _sass/_custom.scss. You can use this both to define new styles or to overwrite the theme's defaults. The file will be automatically compiled during build.

For convenience, customization of the theme's color scheme is also possible via YAML. In this case, create a file called skin.yml in your _data folder and assign new colors from the Open Color library to various HTML elements using the color-number convention. Here is an example:

a:
  color: blue-7         # links
  hover: blue-9         # links when hovering
body:
  bg: gray-0            # background
  color: gray-8         # body text
btn-primary:
  bg: blue-5            # primary button
  color: gray-0         # primary button text
  hover: blue-7         # primary button when hovering
  disabled: blue-3      # disabled primary button
btn-secondary:
  bg: gray-4            # secondary button
  color: gray-0         # secondary button text
  hover: gray-6         # secondary button when hovering
digit:
  bg: gray-3            # background of digit on 404 page
header:
  bg: gray-4            # background of navigation bar
index:
  bg: gray-2            # background of index container
navbar-brand:
  color: gray-8         # website name in header
  hover: gray-9         # website name in header when hovering
nav-link:
  color: gray-7         # navigation links in header
  hover: gray-9         # navigation links in header when hovering
text-muted:
  color: gray-6         # light text
  hover: gray-9         # light text when hovering (if link)

The variables are named after the HTML elements they style. The colors to which they are set in this example are actually the theme's defaults. If no value is provided for some variables, or if _data/skin.yml does not exist, the theme assumes the color scheme above.

Credits

This theme builds on the following projects:

Bugs

If you find any problem using the theme, please open an issue.