Normalize Demo, Dev and Production servers

[wshayes]

Proposing:

demo.openbel.org should be a landing page that has a link to belmgr, apidocs, openbelapi (and any other services available to demo by openbel). the links to each service can be either subdomains or paths off of demo.openbel.org (same for dev.openbel.org below))

dev.openbel.org should be a landing page that has all of the endpoints for the dev version of the belmgr, openbelapi, apidocs, etc

openbel.org should be the landing page for openbel and point to the other resources as a high level guide

api.openbel.org should be the public production endpoint for the openbel api

apidocs.openbel.org should be the public production endpoint for the openbel api - in case we decide to use a hosting service for this

auth.openbel.org (or users.openbel.org) for the authentication endpoint

belmgr.openbel.org should be the public production belmgr instance

We'll retire the belframework.org domain completely.

For the internal Selventa installation of openbel tools/services - belmgr.selventa.com, openbel.selventa.com(/api?) - apidocs hosted on public server and linked from top-level api entrypoint.

[nbargnesi]

I like identity.openbel.org in place of auth.openbel.org. All the others look good.

[abargnesi]

Change apidocs.openbel.org to docs.openbel.org. The docs.openbel.org site should disseminate all documentation.

[abargnesi]

Synonyms for demo.openbel.org:

• try.openbel.org
• play.openbel.org

[abargnesi]

Move the blog from openbel.org to blog.openbel.org. I also think the News section on openbel.org could be captured in short blog posts.

[wshayes]

Closing this issue in order to consolidate this at OpenBEL/openbel.github.io#5