|
|
Line 1: |
Line 1: |
| =Webmaker Curriculum Requirements=
| | move to [[content]] |
| * Webmaker curriculum is a shared responsibility between the Webmaker Product and Community Teams
| |
| ** The '''Product''' team needs curriculum to be world class. It is the primary way users will experience webmaker.org
| |
| ** The '''Community''' team needs curriculum to be an effective on-ramp to contribution.
| |
| | |
| * '''Our shared goal''': fill the Web Literacy Map with outstanding teaching kits, open educational resources and activities that are creative, fun and deliver learning through making.
| |
| * We'll do that through:
| |
| ** 1) '''A community contribution campaign'''. Focused on one skill / competency at a time, working in the open with our lead users. Similar to a localization sprint or thermometer campaign.
| |
| ** 2) '''Contracted professionals'''. Domain experts who can build curriculum relevant to specific Web Lit skills. Work in tickets and deliver public facing work.
| |
| ** 3) '''Curation systems'''. Peer review and QA. Systems for reviewing and up-leveling the best work.
| |
| ** 4) '''Internal resourcing.''' Bespoke tools, content, and apps that team members from both Product and Community teams build. (e.g., building a specific app, video, or widget to help support a given teaching kit or activity.)
| |
| | |
| All of these methods should be given equal placement on webmaker.org, and ideally should re-inforce one another by providing great examples, a broad base of content types, and a built in audience.
| |
| | |
| =Curriculum Roadmap=
| |
| | |
| =Q1=
| |
| * '''Run community curriculum campaign'''. Invite lead users to help fill out the Web Literacy Map. Creating new stuff and gathering existing best-of-breed resources from across the web.
| |
| | |
| * '''Hire some leading lights from our community''' to help fill some aspects of the map (e.g., Remix, HTML/CSS, Privacy). Model best practices.
| |
| | |
| * '''Prototype some new tools that teach aspects of the map'''. Show how new tools and prototypes can help teach the Web Lit Map and publish to the MakeAPI.
| |
| | |
| =Q2=
| |
| Test, localize and train around that first batch of curriculum. Use that momentum to gather more new great curriculum from community.
| |
| * Deliverable
| |
| * Deliverable
| |
| * Delierable
| |
| | |
| =Q3=
| |
| Feed our curriculum into Maker Party. Tell stories about community using, adapting, and contributing that curriculum in the field. Leverage Maker Party as a giant field-testing, localizing and new curriculum contribution sprint.
| |
| * Deliverable
| |
| | |
| =Q4=
| |
| Key milestone / change of state / narrative
| |
| * Deliverable
| |
| | |
| =Tickets=
| |
| * Tagged "Pathways" (coming soon)
| |