|author||Julian Feinauer <email@example.com>||Wed Apr 03 18:16:54 2019 +0200|
|committer||Julian Feinauer <firstname.lastname@example.org>||Wed Apr 03 18:16:54 2019 +0200|
Use "bundle exec" in front of jekyll, to make it more robust (see https://stackoverflow.com/questions/6317980/you-have-already-activated-x-but-your-gemfile-requires-y).
This procedure was borrowed in part from the Apache Apex site except we use Jekyll.
master branch of this repo contains the source files that are used to generate the HTML that ultimately gets pushed to the incubator site. The
asf-site branch is where the actual generated files are stored. Note that this branch must contain exactly one folder called
content, and so has been checked out as an orphan branch with its own commit history apart from the
master branch. See the Contributing section below.
Through a gitpubsub mechanism on the apache.org server, files are taken from the
asf-site branch and pushed to the live server.
If you would like to make a change to the site:
If you are a committer, do the following:
build.shfrom the master branch directory (requires Jekyll). This checks out and updates the
asf-sitebranch with a new commit of the build from the current branch.
asf-sitebranch. Simply push this branch to the asf remote with
git push origin asf-siteand the site will automatically be updated within seconds.
Note: If you want to try out the website locally on the asf-site branch before you push, you can do so with
jekyll serve -d content --skip-initial-build and point your browser to
In order to ensure a consistent user experience, these guidelines should be followed:
##in order to have them be automatically added to the Table of Contents
```, and if applicable, specify the language for syntax highlighting