The original goal for this project was, "an easy to manage and deploy website that uses a static website generator and free (no-cost) hosting." The primary concerns were 1) effort required for lay users to make changes to meetings/events, 2) effort required to add any "unrelated" content, and 3) ability to connect to other resources.
While reviewing static website solutions, generate_content.py was written in order to transform meeting data into application-appropriate pages (and stubs). Although this provided a lot of flexibility, hugo has been selected and now the gen_content phase of website building should be revisited.
It is very likely that most (or all) of that script can be turned into hugo modules that can be used with greater flexibility. This would also allow the template to maintain generated (i.e. static) content rather than requiring the script to be run for any updates.
The original goal for this project was, "an easy to manage and deploy website that uses a static website generator and free (no-cost) hosting." The primary concerns were 1) effort required for lay users to make changes to meetings/events, 2) effort required to add any "unrelated" content, and 3) ability to connect to other resources.
While reviewing static website solutions,
generate_content.pywas written in order to transform meeting data into application-appropriate pages (and stubs). Although this provided a lot of flexibility, hugo has been selected and now the gen_content phase of website building should be revisited.It is very likely that most (or all) of that script can be turned into hugo modules that can be used with greater flexibility. This would also allow the template to maintain generated (i.e. static) content rather than requiring the script to be run for any updates.