Would NetlifyCMS and it’s dependencies be installed on each build? If not, are the files listed below only meant for a dev install?
- and the stuff located in src
My current understanding is that all of this above gets used to generate the JS and css that is needed to support NetlifyCMS. Isn’t this better to be managed in a different repo. One that creates the build image?
Then you would just need minimal templates in your static site repo that builds /admin/index.html and the dependent js/css.
Duplicating all that boilerplate code to each of one’s static site repos is just ugly, and if it is parsed on each build, wouldn’t that affect page generation times?
I am still learning the ropes here, so please point me in the right direction if I have got it wrong. I guess I need the most ‘backend dev’ approach (which is what attracted me to Hugo, I didn’t need a knowledge of front end to get on with generating a static site.
For now I am going with the simplified way of installing. Which if I understand correctly, all the js artifacts are pre-built and hosted on a CDN?