c4hrva-landing 2.0

[qwo]

[qwo]

@wbprice and I were talking about upgrading the current landing site. Some features discussed have been implemented and have a common theme. I link the existing site and don't think a complete overhaul is required but making the site more data-driven and clean will let it be reusable and others to hack on.

The common theme that im seeing is all these brigades sites are being powered the civic.json standard and the cfa-api. (codeforamerica api)[http://codeforamerica.org/api/] I mean look how sweet the brigade landing site looks.. http://codeforamerica.org/brigade/index/Code-for-Hampton-Roads

So heres my brain dump and observations so far and i'd be happy to hear anyones feedback on improving, upgrading, and roadmap for the site.

• Project Pages
  • http://opengovhacknight.org/projects.html (backbone/github api) / Fork https://github.com/c4hrva/c4hrva-landing/issues/103
  • http://projects.betanyc.us/#!/ (angular/github)
  • http://codeforphilly.org/projects/ | http://laddr.poplar.phl.io/ (Emergence )
• Event Pages
• Orientation
• New coders and non coders can get involved
• (Dev Docs Type - Get Started Now button)
• Reusability - is it easy for a brigade to fork and run with
• Upgrade Path - we do have the most forked repo, and origin one, it would be nice for brigades to be able to easily upgrade and stay current but have something they can hack on

[qwo]

two greenfielders @wbprice

• [ ] http://www.codeforboston.org/
• [ ] http://codefordc.org/