Hey Jamie thanks for taking this long form. I’m not going to follow your structure 
I think the first question is whether it is a shared community resource or not. If it’s not – then any opinions we have are just that, and people may be better off banding together and creating something like EthHub. Which is pretty darn good and uses common open source norms for managing a repo, pull requests, and markdown editing. You get stuff like contributors and diffs and discussions on changes as part of being based on git. So I would be disappointed if ethereum.org is just a different version of EthHub.
Then there’s the Ethereum Wiki, which Virgil ported from what was a stale Github Wiki. This has a web front end which anyone can edit (currently – the WikiJS system it runs is backed by Git and can have page / path level permissions set, as well as user logins). I have added several pages there, but the wiki is “lightly maintained” – that is, as far as I know, there isn’t anyone regularly monitoring and updating it.
Drupal.com is an example of a highly informative “landing page” style site for a community.
So, let’s assume it’s an EF run landing page, since EthHub and the Ethereum Wiki already exist.
Here are my thoughts on objectives for an EF run landing / home page for Ethereum:
- What is Ethereum? What is Ether?
- Major news (newsletter sign up?)
- Major events
- Direct people to where they need to go based on what kind of target user they are – end user, developer, miner, exchange
- Case studies (like DrupalDotCom) – there was a call for impact so maybe those are a start; this could be contentious to curate; different types of case studies for open source projects? research? etc.?
- Foundation-specific objectives
It’s the foundation’s site. I think they should commit to transparency and open-ness, so I would suggest the source of the site on Git and clear ways of filing issues, contributing, and so on – if they want help maintaining it. But it should be relatively static other than major events a couple of times per year. So – perhaps not necessary.
I think what was sad was having the source code open and issue queue open, but then basically ignoring community input, especially as we spent years begging them to help update it.
Having an actual site for the foundation would be awesome, too – like at foundation.ethereum.org or /foundation.
The Drupal site has a link to the trademark policy – which seems like it would be useful.
How to pay everyone: I mean, hire people? If it’s an EF owned property, it’s going to need at least one full time person doing content and answering questions around it, plus web dev as needed for maintenance.
Credit work: github commits. But not necessary at all if it is a landing-page style site, that’s just distracting.
I loved Aya’s talk at DevCon4, with the concept of the constellation or galaxy – this is probably a good start for target users (HOWEVER – nothing here about core governance or implementation, just researchers).
In looking at other subdomains of EthereumDotOrg, I found a bunch of other stuff. Like, the footer of the blog links to the LinkedIn profile of some dude in Calgary – it’s a Jekyll blog, but I have no idea who to contact about that other than to tweet at maybe Hudson and/or Virgil.
