Open PaulCormier opened 5 years ago
Alternatively, how about this structure:
For all our projects, we take two folders out of the downloads (the WET folder and the theme folder, like your second example):
In your case, with the GCWeb theme:
It's been noted that there is duplication in the folders: https://github.com/wet-boew/wet-boew/issues/7968.
The CDTS uses the same as your first example. @duboisp wouldn't it be nice is there was a grunt task that just spits out those files? @nschonni I think we talked about this before. grunt slim
or something.
You can use the CDN download available in the GCWeb release here: https://github.com/wet-boew/GCWeb/releases
For example: themes-cdn-4.0.29-gcweb.zip
Lots of options. Thank you! I think I'm wrapping my head around it now.
@duboisp that doesn't solve what I'm looking for... I want a grunt task that doesn't do the example html files or any of the other folders not needed to run WET.
I'm looking for guidance on the minimum set of files needed from the Production Files archives available on the Downloads page. Specifically, when using the GCWeb theme, which subfolders are required and which are just part of the documentation and content examples pages?
Am I correct in assuming that the following is sufficent, and the correct structure?