Commit Graph

331 Commits

Author SHA1 Message Date
6fa4791eaf
.github/workflows/pages.yml: Fix syntax
It's due to the indentation (missing the with:).
2021-12-14 14:14:35 +02:00
0ccf573ace
.github/workflows/pages.yml: syntax error
Not sure why this line has a syntax error...?
2021-12-14 14:13:36 +02:00
4e92f0b8cd
.github/workflows/pages.yml: adjust branches
Run Python job steps on all branches, but only push to GitHub pages
from main.

See: https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions
See: https://docs.github.com/en/actions/learn-github-actions/contexts#github-context
2021-12-14 14:09:58 +02:00
22b78ea149
.github/workflows/pages.yml: add Python for parsing
Attempt to add Python and Poetry so we can run the schema parsing
scripts to generate the site content and the RDF.
2021-12-14 14:02:16 +02:00
3c85358f77 README.md: remove TODO about DSpace fields
We have converted this to a GitHub issue.

See: https://github.com/alanorth/iseal-schema/issues/1
2021-12-13 16:16:18 +02:00
Marie-Angélique Laporte
6f62b97b53 rdf regenerate 2021-12-13 14:20:13 +01:00
Marie-Angélique Laporte
0feba6829a removing unused files 2021-12-13 14:10:59 +01: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
c5eca3cc12
util/generate-hugo-content.py: re-work vocabularies
Read vocabularies from the data/controlled-vocabularies directory
instead of exporting them from the schema itself. Also, I use the
name vocabulary.txt for all of them on the site since they are in
each field's directory already.
2021-12-13 15:03:20 +02:00
96bc2b5f79
Extract controlled vocabularies
We want to keep these outside of the schema file itself to make it
easier and less error-prone to edit them.
2021-12-13 13:32:29 +02:00
747837d14b
util/generate-hugo-content.py: update comment 2021-12-13 13:31:29 +02:00
14edfab18b
util/generate-hugo-content.py: minor re-org
We get the cluster first since clusters encompass modules.
2021-12-13 13:20:09 +02:00
fd3be3163f
util/generate-hugo-content.py: don't split element name on dash
We don't need to do this anymore since we adopted the new clusters
and cleaned up the element name field.
2021-12-13 13:17:03 +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
86f49b5fb8
README.md: add more TODO 2021-12-07 23:21:26 +02:00
6c58ea2db2
Update python requirements.txt
Generated with poetry:

    $ poetry export -f requirements.txt > requirements.txt

This is useful for people who don't have poetry.
2021-12-07 23:05:27 +02:00
2d28e5257b
poetry.lock: run poetry update 2021-12-07 23:03:13 +02:00
b5314a033d
Remove openpyxl
We don't need it now that we're reading the schema fields from CSV.
2021-12-07 23:02:04 +02:00
1c83c043d1
README.md: update for CSV schema 2021-12-07 23:00:25 +02:00
0265e97a2b
util/generate-hugo-content.py: read schema from CSV
Read the schema fields from CSV instead of Excel now that there is
a copy here in the repository.
2021-12-07 22:57:09 +02:00
2074dfe8ce
Add data/schema-fields.csv
This comes from Peter's idss_schema_fields_new2.xlsx. We want to
start versioning this file in git and move away from Excel.
2021-12-07 22:55:36 +02:00
6169f92f6c
README.md: add more TODO 2021-12-06 21:31:03 +02:00
c85a4690f3
.gitignore: ignore Python virtualenv 2021-12-06 21:29:22 +02:00
aa7f27ae38
README.md: add more information
Add a screenshot of the documentation website and more information
about the Python/Node.js setup and usage.
2021-12-06 21:28:18 +02:00
96df76b73d
Add requirements.txt
Generated with poetry:

    $ poetry export -f requirements.txt > requirements.txt

This is useful for people who don't have poetry.
2021-12-06 21:20:25 +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
2b22f9b57d
poetry.lock: run poetry lock 2021-12-02 12:55:55 +02:00
d092f83cda
pyproject.toml: adjust dependencies
Remove pylode because Marie says she was only using it for the HTML
docs, but I'm doing that differently now. This means we can have a
direct dependency on rdflib now.

Also, move isort and black to dev dependencies because nobody will
need them except me. :)
2021-12-02 12:53:25 +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
b5d1b77fb8
Add license notice
ISEAL confirmed that we can use CC-BY-SA-4.0 for website content,
but this is not appropriate for the code in this repository. I will
suggest that we use GPLv3.0 for that as it is comparable.

Importing a copy of the GPLv3.0 license text from:

https://www.gnu.org/licenses/gpl-3.0.txt
2021-12-02 10:40:49 +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