Use the GitHub Pages domain in your vocabulary and make it resolve to your vocabulary

[sroertgen]

It should be possible to actually have working and resolving links when publishing a vocabulary via the GitHub Pages approach

Related skohub-io/skohub-vocabs#26

[sroertgen]

@acka47 you can test this now.

The setup is described in the README 8https://github.com/skohub-io/skohub-docker-vocabs?tab=readme-ov-file#custom-domain)

[acka47]

+1 This works great, see https://acka47.github.io/skohub-pages/

Some example URIs:

• vocab: https://acka47.github.io/skohub-pages/colour-with-hierarchy/
• Concept: https://acka47.github.io/skohub-pages/hcrt/lesson_plan
• Collection: https://acka47.github.io/skohub-pages/hcrt/test_collection

However, I have noticed a general problem that probably not only occurs with SkoHub pages:
We run into problems, when the scheme URI is like https://example.org and we have a concept URI that is https://example.org/index.

In the concrete example these are:

• scheme: https://acka47.github.io/skohub-pages/hcrt/
• concept: https://acka47.github.io/skohub-pages/hcrt/index

As you can see, the Concept HTML will not be shown but only the scheme HTML. This does not occur for HCRT as we have a specific /scheme URI fpr the concept scheme. I am not sure whether we should do something about it.

[sroertgen]

Maybe we should just add a constraint/hint for SkoHub Vocabs that .../index is not a recommended URI

[acka47]

Done with #22, announced in https://blog.skohub.io/2024-03-21-skohub-pages/. Closing.