Drumbeat/website/brief: Difference between revisions

← Older edit

Drumbeat/website/brief (view source)

Revision as of 13:54, 20 November 2009

1,578 bytes added , 20 November 2009

no edit summary

Matt Thompson

Confirmed users

9,624

edits

@@ Line 3: / Line 3: @@
 ==Overview & Goals==
 Mozilla Drumbeat will find and connect people, ideas and actions that make the web better. Drumbeat is launching a PHASE ONE web site. The major goals of this early, beta-type site are to:
+* '''Showcase compelling PEOPLE & PROJECTS making the web better.''' These are the two major content streams, and the heart of the site.
+* '''Crowdsource great new content'''. Make it easy for others to submit their own PEOPLE & PROJECT IDEAS, using templates and workflow we provide.
+* '''Showcase and get people excited about a big upcoming EVENT''': the Drumbeat Festival in June 2010. Make it sexy and trumpet key values: genius ideas, rubbing shoulders with the web’s leading lights, and the prospect of Internet “fame and fortune.”
-* “'''Show people what we mean'''.” Explain what Mozilla Drumbeat is and where it’s headed -- primarily through powerful '''examples''' of what we mean. Use these examples to illustrate the overall concept and show rather than tell.
+''In addition, the Phase One site will:''
-* Showcase compelling a) IDEAS, b) PEOPLE and c) ACTION for making the web better. These are the three major content streams for the site, and heart of the site.
+* Encourage the best content to float to the top. Get an early sense of which project ideas have the most traction and interest with our audiences. Use a simple voting & reviewing layer (probably something like Digg) to make this easy.
-* '''Crowdsource great new content'''. Make it easy for others to submit their own ideas, people and actions, using templates and workflow we provide. This is a key priority for Phase One -- we want to create a great container that models the kind of stuff we’re looking for, and make it easy for others to start feeding their own ideas, people and action into it.
+* Showcase local events. Trumpet the big festival event at the center -- but also local events and opportunities for participation around the edges and in your community.
-* '''Showcase and get people excited about a big upcoming EVENT''': Drumbeat Istanbul in June 2010. Make it sexy and trumpet key values: genius ideas, rubbing shoulders with the web’s leading lights, and the prospect of Internet “fame and fortune.”
+* Be easy to share socially and push content to the places people are already at. Avoid re-inventing the wheel or recreating redundant infrastructure. Embed or aggregate existing third-party tools and external content.
-''In addition, the Phase One site will:''
+==Emphasis on rapid prototyping for Phase One==
-* Encourage the best content to float to the top. Get an early sense of which THEMES, IDEAS, PEOPLE & ACTION have the most traction and interest with our audiences. Use a simple voting & reviewing layer (probably Digg) to make this easy.
+* The emphasis for Phase One is RAPID prototyping and implementation; we want to prioritize speed over perfection.
-* Showcase LOCAL events and action, primarily in the form of short, Ignite-style presentations. Trumpet the big Istanbul event at the center -- but also local events and opportunities for participation around the edges and in your community. Should feel like a global community.
+* '''This means we may be willing to set aside much of the development work done for this early "phase one" site later on in the process.''' So rapid prototyping is more important than long-term durability or a perfect site.
-* Capture a “co-opetive” spirit and flavour.
+* The goal is to get to a point quickly where we can model fleshed out feature projects that show people the kinds of ideas Drumbeat is interested in, and then effectively crowd-source great new project ideas to get into the pipeline.
-* Be easy to share socially and push content to the places people are already at.
+* The "Phase Two" site will be more robust and public-facing, with a greater emphasis on graphic design, scalability, a more robust back-end CMS, etc.
-==Scope: Phase One vs. Phase Two==
+==Technology approach==
-The emphasis for Phase One is RAPID prototyping and implementation. The goal is to get to a point quickly where we can invite others to crowd-source and populate great suggested ideas, action and people. Phase Two will be more robust and public-facing, with a greater emphasis on graphic design, scalability, a more robust back-end CMS, etc.
+* The phase one Drumbeat web site will be built on a Drupal / CiviCRM platform.
+*''' Wherever possible, the Drumbeat site should leverage work completed for another site, "Mozillians.org."''' This site has been built on a Drupal / CiviCRM platform, and shares much of the CMS and CRM functionality needed for Drumbeat
+* Mozillians.org site is still at the bug-fixing stage and is due to launch in mid-December, but is now on a stable staging platform here: https://mozillians.stage.mozilla.com/
+* '''The goal is to produce two sites that are similar in functionality and that share a common CiviCRM back end.''' Since many of the donations requirements and people / relationship data overlap between the two projects, it's important that they share a common CRM platform.
-==Tech Specs and CMS==
+'''We need advice to help decide on the best technological approach to achieving this goal.'''
-Our latest thinking is that (pending some final questions and exploration) we will re-purpose an EXISTING Mozilla-led Drupal and CiviCRM install as Drumbeat's back-end platform, as a way to speed implementation and leverage more CRM muscle quickly. The new "Mozillians.org" site is still at the bug-fixing stage, but is now on a stable staging platform. The "Groups" block will map to Drumbeat's "Projects" stream.
-We will re-theme to give the Drumbeat site its own unique look and feel, using our own front-end page designs (see below). We will "fork" the two projects so that they have their own distinct front ends, while running off a shared CiviCRM platform. For more on Mozillians.org, contact:
+==Key Questions==
-Jay Patel
-jay@mozilla.com
-http://www.mozillians.org
+Given that we need two sites that
+a) share a large amount of Drupal functionality, and
+b) need to share a common CiviCRM back end...
+'''* Should we do a [http://drupal.org/node/43816|Drupal multi-site install], with two sites leveraging the same code base?'''
+* If this multi-site approach is feasible, what's the best way to resource and support that approach?
+** How do we ensure smooth workflow and back-and-forth between the Mozillians.org team and Drumbeat web site team?
+** What's the best way to divide up the work?
+*** In terms of Drupal vs. CiviCRM work?
+*** In terms of specific roles? (e.g., graphic design & theming, lead Drupal development / customization, advice & support, quality assurance, etc.)
-==Target Communities==
+* What specific parts of Mozillians.org does the Drumbeat site want to leverage?
-Leaders and social entrepreneurs making the web better. The audience for this early "Phase One" site is more apt to be technologically inclined, and already understand the issues to a degree. In Phase Two we will aim more explicitly to get beyond the "techosphere," and reach a more mainstream audience. But for phase one, we can assume an audience of more mavens and insiders.
+** In terms of Drupal functionality?
+** In terms of CiviCRM functionality?
-==Information Architecture==
+* What other modules and custom work do we need to add to get the feature set we want?
+** e.g., if we used the Mozillians organic groups set up for Drumbeat 'projects,' we'd need to add things like a blog aggregator and wiki
+* Timelines. What's realistic by deadline. How do we go faster?
+* How can we protect the integrity of Drumbeat's front-end designs? Graphic design and usability are important priorities for Drumbeat.
+** How do we ensure the front-end work we're doing in Photoshop is actually implementable?
-From an information architecture standpoint, the Phase One site is primarily about connecting PEOPLE and PROJECTS, plus raising awareness about a big upcoming EVENT, the Drumbeat Festival.
+==Drumbeat's CRM requirements==
-The people and projects need to cross reference and relate to each other in multiple ways. We need the ability to easily associate a particular PERSON, for example, with a project they're backing. Plus then easily see the other people who are joining with them to work on that project.
+'''Online Donations'''
+* Online fundraising will be a key component for Drumbeat. All fundraising will flow through CiviCRM
+* We need the ability to fundraise directly for Mozilla, but also for specific individual community-led projects as well. Drumbeat may eventually function as a kind of "Kiva for the open web," making it easy to crowdsource volunteer help ~and~ financial help for a large number of individual projects.
+* Creation, customization and management of campaign specific pages for general drumbeat donations and peoject donations through Drupal.
+* Ability to pull donor lists for specific projects and use within CiviMail.
-''Ten broad “themes” or categories''
+'''Community segmenting & sub-segmenting'''
+* Drumbeat will have an e-newsletter, with regular updates & fundraising asks
+* We need the ability to segment our list of Drumbeat supporters and participants so that we customize content and asks based on the community's a) specific interests (e.g., digital divide vs. mobile vs. privacy), roles (project initiator, project volunteer, festival participant, etc.) and geography.
-The ideas, people and action all fall under one of ten broad “categories.” These themes are like mini-impact or mission statements. Like: “The web gets better when we...
+'''Integration with Mozillians.org and other Mozilla projects'''
-* ...ensure anyone can connect to do or say anything.
+* Part of the narrative of Drumbeat is making participants feel like they're part of a larger Mozilla community
-* ...make the internet more accessible.
+* For example, many Drumbeat participants should probably also appear in the Mozillians.org community directory
-* ...use and promote open standards."
+* We want to avoid creating standalone silos of community members and donors, and instead build on a shared and scalable CRM platform
 ==Timelines==
-The site will soft launch in early January.
+The completed site will launch in early January 2010.
-==Early Front-end Page Designs==
-Photoshop mock-up of phase one Front page (Nov 8; v28):
-[[File:Home_v28.png | 700px]]
 Photoshop mock-up of phase one Festival page (Nov 8; v8):