Circle CI may be of use here, but probably in only in a limited number of cases. I need to determine if it's even worth doing since the work in this repo effectively amounts to "front end" type work; Gatsby and Sanity Studio both use their own built-in webpack servers; none of it is stuff I wrote, so it doesn't make sense to test
Most of the Gatsby site changes will be closer to vanilla front end work. The Sanity studio is a bit more custom; that will take some exploring. I'm wondering if there may be use in testing the setup between the Studio and the Gatsby site; e.g., setup an example configuration where the site is configured to listen to content changes from the source Studio ("Preview").
Description
Circle CI may be of use here, but probably in only in a limited number of cases. I need to determine if it's even worth doing since the work in this repo effectively amounts to "front end" type work; Gatsby and Sanity Studio both use their own built-in webpack servers; none of it is stuff I wrote, so it doesn't make sense to test
Most of the Gatsby site changes will be closer to vanilla front end work. The Sanity studio is a bit more custom; that will take some exploring. I'm wondering if there may be use in testing the setup between the Studio and the Gatsby site; e.g., setup an example configuration where the site is configured to listen to content changes from the source Studio ("Preview").