Refactor the github structure

[looooph]

The current git-repository structure can be optimized, making it more convenient to use and create a better overview.

My recommendations would be:

General

• have a main repository for tasks/issues outside a certain dataset (Can only creates issues within a repository in github, lol)

Ideas for the dataset repos

A : Have a repository for each dataset, where the repository would include its dataset website in one branch, the ontology etc in another.

Pros: All the related data and work of a database is at one single place, better overall overview Cons: Working with the website and the ontology at the same time sucks more, it's not the "supposed" git way

B: Have a repository for each function, for example all the webpages in one repository, where each branch represents a different webpage, same for the datasets

Pros: Very good overview of the repositories, easy to work on website and ontology data combined Cons: Might get untidy when adding several other datasets

C: Each webpage and each kg of every dataset get their own repository

Pros: Everything is truly seperated Cons: Will definiatly get pretty untidy at some point

What do you guys think, have any other ideas?

[looooph]

Alright, I have put some work into it and have established a coconutKG and nubbeKG repository of the type A.

All the work we have put into those dataset so far is transfered here, including the webpages. @edgardmarx I already setup the github-pages for the new repos and they are available at https://chemnet-io.github.io/coconutKG/ https://chemnet-io.github.io/nubbeKG/

All you need to do is to set the domain accordingly, then we can delete the repositories "websites" and "coconut-kg-docs" and we have a clean structure.

Additionally I created templateKG, which is the newest release of the updates made to nubbe-webpage by Jonas, but as a template.

[looooph]

All things have been done here, now we look professional enough to invite the OS masters