How it begins I’ve been volunteering time to help the PTA at my youngest daughter’s Elementary School implement a new website and bring some web technologies to their operations. This post focuses on one aspect of this effort, fundraising. The annual Color Run is coming soon and the PTA uses this event as one of the many small fundraisers for the organization. The question to me was, “Can we accept online donations for the students, where each student has their own unique donation page/url?
To simplify and improve the process of building this website, I had to make a few changes. My previous build and delivery process (written about on this site) was based on GitLab CI/CD using a Custom Docker Image and creating GitLab Pages that were hosted on Cloudflare CDN. My new setup just uses GitLab for the code repository and Netlify for everything else. Using Netlify is fairly common for static sites, but the thing that made mine unique and required some of the complexity of the previous setup, is that I wanted to use Madoko to build some documentation files and include the output of that process into the final website.
I posted last year about using Hugo and Madoko in a Custom Docker Image for GitLab CI/CD. I received an email asking for more information about the image and my CI file setup. This post goes into a bit more detail about the GitLab CI configuration file that I used and what the various parts of it do in the build process.