Webmaker/Mentor/Roadmap/Website: Difference between revisions

Jump to navigation Jump to search

Webmaker/Mentor/Roadmap/Website (view source)

Revision as of 14:21, 17 July 2013

279 bytes removed ,  17 July 2013
no edit summary
No edit summary
Line 15: Line 15:
<br>
<br>
[[File:Teach.png|800px]]
[[File:Teach.png|800px]]
<h1>TLDR</h1>
What are we going to do next with [https://webmaker.org/teach webmaker.org/teach]?
* <b>Ship great new teaching kit <u>templates</u></b>. With new and improved graphic design. Drawing on our new Webmaker.org style guide.
* <b>Polish up our best teaching kit <u>content</u></b>. Focus on our "top 10" teaching kits. Brush up content strategy, copy and design for that small number of "cream of the crop" kits.
* <b>Make sure <u>Maker Party</u> and Partner content really shine</b>. Look for quick wins here. Maker Party is the urgent priority -- how do we focus our work there?
<br>
plus...
* <b>Better links for staying in touch and getting more involved.</b>
* <b>And then: better contribution workflow</b>. We're blocked on some technical issues here. So let's sprint on the stuff above, cuz its under our control. But better contribution and curation is the next urgent priority.
<br>
= Key Goals =
short term:
* <b>provide great baseline content</b>.
* <b>keep #teachtheweb MOOC momentum rolling</b>. Make sure those folks stick around and don't dissipate.
* <b>support Maker Party partners and mentors</b>. Mentors and event organizers are at the heart of Maker Party.
<br>
medium term:
* <b>align with the Web Literacy Standard and badges</b>. Let's build *one* great educational product on Webmaker.org. Tying these pieces together.
* <b>get ready for MozFest</b>. see MozFest as another giant potential teaching kit sprint. improve the funnel, so that we can pour a ton of great new content in. Make this process *easy,* immediate and *self-serve*, so we can focus on capturing the next great innovations at MozFest.
<br>
longer term:
* <b>streamline metrics and mentor comms infrastructure</b>. Mentors: we need easy ways to a) count 'em and b) communicate with 'em. Right now we have a diverse mix of channels, which is natural -- but how do we collect more actionable data and streamlined comms going forward?
[[File:Webmaker Teach product.005.jpg|800px]]
= What are we building? =
<b>5 key pieces</b>. We can think of [https://webmaker.org/teach webmaker.org/teach] as a <b>product</b> with five key elements:
* 1) <b>Recommended Teaching Kits</b>. Outstanding teaching kits, educational resources and HOWTOs for teaching the web. This is the "cream of the crop" content. Some teaching kits are better than others -- let's ensure the best content is front and center.
* 2) <b>Templates for making your own</b>. Easy ways to make and share your own teaching kits.
* 3) <b>Community-generated content</b>. A searchable / filterable gallery of community-generated teaching kits. The number of these is going to increase exponentially -- so we need solid <u>curation</u>, <u>tagging</u> and <u>search</u>.
<br>
plus
* 4) <b>Easy ways to stay in touch and get more involved</b>. <u>Especially for people to earn their Webmaker Mentor badge</u>. We need webmaker.org/teach to provide "one stop shopping" and be *the* on-ramp for anyone who wants to teach the web -- which means we need to un-bury things Mentors are looking for and use language they understand. (the current /teach page misses some of this.)
* 5) <b>Data</b>. Metrics. So we can optimize and steer. (e.g., which kits are most popular? where is the traffic coming from? What skills or competencies are people asking us to create resources for?)
<br>
plus coming soon:
* 6) <b>Web Literacy Standard + badges</b>. Align with the standard. Use badges as a way of recognizing quality of guides and that Mozillians have vouched for them.
<h2>What are we going to focus on first?</h2>
<b>For the weeks of July 8, 15 and 22</b> we're focusing on (1) and (2) above. Why?
* <b>Because they're already in active use</b>. And can help tie into Maker Party fast.
* <b>Because we're blocked on 3</b>. But expect to have that cleared soon.
* <b>Because 2 makes both 1 and 3 better</b>.
<br>
http://farm6.staticflickr.com/5336/9243169266_cd7d912372.jpg


