The version of this project pre-gatsby (see #2) had a simple docker-compose and dockerfile that could be used to play with the documentation without having to install secondary package managers or languages (only docker). I hadn't taken the time to build that during #2 -- it should be a simple migration to a container that uses yarn, install, then run and expose port 8000.
docker compose config could be done in a very similar way to support docker-compose up for an easy setup of the website to play with while editing files. Bonus points for doing volume mounts so development can be done at the same time -- gatsby supports hot reloads.
The version of this project pre-gatsby (see #2) had a simple docker-compose and dockerfile that could be used to play with the documentation without having to install secondary package managers or languages (only docker). I hadn't taken the time to build that during #2 -- it should be a simple migration to a container that uses yarn, install, then run and expose port 8000.
docker compose config could be done in a very similar way to support
docker-compose upfor an easy setup of the website to play with while editing files. Bonus points for doing volume mounts so development can be done at the same time -- gatsby supports hot reloads.