The web site for Biology 708. The user-friendly view is here.
Under construction
Directories with course content:
All of these directories follow the same rules to farm out material to corresponding subdirectories of docs/ which is where the github.io pages are served.
Some make rules:
make dateup
insteaddata is version-controlled at docs/data. Avoid adding vc stuff to data/ directly. This can work for a while, but will definitely confuse new clones.
You are meant to edit the file data.md. It will also edit itself, as follows.
From the weird hybrid file, the pipeline makes data_index.md (an intermediate) and then data/index.html (which is linked to docs). The index.html
data/<fn.ext>
instances into local links (since the index file is itself in data)
You can update the data.md page through most kinds of auto-update (e.g., make update, make update_all, make sync), or just by saying make data_index.md (but there's no obvious reason to look at data_index.md, it is an intermediate towards data/index.html)
The usual style is to keep the files identified as Untracked when the script is run, but delete the word Untracked (so you can notice if new Untracked files show up)
Code directory is also meant to be a symbolic link. Like the data directory, if you git add to code (instead of docs/code), it will work fine but mess things up for future fresh clones.
The point is to have code think that it's on the "code side" (since we edit it), but also be visible on the web side.
pix/
miscellaneous non-workflow-generated imagesoldSource/
makestuff/
machineryhtml/
style stuff