==July 15==
==July 15==
Line 106: Line 60:
<br>
<br>
http://farm3.staticflickr.com/2832/8939658310_397e7c33d6.jpg
http://farm3.staticflickr.com/2832/8939658310_397e7c33d6.jpg
<br>
=Overall Goals and Context=
<h1>TLDR</h1>
What are we going to do next with [https://webmaker.org/teach webmaker.org/teach]?
* <b>Ship great new teaching kit <u>templates</u></b>. With new and improved graphic design. Drawing on our new Webmaker.org style guide.
* <b>Polish up our best teaching kit <u>content</u></b>. Focus on our "top 10" teaching kits. Brush up content strategy, copy and design for that small number of "cream of the crop" kits.
* <b>Make sure <u>Maker Party</u> and Partner content really shine</b>. Look for quick wins here. Maker Party is the urgent priority -- how do we focus our work there?
<br>
plus...
* <b>Better links for staying in touch and getting more involved.</b>
* <b>And then: better contribution workflow</b>. We're blocked on some technical issues here. So let's sprint on the stuff above, cuz its under our control. But better contribution and curation is the next urgent priority.
<br>
= Key Goals =
short term:
* <b>provide great baseline content</b>.
* <b>keep #teachtheweb MOOC momentum rolling</b>. Make sure those folks stick around and don't dissipate.
* <b>support Maker Party partners and mentors</b>. Mentors and event organizers are at the heart of Maker Party.
<br>
medium term:
* <b>align with the Web Literacy Standard and badges</b>. Let's build *one* great educational product on Webmaker.org. Tying these pieces together.
* <b>get ready for MozFest</b>. see MozFest as another giant potential teaching kit sprint. improve the funnel, so that we can pour a ton of great new content in. Make this process *easy,* immediate and *self-serve*, so we can focus on capturing the next great innovations at MozFest.
<br>
longer term:
* <b>streamline metrics and mentor comms infrastructure</b>. Mentors: we need easy ways to a) count 'em and b) communicate with 'em. Right now we have a diverse mix of channels, which is natural -- but how do we collect more actionable data and streamlined comms going forward?


<h1>Next steps</h1>
[[File:Webmaker Teach product.005.jpg|800px]]
* Gather feedback from Mentor Team on this roadmap.
= What are we building? =
* Add links to Bugzilla tickets above. And file new tickets as needed.
<b>5 key pieces</b>. We can think of [https://webmaker.org/teach webmaker.org/teach] as a <b>product</b> with five key elements:


=Feedback for next version=
* 1) <b>Recommended Teaching Kits</b>. Outstanding teaching kits, educational resources and HOWTOs for teaching the web. This is the "cream of the crop" content. Some teaching kits are better than others -- let's ensure the best content is front and center.
* <b>Wed, July 10</b>: [https://etherpad.mozilla.org/Mentor-Website-Roadmap we collected some initial mentor team feedback here]
* 2) <b>Templates for making your own</b>. Easy ways to make and share your own teaching kits.
* 3) <b>Community-generated content</b>. A searchable / filterable gallery of community-generated teaching kits. The number of these is going to increase exponentially -- so we need solid <u>curation</u>, <u>tagging</u> and <u>search</u>.
<br>
plus
* 4) <b>Easy ways to stay in touch and get more involved</b>. <u>Especially for people to earn their Webmaker Mentor badge</u>. We need webmaker.org/teach to provide "one stop shopping" and be *the* on-ramp for anyone who wants to teach the web -- which means we need to un-bury things Mentors are looking for and use language they understand. (the current /teach page misses some of this.)
* 5) <b>Data</b>. Metrics. So we can optimize and steer. (e.g., which kits are most popular? where is the traffic coming from? What skills or competencies are people asking us to create resources for?)
<br>
<br>
plus coming soon:
* 6) <b>Web Literacy Standard + badges</b>. Align with the standard. Use badges as a way of recognizing quality of guides and that Mozillians have vouched for them.
<h2>What are we going to focus on first?</h2>
<b>For the weeks of July 8, 15 and 22</b> we're focusing on (1) and (2) above. Why?
* <b>Because they're already in active use</b>. And can help tie into Maker Party fast.
* <b>Because we're blocked on 3</b>. But expect to have that cleared soon.
* <b>Because 2 makes both 1 and 3 better</b>.
<br>
<br>
http://farm6.staticflickr.com/5336/9243169266_cd7d912372.jpg
Matt Thompson
Confirmed users
9,624

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/677191"

Navigation menu