Deployment

Deployment is the process that makes an approved version of the website public. Contributors normally do not deploy manually; they submit a pull request and the repository settings handle publication after approval.

GitHub publishing

Current publishing branch

GitHub Pages currently publishes the redesign branch while that version is being tested. The project plans to publish from main again after the redesign is stable.

This branch choice is managed in the repository's GitHub Pages settings. It is separate from the automated testing workflow.

Automated checks on GitHub

.github/workflows/site-checks.yml tells GitHub to run the project checks:

• whenever a pull request is opened or updated;
• after a direct push to main.

A green check means the automated tests passed. It does not replace browser testing or maintainer review.

Production contents

Production settings

_config.yml contains:

• the public website name and address;
• the news collection settings;
• the files and folders excluded from the generated site.

Restart the local Jekyll server after changing _config.yml.

Files that must stay out of the public site

The generated website must not contain:

• AGENTS.md;
• README.md;
• tools/;
• vendor/;
• font specimen HTML pages and unused font formats.

Do not commit generated _site/ or .jekyll-cache/ folders. The publishing environment creates fresh output from the source files.

Release process

Before a release reaches visitors

1. A contributor runs Running Checks.
2. The contributor opens a pull request.
3. GitHub runs the automated checks again.
4. A maintainer reviews and approves the change.
5. The approved change reaches the branch configured in GitHub Pages.
6. GitHub Pages builds and publishes the site.

Return to Testing and Deployment.