Webmaker/Roadmap: Difference between revisions
< Webmaker
Jump to navigation
Jump to search
Brett Gaylor (talk | contribs) No edit summary |
|||
| Line 11: | Line 11: | ||
{{DoNotEdit}} | {{DoNotEdit}} | ||
== Priorities for the year: == | |||
* Iterate on what "webmaker content" looks like, measure how users react | |||
** starting point: "webmaker lets you make content that is irresistibly hackable" | |||
* Encourage learning by making | |||
** lean into connected learning - make our tools fun, easy and empowering | |||
** Measure learning through badges | |||
* Develop webmaker experiences that work in the spaces where users live online | |||
** Frictionless sharing to Twitter, Tumblr + Facebook | |||
** Facebook app | |||
** Constrained mobile experience | |||
* Localization | |||
* Develop a method for external partnerships / developers to influence codebase | |||
** ability to fork our codebase and submit pull requests that we can integrate | |||
** ability to activate external libraries, eg Processing.js | |||
* Expose enough "code" (e.g., markup) for users to learn web mechanics if desired | |||
* Make working open and agile both work | |||
== Development process == | |||
<ul><li>Ship a release a week</li | |||
><li>Focus on early wins that help users make more things, more easily</li | |||
><li>Integrate with Product Marketing to source and build excitement about new content, features</li | |||
><li>Metrics-driven, user-driven priority decision making as we go vs. spec'ing out a year of features now and locking into that.</li | |||
><li>Content possibilities and types drive product priorities: we build tools to support creators vs. hoping creators will find uses for the tools<br/><br | |||
/></li></ul | |||
> | |||
== Content process == | |||
<ul><li>Think like a newsroom - react quickly</li | |||
><li>Enter and participate in popular culture<br/><br/></li> | |||
</ul> | |||
== Q1 Priorities == | |||
=== P1 === | |||
==== Popcorn Maker ==== | |||
<ul> | |||
<li>Immediate creation and testing of content types with existing tool features (content)</li | |||
> | |||
<li>Sequencing in Popcorn Maker</li | |||
><li>Fix remixing flow</li | |||
><li>A series of known Popcorn Maker UX fails:<ul><li>Undo</li | |||
><li>Event defaults (remove tedium of changing fonts, for instance)<ul></ul | |||
></li> | |||
<li>Fix weird escaped characters (a byproduct of our security efforts) | |||
Allow users to add an amount of time to an event (not simply the duration of the event)</li | |||
> | |||
<li>Fix layout of tray / make it resizable</li> | |||
<li>Position new events at mouse location</li> | |||
<li>Make default new layer on top</li> | |||
<li>Change background colour of canvas</li> | |||
<li>Allow users to add an amount of time to an event (not simply the duration of the event) | |||
<li>Twitter cards (Thimble + Popcorn Maker)</li></ul> | |||
</li> | |||
<li>Extend default embed page to include data about views, other remixes, etc. (i.e., start to explore gallery-like ideas from that single page)</li> | |||
<li>Facebook<ul><li>Research being a Facebook App</li | |||
><li>UX work to fit in their box size</li | |||
><li>Initial version of our app working in FB, with lots of follow up</li | |||
><li>Facebook Auth</li | |||
> | |||
</ul></li> | |||
</ul> | |||
==== Webmaker.org ==== | |||
<ul> | |||
<li>A "firehose" gallery of everything people are making with our tools, sortable by most recent and most viewed<ul><li>First iteration is an internal tool used to highlight and celebrate what users make</li | |||
><li>Following iteration is public facing</li></ul | |||
></li | |||
> | |||
<li>A "mentors" top level page on webmaker.org linking out to community resources<ul><li>w/ review</li></ul | |||
></li | |||
> | |||
<li>Refresh voice and tone, celebrate press of popcorn maker etc</li | |||
> | |||
</ul> | |||
==== Thimble ==== | |||
<ul> | |||
<li>Embedding in Thimble | |||
<li>Remix button in thimble | |||
<li>Fix Thimble project creation<ul><li>html5 linting for projects we publish vs. full review</li></ul> | |||
</ul> | |||
=== P2 === | |||
<ul> | |||
<li>Support.webmaker.org</li> | |||
<li>User project submission</li> | |||
<li>Localization | |||
<li>Facebook app | |||
<li>Instruction Layer | |||
<li>Developer documentation | |||
</ul> | |||
== Beyond Q1 == | |||
<ul> | |||
<li>Exposing HTML/markup in Popcorn Maker</li> | |||
<li>Collaboration</li> | |||
<li>Mobile App</li> | |||
<li>Revision History | |||
<li>Badges in Popcorn Maker<ul><li>upon completion of OBI 1.0 | |||
<li>Remixing within embeds | |||
</ul> | |||
Revision as of 22:48, 4 February 2013
| Webmaker 2013 Roadmap | ||
| Owner: Brett Gaylor | Updated: 2013-02-4 | |
| Vision: Building a generation of webmakers. 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!
Priorities for the year:
- Iterate on what "webmaker content" looks like, measure how users react
- starting point: "webmaker lets you make content that is irresistibly hackable"
- Encourage learning by making
- lean into connected learning - make our tools fun, easy and empowering
- Measure learning through badges
- Develop webmaker experiences that work in the spaces where users live online
- Frictionless sharing to Twitter, Tumblr + Facebook
- Facebook app
- Constrained mobile experience
- Localization
- Develop a method for external partnerships / developers to influence codebase
- ability to fork our codebase and submit pull requests that we can integrate
- ability to activate external libraries, eg Processing.js
- Expose enough "code" (e.g., markup) for users to learn web mechanics if desired
- Make working open and agile both work
Development process
- Ship a release a week
- Focus on early wins that help users make more things, more easily
- Integrate with Product Marketing to source and build excitement about new content, features
- Metrics-driven, user-driven priority decision making as we go vs. spec'ing out a year of features now and locking into that.
- Content possibilities and types drive product priorities: we build tools to support creators vs. hoping creators will find uses for the tools
Content process
- Think like a newsroom - react quickly
- Enter and participate in popular culture
Q1 Priorities
P1
Popcorn Maker
- Immediate creation and testing of content types with existing tool features (content)
- Sequencing in Popcorn Maker
- Fix remixing flow
- A series of known Popcorn Maker UX fails:
- Undo
- Event defaults (remove tedium of changing fonts, for instance)
- Fix weird escaped characters (a byproduct of our security efforts) Allow users to add an amount of time to an event (not simply the duration of the event)
- Fix layout of tray / make it resizable
- Position new events at mouse location
- Make default new layer on top
- Change background colour of canvas
- Allow users to add an amount of time to an event (not simply the duration of the event)
- Twitter cards (Thimble + Popcorn Maker)
- Extend default embed page to include data about views, other remixes, etc. (i.e., start to explore gallery-like ideas from that single page)
- Facebook
- Research being a Facebook App
- UX work to fit in their box size
- Initial version of our app working in FB, with lots of follow up
- Facebook Auth
Webmaker.org
- A "firehose" gallery of everything people are making with our tools, sortable by most recent and most viewed
- First iteration is an internal tool used to highlight and celebrate what users make
- Following iteration is public facing
- A "mentors" top level page on webmaker.org linking out to community resources
- w/ review
- Refresh voice and tone, celebrate press of popcorn maker etc
Thimble
- Embedding in Thimble
- Remix button in thimble
- Fix Thimble project creation
- html5 linting for projects we publish vs. full review
P2
- Support.webmaker.org
- User project submission
- Localization
- Facebook app
- Instruction Layer
- Developer documentation
Beyond Q1
- Exposing HTML/markup in Popcorn Maker
- Collaboration
- Mobile App
- Revision History
- Badges in Popcorn Maker
- upon completion of OBI 1.0
- Remixing within embeds