Apache Daffodil Website

Clone this repo:

Branches

  1. ebfecec Release Daffodil 4.1.0 and Daffodil SBT Plugin 1.6.0 by Steve Lawrence · 5 days ago main
  2. f9f5a37 Include Java information in release notes by Steve Lawrence · 6 days ago
  3. 8b87c3c Set max-parallel for matrix GitHub action jobs by Steve Lawrence · 7 days ago
  4. 793313b Update documentation from daffodil v4.1.0-rc1 by Apache Daffodil Site · 13 days ago
  5. 7ac34a2 Add Daffodil 4.1.0 and SBT Plugin 1.6.0 release notes by Steve Lawrence · 13 days ago

Apache Daffodil Website

The Apache Daffodil website is based off of the Apache Website Template.

The website is generated using Jekyll and some plug-ins for it.

Testing Locally

To improve reproducibility and to minimize the effects and variability of a users environment, it is recommended that changes to the site repo be tested locally with a container. To do so, run one of the following commands.

With docker:

docker run -it --rm \
  --publish 127.0.0.1:4000:4000 \
  --volume="$PWD:/srv/jekyll" \
  docker.io/jekyll/jekyll:4.2.2 \
  jekyll serve --watch --source site

With rootless podman:

podman run -it --rm \
  --publish 127.0.0.1:4000:4000 \
  --volume="$PWD:/srv/jekyll" \
  --env JEKYLL_ROOTLESS=1 \
  docker.io/jekyll/jekyll:4.2.2 \
  jekyll serve --watch --source site

Then open http://localhost:4000 to view the site served by the Jekyll container. Changes to files in the site directory are automatically rebuilt and served.

Once satisfied, create a branch and open a pull request using the Daffodil project Code Contributor Workflow but using the website repo instead of the code repo.

Publishing to the Live Site

Daffodil uses gitpubsub for publishing to the website. The static content served via Apache must be served in the content directory on the asf-site orphan branch. When changes are merged into the main branch on GitHub, a GitHub action will automatically run and perform the necessary steps to publish the site.