Webmaker/Roadmap

From MozillaWiki
Jump to navigation Jump to search
Mozilla webmaker logo-icon.png Webmaker Roadmap 2014
Owner: Webmaker Community & Product Team Updated: 2014-01-14
Vision: Mozilla Webmaker provides tools, community and badges that help people move from *using* the web to *making* the web.



Read about why we're building this and how to get involved

Goal

In 2014, Webmaker's main mission is to:

  • Get 10,000 people teaching, building, and organizing as part of Webmaker.
  • If we do this, we succeed.

This is Webmaker's commitment to Mozilla's goal of reaching the next million Mozillians. Webmaker gathers people who want to teach the web, advance web literacy and champion digital empowerment. We want people to understand the culture, mechanics and citizenship of the web.

In 2014, we'll focus on our lead users: people already excited about this work. We'll engage them to help build our products, bring content, and grow community.

Contribution is our #1 metric

We have set a target of 10,000 contributors by the end of 2014.

We will work with anyone interested in teaching, making or organizing around web literacy. Learn more about what we mean by web literacy.

What are our contributors doing?

  • Teaching. Teach and curate Webmaker tools, pathways and other aligned resources that teach web literacy.
  • Building. Write pathways and code that foster web literacy, including localization and MakeAPI implementations.
  • Organizing. Host events, trainings and campaigns that grow local communities in a networked way.

See a more detailed list of what our contributors do.

2014 Priorities

What are we SHIPPING to support these goals and bring in more people?

Priority 1

  • Engagement Ladder. Make it easier to get started, become more involved, and contribute. Clearer pathways, calls to action, documentation, celebration.

Priority 2

  • Web Literacy UX. Make Web Literacy the heart of our user experience on Webmaker.org.
  • Pathways. Content, curriculum and educational resources. Flesh out the Web Lit map with great activities, lesson plans and ways to teach and learn.
  • Training. Teaching people how to teach the web. Professional Development for educators. Guides, MOOCs, human support. Well-packaged on webmaker.org, developed and tested with Hives and other key communities

Priority 3

  • Product Support. Webmaker Product support systems. Documentation. SUMO management.
  • Events platform. Better UX. Capture data on event hosts *and* event participants.
  • Hive Infrastructure. "Hive in Your City" cookbook. Infrastructure to align, grow and govern.
  • Webmaker Badges. Aligned with the Web Literacy map. Plus badges for Webmaker Mentors and Hive participation. (NOTE: dependent on BadgeKit)
  • Appmaker. Introduce Appmaker as a Webmaker tool.
  • Webmaker Channels. Turn Webmaker profile pages into a robust personal curation tool or "channel." Allow users and partners to easily curate things they’ve made on Webmaker, and from elsewhere on the web. Co-design and test with Hives.
  • MakeAPI. Improve the MakeAPI to make it easier for partners and other developers to plug into our platform. Allow 3rd party tools and arbitrary URLS to be added to Webmaker.org.

Timeline

Q1: Jan to March: Design and build

  • Redesign Webmaker UX with Web Literacy at its heart. Curriculum sprint with community. Optimized design, engineering and user testing systems. Community training.
    • Community growth focus: Train

Q2: April to June: Ship and refine

  • Prep for Maker Party. Events platform. Improved UX. Refine and test curriculum. Localization sprint. Better on-boarding and features for partners. Local community leaders prepped.
    • Community growth focus: Recruit

Q3: July to Sep: Campaign and market

  • Maker Party. Spike in community growth, celebration, contribution, localization. Showcase first Webmaker Badges. Marketing push in key locales.
    • Community growth focus: Organize

Q4: Oct to Dec: Harvest, celebrate community, plan

  • MozFest. Key product announcements. Web lit PR and press push. Recognize and empower lead users. EOY campaign.
    • Community growth focus: Celebrate

Next steps on this document


Synthesized from Mark Surman's email Jan 12

  • Goals.
    • This page is both a set of Webmaker goals and a roadmap for delivering them. So pull in more of the Webmaker goals from the 2014 planning wiki: https://wiki.mozilla.org/Foundation/2014Plans
    • TO DO: Update /Webmaker wiki with this stuff from MoFo 2014 plans page
  • Story
    • We need a place to up-level the Webmaker story from https://wiki.mozilla.org/Foundation/2014Plans
    • Needs to go somewhere prominent. It gives a good picture of what we're going to build and why we're going to build it.
    • Make sure the'what we're going to ship' and 'how we're going to recruit people' narratives don't get buried in all our priorities and detail.
      • Proposal for this:
        • Feed it into an updated "About" page for Webmaker. (the high level vision)
        • Feed it into an updated "Get Involved" page for Webmaker. (the high level of what we're building) [done, here: https://wiki.mozilla.org/Webmaker/Get_Involved]
        • Link to it prominently from this roadmap page. As a good intro / context to "what we're building and why." [done, top of this page]
        • Refresh the main Webmaker wiki page to address this as well [done, here: https://wiki.mozilla.org/Webmaker]
  • Contributors section
    • Numbers. Add numbers for the metrics information.
      • if contributors are our main metric, how many contributors do we want? (Target: 10k contributors in 2014)
    • Detail. the list of teaching / building / organizing roles may be too detailed here.
  • Hive
    • Up-level Hive in the priorities. It represents almost 1/3 of Webmaker staff and budget. So integrate the Hive and Webmaker story more. [done]
  • 2014 Priorities and Timeline
    • Spreadsheet doc. Make sure this spreadsheet workplan doc is fully integrated
    • Add priorities. Which are P1 vs P2, P3, etc.
  • Narrative
    • Ensure these notes are integrated:

In 2014, our main mission is to:

- Get x,000 people teaching, organizing and contributing as part of Webmaker. - If we do this, we succeed.

In order to do this, our team and our community needs to build / ship:

- Teaching kits and makes that cover the whole web literacy map - Pathways that guide people through that map - Badges for people teaching against that map - [plus other stuff product team lists]

As we build these things, we're also going to go out and recruit people by:

- 'Bulk recruiting' contributors via like minded orgs and networks like NWP - Growing more Hives and local networks to that network contributors locally - Inviting Mozilla supporters to 'teach' via mainstream Mozilla channels

Once we recruit these people we will activate them by:

- Running ongoing train the trainer MooCs all of these people to onboard them - Inviting all them to teach with our stuff, and run their own events as party of our Maker Party campaign - Eventually, getting them to to build / translate / etc. teaching kits so they get invested and bring friends

Retrieved from "https://wiki.mozilla.org/index.php?title=Webmaker/Roadmap&oldid=892069"