Neue ESE-Website
Find a file
AntoniaObersteiner 3e7e12ee0b
All checks were successful
publish / publish (push) Successful in 40s
add slides by BP
2024-10-18 17:53:25 +02:00
.forgejo/workflows set timezone in CI 2024-10-07 19:28:01 +02:00
_includes honor prefers-reduced-motion 2024-10-09 09:58:19 +02:00
content add slides by BP 2024-10-18 17:53:25 +02:00
submodules use better source for aileron font 2024-09-20 13:22:58 +02:00
.envrc add nix flake and devShell 2024-09-11 17:33:55 +02:00
.gitignore update gitignore 2024-10-04 22:09:22 +02:00
.gitmodules use better source for aileron font 2024-09-20 13:22:58 +02:00
eleventy.config.js migrate to Eleventy v3 and ESM, upgrade dependencies 2024-10-06 17:58:35 +02:00
flake.lock add nix flake and devShell 2024-09-11 17:33:55 +02:00
flake.nix add nix flake and devShell 2024-09-11 17:33:55 +02:00
LICENSE Update LICENSE 2024-09-12 12:45:35 +02:00
package-lock.json migrate to Eleventy v3 and ESM, upgrade dependencies 2024-10-06 17:58:35 +02:00
package.json migrate to Eleventy v3 and ESM, upgrade dependencies 2024-10-06 17:58:35 +02:00
README.md update readme 2024-10-06 23:15:46 +02:00

ESE Website

This is the rewrite of the ESE website in Eleventy.

The goal is to have an accessible and more easily editable and maintainable ESE Website.

Editing the content

All content is in the content directory, in the form of markdown files. There is usually no need to install/build the project in order to make changes there.

Additionally, there are some data files in content/_data:

Building

To build the website, install the dependencies and run the build script:

git submodule update --init
npm install
npm run build

The output will be in _site.

You can also start a development server with auto-reloading:

npm run start

Nix DevShell

A nix development shell that provides all required tools for developing and building the project is provided for convenience. Using it is by no means required, although we encourage it.

You can activate the devShell using nix develop or automatically, whenever entering/leaving this project's directory, using direnv (run direnv allow once).

CI Pipeline

Our CI will automatically build and publish any changes on main. So hopefully, the barrier for making changes is reduced further :).