arith-geom/ag-comp-arith-geom

Purpose and runtime

This repository builds the official static website for Heidelberg University’s Computational Arithmetic Geometry group. It is a Ruby/Jekyll site: source content is rendered at build time into static HTML/CSS/JS, then published through GitHub Pages. Local entry point: bundle exec jekyll serve; dependencies are defined in Gemfile and Gemfile.lock.

Site entry points and routing

Top-level landing and primary sections are Markdown pages, with navigation/content driven by front matter and data:

• index.md

• _pages/home.md

• _pages/members.md

• _pages/publications.md

• _pages/research.md

• _pages/contact.md

Jekyll layout selection is the main routing/rendering boundary. Shared page shell and specialized content layouts live in _layouts/default.liquid, _layouts/page.liquid, _layouts/publication.liquid, and _layouts/profiles/member.liquid.

Structured content model

Editorial data is primarily YAML under _data, separating content from templates. Important domain datasets include:

• _data/members.yml

• _data/publications.yml

• _data/teaching.yml

• _data/research.yml

• _data/navigation.yml

Research and teaching also use Jekyll collections/content files under _research/ and _teaching/, e.g. _research/galois-representations.md and _teaching/index.md. This boundary allows editors or a Pages CMS workflow to change structured records without altering rendering code.

Build-time content generation

Custom Ruby plugins convert structured records into generated pages, enforce naming rules, and provide presentation filters:

• _plugins/member_generator.rb

• _plugins/publication_generator.rb

• _plugins/teaching_generator.rb

• _plugins/shortlink_generator.rb

• _plugins/filename_checker.rb

These plugins are architecturally significant because generated member, publication, teaching, and redirect/shortlink routes depend on build-time transformations rather than only handwritten pages. _plugins/cache_bust_filters.rb supports asset versioning; _plugins/linkify_authors.rb enriches publication author output.

Rendering composition

Layouts compose reusable Liquid includes into site pages. The global shell is split into head, header, footer, and scripts:

• _includes/layout/head.liquid

• _includes/layout/header.liquid

• _includes/layout/footer.liquid

• _includes/scripts/scripts.liquid

Domain rendering is componentized for publications, projects, CVs, and repository information, notably _includes/components/citation.liquid, _includes/components/selected-papers.liquid, and _includes/cv/time_table.liquid. Page data flows from front matter/YAML collections through layouts and includes to static output.

Assets and browser behavior

Sass is compiled from the main stylesheet entry point and partials:

• assets/css/main.scss

• _sass/_variables.scss

• _sass/_themes.scss

Client-side JavaScript adds interactive presentation behavior, including search and MathJax configuration:

• assets/js/search/search.js

• assets/js/components/mathjax-setup.js

• assets/search-data.json

Large static PDFs and migrated archival materials are served directly from assets/uploads/, assets/migrated/, and assets/img/fileadmin/; they are content assets, not application-managed storage.

Delivery and quality boundaries

GitHub Actions provides the deployment pipeline in .github/workflows/pages.yml, targeting GitHub Pages. Repository configuration is centered in _config.yml and .pages.yml. A Python validation utility at .github/scripts/validate.py is available for content/data quality checks; it is separate from the Jekyll runtime. No server-side application, database, or API integration is indicated; external comment/embed providers are represented by optional Liquid includes such as _includes/content/disqus.liquid and _includes/content/giscus.liquid.