Recent PR from Austin raised an excellent point about the current structure of our Apache/Flagon repo.
Presently, this repo contains: 1. Website assets 2. Integration examples (e.g., ELK) Keeping this repo together as a jumble of top level “utilities” does prevent us from improving automation in builds and tests for our website, in particular. Proposal: Let’s split this repo into two. Establish an Apache/Flagon-Website repo, and maintain automated builds and tests for our website. Thoughts?