Port aurweb's php HTML generation templates to jinja2
This should be done in a modular fashion. See the check list.
Note The page content
fragment can be left as a placeholder at the end of this task's portion. That is, a jinja2 template should be defined for it and included in the <body>
fragment. We can then move on to migrating routes individually by defining corresponding templates for their content.