This document provides instructions about the ALEPH website. Please start by reading (at least) the How to update the website section.
Table of Contents:
- Read the instructions you find in the Common operations section to understand how to implement your change (e.g., add a new publication, update a project). You may try out your change by following the instructions in the How to try the website locally section;
- Create a dedicated issue and make a pull request to the repository. It is a best practice to avoid pushing changes directly into the main branch;
- The Content Managers (
sberlato@fbk.euandaltomasi@fbk.eu) will check your modification and merge it into the main branch; - The website will automatically update accordingly.
- clone the repository;
- install rvm (https://rvm.io/rvm/install) (you may need to reboot your computer);
- install ruby with
rvm install ruby 2.7.2; - run
bundle install; - run
bundle exec jekyll serve;
- if the above command does not work, delete the
gemfile.lockfile, runrvm install ruby 3.2.2and againbundle exec jekyll serve;
- open the browser at
http://0.0.0.0:4000/;
Sample installation script in Ubuntu 22.04:
sudo apt install software-properties-common ruby-dev ruby-bundler
sudo apt-add-repository -y ppa:rael-gc/rvm
sudo apt-get update
sudo usermod -a -G rvm $USER
source ~/.bashrc
sudo apt-get install rvm
rvm install ruby 3.2.2
bundle install
bundle exec jekyll serveCommon images can be found in and used from the folder assets/images.
Custom images or attachments should be uploaded in the assets/areas folder. Please keep material properly organized (e.g., using subfolders).
This website is composed of several markdown (.md) pages that are automatically compiled and converted to HTML whenever the repository is updated (e.g., with a new commit).
On top of many pages, a YAML preamble (that starts and ends with ---) defines metadata (e.g., title, layout) as well as custom variables. Each layout requires specific variables, while others may be optionally assigned.
Only plaintext is allowed inside YAML preambles, while common markdown or HTML tags can be used outside.
Important: anything you create a reference to in the website (e.g., collaborations, complementary material, events, people, projects, tools, tags) need to exist already. For instance, it is not possible to create a new project referring to a person that does not exist in
_data/people.yml. Similarly, it is not possible to create a new publication whose venue (e.g., conference) does not exist in_data/destinations.yml.
You can add a person (e.g., new member or student) in the _data/people.yml file:
- check whether the person (and the correct affiliation) is already listed;
- if the person is already listed but with a former affiliation, please do not update the existent entry, as this would cause every page referring to the entry to update accordingly. Instead, add a new entry with a different ID;
- if the person is not listed, add it using the template you find at the top of the file.
Optionally, you can add a personal page for the new person in _people following the template and naming it accordingly.
Finally, modify the _data/members.yml file to add the new person to the people page of the website.
You can add a thesis in the _data/theses.yml file using the template you find at the top of the file.
You can add a tool by creating a new file in _tools following the template and naming it accordingly.
You can add a publication in the _data/publications.yml file using the template you find at the top of the file. Remember that each publication is linked to a destination (see below).
How to define tags for a publication? You can (i) check the tags already existing in
_data/tags.ymlor (ii) use the keywords of the publication as tags or (iii) you can create new tags (but only if strictly necessary), either by defining them manually or by asking an AI (e.g., ChatGPT) to extract them from the abstract. A publication should have no less than 2 tags and no more than 5 tags.
This website implements a filtering system for publications based on tags. You can add a tag in the _data/tags.yml file using the template you find at the top of the file.
You can add a destination (e.g., conference, journal) in the _data/destinations.yml file using the template you find at the top of the file.
You can add a project by creating a new file in _projects following the template and naming it accordingly.
You can add a collaboration by creating a new file in _collaborations following the template and naming it accordingly.
You can add a complementary material (e.g., for a publication) by creating a new file in __complementary following the template and naming it accordingly. The page will not be listed on the website, but the link can be used in papers or other publications: https://aleph.github.io/complementary/<name_of_the_complementary_file>.
For now, just contact sberlato@fbk.eu.
For now, just contact sberlato@fbk.eu.
We have decided to permanently remove the news from the ALEPH's website (see issue #2).
Until we have an event, we have decided to remove the events page from the ALEPH's website. We will refer to the instructions in the ST website to add events.
Until we have a dissemination activity, we have decided to remove the dissemination page from the ALEPH's website. We will refer to the instructions in the ST website to add dissemination activities.
Until we have a teaching activity, we have decided to remove the teaching page from the ALEPH's website. We will refer to the instructions in the ST website to add teaching activities.