Apache Daffodil Website

Clone this repo:
  1. fce0dd4 Update people list by Steve Lawrence · 4 days ago main
  2. ed62f60 Fix tunable doc headings by Steve Lawrence · 9 days ago
  3. 81da355 Update documentation from daffodil v4.2.0-rc1 by Apache Daffodil Site · 2 weeks ago
  4. d8b2bf6 Generate tunables.md in update-docs workflow by Steve Lawrence · 2 weeks ago
  5. b6ab554 Correct daffodil-sbt release notes to remove flowerpress. by olabusayoT · 2 months 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.