Feat/publish

[y10011010]

this needs to be made into 2 PRs.

One for admin related code. I.e., calcurse code - hooks/conf. apts todo notes should be secured and published/backed up

Another PR for public code. I.e., jekyll collections config (and the data) _data notes/_jobs *.css etc.

Each PR should be formalised and packaged.

[y10011010]

It may make sense to alter this project to contain

config (built using yq)
UML models

The models would inform the config

[y10011010]

config/diagrams should correspond

[y10011010]

Reduce scope

Make target which outputs Jekyll collection config

Allows calcurse notes to be collection

Build config from template

[y10011010]

blocked on new version of yq with environment variables

[y10011010]

This is useful for creating config based on dynamic labels

Since there are a lot of choices for labels and categories etc, it could work to create config dynamically.

Environment can set levels of categorisation and the notes themselves contain labels