v2 Project Scope

[renatomcamilio]

Intro

Although it's expected to have a well defined scope before we can put our hands on, this project has a different set of requirements and might have some adjustments on the go.

10,000ft view

We currently have a MVP version of our org website at http://codedoesgood.org; It's out there 'cause 1 > 0 (read "one is greater than zero", or "one is better than nothing").

It's time to make justice to our organization and the awesome work we've been doing. Some of our v2 goals (but not limited to):

• Unified interface to expose our projects, guides & volunteer community
• Integrated with volunteer manager APIs (projects, volunteers, guide/wiki* editor)
• Enhanced reading experience (by implementing a Medium like UI -- we have lots of text content)

Moving away from GitHub Wiki based content

*wiki based on GitHub; we are planning to move towards storing the content on our own db and have an editor for our documentation/guides.

Just as a reference, some good points of our conversations around the evolution of v2:

[...] it is hard for people to find things (on the wiki). [...] it would be good to brainstorm a v2 that has a kind of operations manual or training guide or something that would be more user friendly than the wiki on GitHub. It should be searchable but also readable so that ppl can easily read the required information, not only search.

The goal of CDG is to be a self running, self policing, machine. People should be totally empowered to make decisions with their team without involving ppl "higher" in the hierarchy than they are. That can only be achieved with easy access to information [...]. Ideally the volunteers will know most things so that you all can correct each other [...].