iseal-core

mirror of https://github.com/ISEAL-Community/iseal-core.git synced 2024-11-18 04:47:04 +01:00

Author	SHA1	Message	Date
Alan Orth	6b2dcc9fc1	.gitignore: Ignore some build stuff in site	2021-11-11 14:56:24 +02:00
Alan Orth	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
Alan Orth	29c91c4ed4	Regenerate public	2021-11-07 21:03:51 +02:00
Alan Orth	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
Alan Orth	292274b6ff	Regenerate docs	2021-11-07 16:16:27 +02:00
Alan Orth	a7140f3d3d	layouts: Use "element" instead of "field" ISEAL refers to these as elements instead of fields.	2021-11-07 16:16:00 +02:00
Alan Orth	7eac3b9f70	Regenerate docs	2021-11-03 21:58:58 +02:00
Alan Orth	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
Alan Orth	4e65813180	Rename util/generate_docs.py to util/generate-hugo-content.py This script doesn't generate the docs itself. It actually only does the schema parsing to generate the metadata term content and vocabs. The docs site is generated by Hugo after running this.	2021-11-01 09:04:57 +02:00
Alan Orth	755ad75150	Regenerate website docs	2021-11-01 08:44:20 +02:00
Alan Orth	d2ee0b5770	.github/workflows/pages.yml: Deploy to site branch	2021-11-01 08:41:17 +02:00
Alan Orth	992fda8f85	Add GitHub workflow to publish to Pages It seems we can only enable GitHub Pages with subdirectories at the root of the project. Ours is in ./site/docs so I think we need to use an example like Hexo's to publish with a GitHub workflow. See: https://hexo.io/docs/github-pages	2021-11-01 08:38:05 +02:00
Alan Orth	fdf1c8ebcb	Add .gitignore For now only ignoring the site/node_modules directory.	2021-11-01 08:34:00 +02:00
Alan Orth	10dc377139	Add basic README.md	2021-11-01 08:33:36 +02:00
Alan Orth	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
Alan Orth	30310e6db6	Add util/generate-docs.py This script parses the Excel schema file to produce term metadata and extract controlled vocabularies to the site content directory. After running this we can generate the site using Hugo.	2021-11-01 08:21:50 +02:00
Alan Orth	c7c0d0efcc	Add setup.cfg for isort This is for sorting Python imports and warning about unused ones.	2021-11-01 08:21:32 +02:00
Alan Orth	a0e6e417d4	Add poetry config Currently covers the dependencies used in Marie's Jupyter notebook and some extra dev tooling. Note that I had an issue using poetry to install pylode, so I added it to pyproject.toml manually.	2021-11-01 08:19:39 +02:00
Marie-Angélique Laporte	5b622e80e6	fixing domain and range namespace	2021-10-28 09:04:51 +02:00
Marie-Angélique Laporte	3e194e10c6	first attempt at creating the ontology file	2021-10-06 18:13:21 +02:00

20 Commits