move website to GitHub pages or similar

[cmungall]

A few issues with existing site:

• need to figure out how to map to environmentontology.org without a proxypass machine
• "Recent News" has stuff from 2013
• the OLS iframe is a bit hokey, better to just link
• envo adopters should be synced with obo metadata
• downloads is out of date - e,g no need to link to oboedit!
• core team is out of date

options:

1. fix the proxypass thing and just keep with gsites, update info as needed
2. low maintenance: have environmentontology.org redirect to http://obofoundry.org/ontology/envo
   • ancilliary docs such as annotation docs could live as md docs in this repo or on gh wiki
3. higher initial cost: make a new site using GitHub pages using some pre-existing template. Manually move some content across, but this would be largely refactored may be quickest to start again, except for some pages like annotation guidelines

[kltm]

@pbuttigieg @kaiiam @wdduncan @cmungall It may be a good time to prioritize this as Google Sites is forcing an update or migration by September 2021. Admittedly a little ways off, but the current site is quite stale--last edit June 2017--and it's precariously based off of proxying through Berkeley physical infrastructure.

[kaiiam]

@cmungall when you refer to option 3 with a higher initial cost using Github pages do you mean financial cost? From my understanding Github pages is free. Do you mean overhead to update/revamp the site to the appropriate format? Having a quick readover it seems pretty straightforward if we just use simple markdown to format the page(s).

Let me know what you want to go with. If we decide to go with Github Pages I could try to take a pass at putting together the site that way. Updating the content, however, could benefit from being a group effort.

[pbuttigieg]

New Google site up. GH pages still of interest, but low priority.