I recently forked/cloned the Academic-Kickstart for the Academic theme and had 3 sets of questions:
What to do with Shell files in the root directory?
The root Kickstart directory has two files
view.sh. What is the purpose of these files? Is there a reason to keep them in my own website directory and/or push them to Github given I’m deploying and building via Netflify?
Best-practice to edit root directory or example website in theme subdirectory?
In the root directory, there is essentially an entire website containing a
public subdirectory, etc. If one then goes into the
/themes subdirectory, there is the theme structure and an example website. When building our own website using the Kickstart directory, is it recommended to (a) edit the files in the root Kickstart directory, (b) edit the example site found in
/themes/academic/examplesite/? My inclination is build my site by editing the root Kickstart directory, but perhaps I’m missing something because it seems odd edit this directory given it will ultimately mean the files I’m pushing to my Github repo for Netlify will contain an example website within
/themes. Simply delete the example site? What else should be deleted?
Building a site where /layout and /theme are parent directories of the /content and /config directories?
If one goes from the root directory to
themes/academic, there are many additional files presumably defining the theme and an example website at
themes/academic/examplesite/. However, the
examplesite subdirectory only has
/static directories. I am confused how these files can be used to generate a site: wouldn’t we need to add a
/public directory and a
\layouts directory to
themes/academic/examplesite/ to build a website that uses the Academic theme? More generally, shouldn’t our
/content subdirectories be in the root directory and the theme files should be in a child of the root?