In my original proposal for Jenkins 2.0, I called for the site to switch from Drupal to a static site generator.
This is something I personally believe in, and the feeling was shared by danielbeck and rtyler. In the past, Tyler has done a Jekyll based jenkins-ci.org prototype. Arquillian, my go-to example of what our website should be, uses Awestruct.
The goal here is to improve the community participation into the content by lowering that bar, and also secondarily reduce the infra overhead. We think the static site generator backed by a Git repo in the jenkinsci org achieves these goals.
gusreiber also walked me through the process of how one thinks about the website project, and he said that one of the important parts is to think about "information schema" to organize contents in, separated from what gets shown in what pages how. The system then should let us map those contents into actual pages, which is more in the hands of the designer (
This ticket captures the preliminary experiment needed to validate these key assumptions. Either by putting together some kind of PoC, or just all-out copying how somebody else does this (such as Arquillian or the earlier prototype.)
swashbuck1r said he will check with gusreiber if this choice should be made by the designer of
INFRA-372, if it should be done by us beforehand, or if it should be done collaboratively between us and the designer.