We use a custom style block in the base that defaults to ISEAL, but
gets overridden in the FSC layout. Layout is determined in the term
frontmatter, either "home" or "fsc".
We now have FSC and ISEAL color schemes with some common style in
main.scss. I don't have any branding guidelines for FSC so I'm just
using colors for now.
I don't like the "hanging" icons now that I look again. Better to
use normal Bootstrap columns and rows here with the icons in the
header. I need to figure out how to add spacing between these when
we are on small devices and the columns stack, though!
The ISEAL Branding Guidelines Version 3.0 (June 2021) say we should
use Arial font for online material and it specifies the RGB values
to use for headings, sub-headings, and body text. It also specifies
four secondary colors to be used in support of the primary colors.
Re-organize content and navigation around the concept of clusters
and modules. Elements that have suggested field names are displayed
prominently near the top of each cluster.
I am still exploring how to present the clusters and modules better.
Perhaps as a badge on each element?
This installs a local copy of the Hugo binary that we need to build
the site. Otherwise the user would have to install it via their sy-
stem package manager. This also adds a new npm "build:site" script
to build the site using our local version of Hugo.
Note: this is slightly annoying, but after toying with "easier" op-
tions like Hexo that integrate with the JavaScript ecosystem more
naturally, I ended up preferring Hugo anyways. Hexo's not nearly as
powerful or well documented as Hugo.
Note note: there is also the `hugo-bin` package on NPM, but it is
very out of date.
