Page History

...

To explain the current workflow it is useful to cover its history, as the current workflow has a foundation upon which it was built. This can help understand where were, where we are, and where we can go in the near term. Or, if you're impatient and just want to get flying with Fawkes, jump to How to Build the Website.

The website was designed to have multiple site versions. There would be a website for the oldest version still maintained, v0.11.0, and one for v0.12.0, and one for v0.12.1, and so forth, as well as a site for the master branch. Each site would be a complete representation of the website at the time of that version's release and would be generated from the release tag. Then, the sites would be combined into one overall site with the latest tag being the default view. You could switch between the sites by clicking the plus button on the top right side near the search box, and a versions drop down selector would appear. The API docs would appear per version, and views would be rewritten dynamically first by Python code in the website build and then by client-side code during site run-time. 

...