Skip to content

ADR: Migration to Gatsby

Stuart Casarotto edited this page May 5, 2020 · 3 revisions

Architecture Decision Record: migration to Gatsby

Status

Approved

Context

With the redesign of the site, there is a good opportunity to reevaluate the use of Jekyll as the static site generator for dds.mil. A primary goal of the re-work is for it to be backed by a CMS for content creators to maintain the site without need for developer involvement. Gatsby is proposed as a more modern, feature-complete, and developer-friendly alternative.

Decision

Re-work the site using Gatsby and TypeScript

Consequences

Pros

  • Easier integration with netlify-cms as a CMS backend, and Netlify for hosting
  • Plugin based ecosystem provides more modern features out of the box
  • Plugin exists for easy integration into planned to be hiring platform
  • Gatsby is based on React, which is more familiar to the current team and provides smoother onboarding.
  • React is the most popular javascript frameworks thus biasing toward a higher likelihood that future developers will be familiar with the core technology.
  • TypeScript provides type-safety and ease of development
  • Gatsby is highly extensible and customizable through it's graphql data management system

Cons

  • Requires reworking the previous working setup