Webmaker/Roadmap: Difference between revisions
< Webmaker
Jump to navigation
Jump to search
(→Goal) |
(→Goal) |
||
Line 15: | Line 15: | ||
* If we do this, we succeed. | * If we do this, we succeed. | ||
<b>This is Webmaker's committment to Mozilla's goal of reaching the next million Mozillians</b>. Webmaker gathers people who want to teach the web, advance web literacy and digital empowerment. In 2014, we'll focus on our <b>lead users</b>: people already excited about this work. We'll engage them to help build our products, bring content, and grow community. | <b>This is Webmaker's committment to Mozilla's goal of reaching the next million Mozillians</b>. Webmaker gathers people who want to teach the web, advance web literacy and champion digital empowerment. In 2014, we'll focus on our <b>lead users</b>: 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= | =Contribution is our #1 metric= |
Revision as of 18:08, 9 January 2014
![]() |
Webmaker Roadmap 2014 | |
Owner: Webmaker Community & Product Team | Updated: 2014-01-9 | |
Vision: Mozilla Webmaker provides tools, community and badges that help people move from *using* the web to *making* the web. |
Please do not edit this page without permission.
Thank you!
Goal
In 2014, Webmaker's main mission is to:
- Get thousands of people teaching, building, and organizing as part of Webmaker.
- If we do this, we succeed.
This is Webmaker's committment 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. 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
How will our community contribute? By TEACHING, BUILDING and ORGANIZING
- TEACHING
- Teaching. Teaches web literacy with our stuff. In classrooms, informal spaces, at events.
- Curation. Discover and link to resources that help others learn and teach the web. Organize community-contributed content.
- Assessment. Review and critique learners' and mentors' work.
- Support. Help with documentation and Webmaker product support.
- Advocacy. Advance web literacy. Tell the story. Recruit more contributors.
- BUILDING
- Curriculum. Contribute to teaching kits, activities and resources aligned with the Web Literacy Map.
- Code. Pitch in on bugs, source code and patches to Webmaker tools, including experiments in new domains, such as Appmaker.
- QA and User testing. Ensure the quality of Webmaker offerings and participate in live and asynchronous testing.
- Localization. Remix (culturally or linguistically) curriculum and code that makese sense locally.
- Make API integration. Integrates with and buld on top of the MakeAPI.
- ORGANIZING
- Events. Hosts an aligned event (for Maker Party, Hive, etc.), a session (i.e. Mozfest, DML).
- Campaigns. Participate in / partner with Maker Party. Organize local campaigns and outreach.
- Hives. Establish new networks.
- Training. Train other trainers, teachers and mentors.
- Storytelling. Write blog posts, documentation and local stories.
2014 Priorities
What are we going to BUILD to support these goals?
- Web Literacy UX. Make Web Literacy the heart of our user experience on Webmaker.org.
- Curriculum. Flesh out the Web Lit map with great activities, lesson plans and ways to teach and learn.
- Engagement Ladder. Move users along an intentional ladder of engagement. Make it easier to get started, become more involved, and contribute. Clearer pathways, calls to action, documentation, celebration.
- Training. Teaching people how to teach the web. Professional Development for educators. Guides, MOOCs, human support. Well-packaged on webmaker.org.
- Product Support. Webmaker Product support systems. Documentation. SUMO management. (Question: who owns this now?)
- Events platform. Better UX. Capture data on both event hosts *and* event participants.
- Webmaker Badges. Aligned with the Web Literacy map. Ready for Maker Party 2014. (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.
- 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
- Webmaker UX re-design. Web Literacy 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, and plan
- MozFest. Key product announcements. Web lit PR and press push. Recognize and empower lead users. EOY campaign.
- Community growth focus: Celebrate