Security & Trust Website

This document explains how the code behind the Security & Trust website (available at https://st.fbk.eu) is organized and how to work with it.

Repository Structure

The website's code is organized as follows:

.
|── .github/                => GitHub configuration (workflows, templates, etc.)
|── _collaborations/        => Collaboration pages
|── _complementary/         => Complementary materials for papers
|── _data/                  => Data used to populate lists
|   └── menus/              => Entries for custom side menus
|── _events/                => Event websites
|── _people/                => People pages
|── _projects/              => Project pages
|── _teaching/              => Teaching pages
|── _tools/                 => Tool pages
|── _topics/                => Homepage topic pages
|── assets/                 => Static assets
|   |── areas/              => Area-related assets
|   |── css/                => Custom stylesheets
|   └── images/             => Shared images
|       └── logos/          => Shared logos
|── _config.yml             => Site configuration
|── .gitignore              => Git ignore rules
|── .markdownlint.yml       => Markdown linting configuration
|── .yamllint               => YAML linting configuration
|── 404.md                  => Custom 404 error page
|── CNAME                   => Custom domain configuration for GitHub Pages
|── docker-compose.yml      => Docker configuration for local deployment
|── favicon.png             => Website favicon
|── Gemfile                 => Ruby gem dependencies
|── Gemfile.lock            => Locked gem versions
|── index.md                => Homepage
└── README.md               => This document

Local Deployment

The website can be deployed locally to preview changes in real time. This requires Docker. From the website's root folder, the container can be built and started with:

docker compose up --build

Once the "Server running..." message appears, the website is available at http://localhost:4000. Any changes are reflected in the local preview shortly after, once the rebuild completes.

Once the container is no longer needed, it can be stopped with:

docker compose down