> > Rather than serving the production site from the *content/* directory on > the master branch, is there any objection to serving it from the asf-site > branch? This would mean that the last step in the above process would be > performed on the asf-site branch rather than the master branch. In > addition, there would be no need to have a *content/* directory on the > master branch. The *content/* directory from which the production site is > served would live in the asf-site branch. This would clean the master > branch history, hiding the generated *content/* directory and the unwieldy > content changes generated by Jenkins user.
This change has been made. The repository's README.md has been updated accordingly.
