abstract away commonalities between project/group sites?

[KonradHoeffner]

Now that we have https://onto-med.github.io/top.de/, https://annosaxfdm.de/, https://www.snik.eu/ and https://hitontology.eu, it is time to discuss whether it is feasible and worth it from a time cost to benefit ratio to refactor out the common files and functionality, what do you think @Yagnap?

Disadvantages of the current approach

• All the files from the forked Poole/Hyde template clutter the repository and make it harder to see the actual content.
• When some dependency breaks or a new feature is available, all the repositories need to be updated where again the commits with clutter of files make it harder to see the actual content changes.
• The current way of adding publications is tedious and error prone.

Potential improvements

1. Instead of forking the Poole/Hyde template, it could be published and used as a Ruby gem or github remote repository. However initial tests with that approach were not successful. See https://github.com/KonradHoeffner/markdowntest however I may delete that repo in the future.
2. The publication information could be put in a JSON file and then a new JavaScript library could recreate the current publication pages. However at the point people with script blockers could not see the publications anymore.

This issue is low priority but at some point we should talk about it because it could save time in the long run.