Pointers for updating the site - Act-Conferences/tpc-2017-amsterdam GitHub Wiki
Updating the site
To update the site, change the master branch of the repository. After a few minutes the changes will show up on http://test.mongueurs.net/tpc-2017-amsterdam/ . If okay, someone needs to pull the changes to the production branch.
Notes on site structure
As a result of history the site uses two different responsive frameworks:
- The front page was designed in Mobirise (https://mobirise.com/), based on Bootstrap v4.0.0-alpha.2.
- The ACT templates were copied from a set of mobile-friendly ACT templates (https://github.com/barcelonapm/act-responsive) based on Bootstrap v3.2.0
It turns out those two frameworks can't be mixed in one html page. Therefore there are two site wrappers:
- actdocs/templates/ui_bootstrap4, so far only called from actdocs/static/index.html
- actdocs/templates/ui, called from all standard templates
They each call their own menu bar definition (actdocs/templates/menu_bootstrap4 and actdocs/templates/menu), which in turn calls a number of individual menus (actdocs/templates/menus/user etc.). In the individual menus, the difference between the two frameworks is hidden by setting variables in actdocs/templates/menus/bootstrap_v3_v4_adaptor.
Changing menus
- To change menu options in existing menus, only a single file actdocs/templates/menus/MENUNAME needs to be modified (following the example of existing menus)
- To change the selection of menus modify both actdocs/templates/menu_bootstrap4 and actdocs/templates/menu
Adding sections to front page
The blocks on the front page come more or less straight from Mobirise. Each block was copied to a separate template file in actdocs/templates/section/SECTIONNAME. Each block is called by a line [% PROCESS sections/SECTIONNAME %] in actdocs/static/index.html.
So, obviously to add a section, create a block in Mobirise, find the corresponding section in the index.html generated by Mobirise and follow the same steps. Each section has an id attribute in the first line and links to the id of the following section in a <div class="mbr-arrow mbr-arrow-floating ... >. IDs and linking sequence need to be adapted as desired.