From a15b795687e5c3093d06643e8b76452b03c39d6e Mon Sep 17 00:00:00 2001
From: Adam Butterworth <abutterworth@edx.org>
Date: Mon, 7 Oct 2019 16:09:52 -0400
Subject: [PATCH] Create 0001-non-usage-of-gatsby.rst (#12)

---
 docs/0001-non-usage-of-gatsby.rst | 37 +++++++++++++++++++++++++++++++
 1 file changed, 37 insertions(+)
 create mode 100644 docs/0001-non-usage-of-gatsby.rst

diff --git a/docs/0001-non-usage-of-gatsby.rst b/docs/0001-non-usage-of-gatsby.rst
new file mode 100644
index 000000000..f9b447fc8
--- /dev/null
+++ b/docs/0001-non-usage-of-gatsby.rst
@@ -0,0 +1,37 @@
+1. Non-Usage of Gatsby
+----------------------
+
+Status
+------
+
+Accepted
+
+Context
+-------
+
+This package is responsible for containing common code concerning the transpilation,
+building, linting, and testing of React-based microfrontends. Gatsby was considered as a
+potential tool for this job.
+
+Decision
+--------
+
+We will not use Gatsby in these frontend build tools for two reasons:
+
+- Gatsby is itself a javascript framework. It concerns itself with more than 
+  frontend build tooling, including patterns and tools for the runtime of the frontend app itself.
+- Gatsby relies heavily on convention, expecting to find files in particular places.
+  This makes it difficult/impossible to pull a common configuration of Gatsby into a
+  package like this one.
+
+Consequences
+------------
+
+Gatsby is a great tool for us leverage when appropriate, but it is not the right tool
+for the concern of this package.
+
+References
+----------
+
+* https://www.gatsbyjs.org/docs/
+* https://www.gatsbyjs.org/docs/gatsby-project-structure/