Basic website structure

[timlichtenberg]

I suggest the following website structure, partly based on @nichollsh suggestions in FormingWorlds/PROTEUS#438.

proteus-framework.org                <- landing page
proteus-framework.org/docs           <- documentation, links to ReadTheDocs
proteus-framework.org/papers         <- list of papers, with embedded PDFs, and citation policy
proteus-framework.org/map            <- disambiguation as to module roles
proteus-framework.org/team           <- presentation of the team, developers, supporters, enabling a multi-group, multi-institutional collaboration
proteus-framework.org/policy         <- contribution and credit policy
proteus-framework.org/demo           <- example outputs and tutorials
proteus-framework.org/help           <- link to troubleshooting, contact, and forum

That seems to me a good start. Some more thoughts:

• We need to make sure to not duplicate everything from the Docs on the website. In the long-term we could consider moving the Docs to the website, but not for now.
• The website should be relatively simple and clean, the most important aspect of it is a sleek introduction to the project, some nice visuals, and essentially being a linktree to all repositories, teams, and motivation of the project.

[timlichtenberg]

I think we are edging closer to the original website structure intent: https://proteus-framework.org/, but some things remain to be discussed:

Papers: I see this becoming very tiresome to update over time. Would it be easier to simply link to an ADS or SciX curated list?
Policy: We may end up duplicating a lot of stuff in documentation and policy. Should also link to either the Docs here or instead from the Docs to this page?
Map: is now modules, I like that.