Presently, it's a little bit unclear how data gets from this repository to wherever campusdata.org looks to serve static files. As a result, we have a situation where https://campusdata.org/ is half health blog, half content from this project.
Screenshots: (health blog)

(content from this project's markdown files)

Medium term suggestions:
- Document current pipeline
- Replace current pipeline with a new one (perhaps with Netlify)
Short term suggestions
- Investigate how health blog content is getting deployed to the current location, and replace with the static build from this site
Presently, it's a little bit unclear how data gets from this repository to wherever
campusdata.orglooks to serve static files. As a result, we have a situation where https://campusdata.org/ is half health blog, half content from this project.Screenshots: (health blog)
(content from this project's markdown files)
Medium term suggestions:
Short term suggestions