Commit Graph

140 Commits

Author SHA1 Message Date
alanorth
4db80ac8c1 Automated commit with site updates 2021-12-14 12:49:06 +00:00
cf5f17ff0f
site/docs: regenerate site with hugo 2021-12-13 15:10:04 +02:00
c815e0cffd
package.json: add npm script for hugo server
Use `npm run server` to start local Hugo server.
2021-12-13 15:07:47 +02:00
eb18a5ab3b
site: regenerate vocabularies 2021-12-13 15:05:49 +02:00
b8f2819556
site/docs: regenerate site with hugo 2021-12-13 10:24:14 +02:00
3feddf1077
site/assets: run npm build
Regenerate static assets after change in CSS.
2021-12-13 10:23:42 +02:00
f059918c40
Re-work download section
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!
2021-12-13 10:22:46 +02:00
b50e5fa3fd
site/docs: regenerate with hugo 2021-12-12 22:03:23 +02:00
9f88a0ab44
site/layouts: use table for clusters
This is better than a list.
2021-12-12 22:02:43 +02:00
fb43eeb0c8
site/package-lock.json: latest changes
After installing the bootstrap-icons.
2021-12-12 21:24:00 +02:00
7b18447e5d
site: regenerate static assets 2021-12-12 21:16:23 +02:00
060ce5e556
site: add download section
Use something similar to Bootstrap's "Hanging icons" example from
the Bootstrap 5.1 docs.

See: https://getbootstrap.com/docs/5.1/examples/features/
2021-12-12 21:13:46 +02:00
81466a508c
site/package.json: use Bootstrap Icons
For download icons.
2021-12-12 21:09:42 +02:00
568fca6400
Update npm packages
Version bump in package.json and then run `npm update` to generate
a new package-lock.json.
2021-12-06 21:05:47 +02:00
8e8aa2983c
site/docs: regenerate with hugo 2021-12-02 10:54:08 +02:00
46b31f4585
site/layouts: add CC-BY-SA-4.0 text to footer 2021-12-02 10:51:12 +02:00
26f33244d9
Regenerate site
Use `npm run build` to regenerate the static CSS/JS assets and the
HTML docs.
2021-12-01 15:16:09 +02:00
f42227914f
layouts/_default/term.html: use code for element
Use a monospace font for the element name so it is unambiguous.
2021-12-01 15:11:38 +02:00
ac1b61d3dd site/source/scss: use orange for code blocks 2021-12-01 15:08:02 +02:00
69956024f7 site/source/scss: adapt more ISEAL branding
Use tint colors from the ISEAL Branding Guidelines Version 3.0 and
remove the dark and light blues that I gleaned from the ISEAL web-
site.
2021-12-01 15:08:02 +02:00
320ade7069 source/scss: use secondary green for code
Experimenting with secondary colors.
2021-12-01 15:08:02 +02:00
3598509499 site/assets: regenerate static assets
Using the `npm run build` script.
2021-12-01 15:08:02 +02:00
71bcd1092c site: apply principles from ISEAL branding guidelines
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.
2021-12-01 15:08:02 +02:00
8aef2a0a20
package.json: update dependencies 2021-12-01 15:07:42 +02:00
77e62be66c
site/docs: regenerate with hugo 2021-12-01 12:00:16 +02:00
a86e0dfc1f
site: fix grammar in intro 2021-12-01 11:59:42 +02:00
be19dc0489
site/docs: regenerate static website using Hugo
For now it's manual:

$ cd site
$ rm -rf docs/*
$ hugo

I will explore making this automatic using a GitHub Action.
2021-11-26 12:07:48 +02:00
8482294e3c
site/content: regenerate terms
This is based on the new cluster/module re-organization by Peter
last week: idss_schema_fields_new2.xlsx
2021-11-26 12:05:40 +02:00
10f24ad093
site: add clusters and modules
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?
2021-11-26 12:01:18 +02:00
4827b2b0d4
site: align required badges with text 2021-11-26 12:00:31 +02:00
5ecf1e597c
package.json: Fix path to hugo binary 2021-11-25 07:45:40 +02:00
392a49f854
Add hugo-installer to site package.json
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.
2021-11-11 14:55:40 +02:00
29c91c4ed4
Regenerate public 2021-11-07 21:03:51 +02:00
48d91378d1
layouts/_default/home.html: update intro blurb
Use some text from the draft ISEAL Core proposal.
2021-11-07 21:02:31 +02:00
292274b6ff
Regenerate docs 2021-11-07 16:16:27 +02:00
a7140f3d3d
layouts: Use "element" instead of "field"
ISEAL refers to these as elements instead of fields.
2021-11-07 16:16:00 +02:00
7eac3b9f70
Regenerate docs 2021-11-03 21:58:58 +02:00
32949819ac
Update name of project
After discussing with ISEAL I see that the preferred name for this
project is "ISEAL Core Metadata Set".
2021-11-03 21:58:10 +02:00
755ad75150
Regenerate website docs 2021-11-01 08:44:20 +02:00
286896486e
Add initial version of schema specification site
After running the util/generate_docs.py script to parse and extract
the metadata term specifications and their controlled vocabularies,
we use Hugo to generate the HTML site. The HTML site uses Bootstrap
with several ISEAL brand colors gleaned from the corporate website.
2021-11-01 08:27:41 +02:00