Works” “Good morning tech pundits! The main HealthCare.gov landing page and the thousands of subpages that educate the public on Affordable Care Act insurance are powered by Jekyll. This portion of the website has experienced 100% uptime and has functioned perfectly since we launched it in June. The site and our approach is all part of how we build CMS free websites.”
it or will they need a manual to figure it out? • Keep things in as few “buckets” as possible. • Be Dry: Don’t Repeat Yourself. • Reduce opportunities for error. content creators
for translators, etc.) • mage • image credit • banner image • bio • tagline • Posts, if any related • Events collection, only if any coming up • Books collection • title • cover • category (fiction, etc) • was it translated? • related translator, related editor, related contributor • synopsis • message • editions available • links to purchase • Reviews collection (on some pages) • Genre (yaml, in config)
than wrangling forms in the back-end of a CMS. • And, because every bit of our site, including the content, is in version control, it's quite easy to create an entirly new version of the site, experiment, and throw up a staging copy for review and either fold that work in or discard it. Build & Iterate