On 18 April 2018 at 07:43, Jan Iversen <jancasacon...@gmail.com> wrote: > > >> On 18 Apr 2018, at 03:04, sebb <seb...@gmail.com> wrote: >> >> The SVN tree under: >> >> https://svn.apache.org/repos/asf/attic/site-test >> >> has a sample implementation of the site generation using Jekyll >> >> This uses projects.json to create the list of projects for the RH side >> of pages as well as generating the individual pages. >> >> It needs some tweaking and documenting. >> >> For simplicity the page templates were left as HTML with minimal tweaks. >> In the longer term they should be converted to markdown for easier >> maintenance. >> >> The intention is that it will only be necessary to update >> projects.json (and create the flagged file) when retiring a project. > Surely the script could easily create the flagged file/directory, which would > be one step less to do. >> >> The output is currently directed to docs2/ to make it easy to compare >> the files with the originals which are in docs/. >> >> AFAICT all the project-specific parts of the website are now derived >> from the JSON file. > > What is the max delay between making a change and seeing the result ? (This > one is critical since you are in front of a device, and basically wants to > see the result without wait.
The jekyll build process itself takes about 1 second. > Maybe using a hook in svnpub would achieve that (having the build job to run > in a high frequency raster, sounds very inefficient, considering that we > typically only have 2-3 changes pr. year). I think the proposed buildbot builds when it detects a change to SVN (e.g. a new version of the JSON file). If not, AIUI one can add a trigger. > rgds > Jan I. >
