The url data.ocean-sampling-day.org is very nice as a url, but the amount of editing one can do to that webpage is a bit limited
I asked Ioulia to review the OSD and the ARMS landing pages - these being build in different ways. She likes them both, however she made some comments about the OSD one that makes we wonder whether we need to have an ARMS-landing-page approach here, instead of what we have now
the links on the OSD landing page do not open in a new tab
she suggests adding logos. I am pretty sure I can add images to the README, but I wonder how modifiable that is
there is some text on the OSD landing page that should not be there (everything after "other pages: urispace documentation", or at least I did not add it and I would rather not have 2 days of adding content to one page - loss of control!
The links to the repos (OSD2018) open in the rocrate explorer and she does not like that. It is too confusing, too many files., too difficult to navigate I concurr. The github page is much better here, rather than the rocrate explorer, which has a different use-case.
This last point - maybe we should be testing the rocrate explorer on some external people, and thinking a bit more about its use case? Ioulia is a good test subject here.
I think we could discuss these points before doing anything
The url data.ocean-sampling-day.org is very nice as a url, but the amount of editing one can do to that webpage is a bit limited I asked Ioulia to review the OSD and the ARMS landing pages - these being build in different ways. She likes them both, however she made some comments about the OSD one that makes we wonder whether we need to have an ARMS-landing-page approach here, instead of what we have now
I think we could discuss these points before doing anything