Bumbleflies homepage

made possible with

• jekyll
• agency-theme

Build

Install bundles

bundle install

PermissionError

When using bundler 2.4.x, the silent permission upgrade feature got removed and bundler can't write to its cache anymore: rubygems/rubygems#6272

Retrying download gem from https://rubygems.org/ due to error (4/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.1.0/cache/ffi-1.15.5.gem`. It is likely that you need to grant write permissions for that path.

to fix this, create a user writable directory like so

mkdir ~/.gems_cache
bundle config path ~/.gems_cache

Build site

bundle exec jekyll build

Serve locally

bundle exec jekyll serve

Purge css and font

cd _purge
./purge.sh

new font awesome tags must be added to purge-fa.py

Conventions

Location of markdown files

Pages are located in _pages directory

Template construction

Every page needs to have at least

---
layout: <layout>
namespace: <name>
permalink: <url-name>
permalink_en: <url-name>
nav_highlight: <navigation title to highlight (referencing i18n-key)>
title: <page title (referencing i18n-key)>
---

• layout is the template to be used to render the page
• namespace is used to resolve translated url when used with {% tl <namespace> %}
• permalink and permalink_en denote the url-names of the site in different languages
• nav_highlight references the same i18n-key which is used in navigation in order to highlight when the page is selected
• title is the i18n-key to resolve the title

i18n

The page uses i18n in languages defined in _config.yml and resolves key by looking them up in _i18n directory.

Translate keys

Key are resolved using

{% t key.to.look.up %}

usually, keys aren't resolved directly from i18n files, but from page variables.

Example

Given you have a markdown file like this

index.md

---
layout: default
title: pages.home.title
----

and your translation file contains a structure like this

en.yml

pages:
  home:
    title: My Home

in order to translate the title for example in the title, you have to use the translation function like so

_layouts/default.html

<title>{% page.title %}</title>

In such a way, the defaulttemplate can be used for all pages, which specify a title i18n-key

Chaining

This comes with some limitations: this statement cannot be used in order to chain variables, linke for example

{% t key.to.look.up | markdownify %}

This will produce an error like

Missing i18n key: key.to.look.up | markdownify
Using translation '' from default language: de
Liquid Exception: no implicit conversion of nil into String in /_layouts/<layout>.html

In order to fix this, you need to use the capture function

{% capture translated_content %}{% t key.to.look.up %}{% endcapture %}
{{ translated_content | markdownify }}

Navigation

The navigation is constructed from navigation template file, also containing i18n lookup keys.

Next Event

The information text for the next event can be found in the i18n folder in the next.md file

Background image

Background images are tricky: they are introduced via CSS, which means they are accessible by simply putting a css-class attribute to the item. But for generating the code, it's a mess. The process of adding a new image to a page is as follows:

1. Add a new yaml-entry for the image to the yaml style file
   • accceu-image: "/assets/img/accceu-header.webp"
2. Transform this yaml variable into a scss variable in the bumble.scss preprocessor
   • $accceu-image: "{{ site.data.style.accceu-image }}";
3. Create a new style definition in the header images scss
   • &.accceu-image { background-image: url("#{$accceu-image}"); }
4. (optional) Add a preload entry to the head html
   • <link rel="preload" as="image" href="{{ site.data.style.accceu-image }}" type="image/webp">
5. Now you're ready to use the image class in your templates
   • header: image-class: accceu-image