Q4 Priorities
-
Setting up static website for Appmaker
- what / why / how
- /teaching
- /getinvolved
- /code
- /values
- /components (listing of components w/ simulator?)
- /coolapps (move to home page when ready)
-
Enabling teacher feedback
- Setting up discussion forum for teachers
- Wiki or ?? for lesson plans
-
Get Involved
- Page for getting in touch:
- developers sent to github issues & IRC
- Teachers get sent to forum, wiki, workshop-feedback form
- workshop-feedback-form:
- name, location, school?, age-range of participants
- tells about who you taught? (how many people, what background)
- what worked well?
- what didn't work well?
- specific bug reports: please file in github issues, including steps to reproduce if you have them
- in app, have a bug report link
- Page for getting in touch:
-
Advertise Open Community Call
- Find someone to commit to run said call
-
Change /designer UI to:
- have CTA for coders & educators
-
Comms
- Weekly editorial calendar
- new stuff to play with: new component of the week
- new role model: app+user of the week (within context of teacher if appropriate)
- design question: a specific thing we actively want feedback on
- Twitter plan
- Highlight educators, users, stories, apps
- Weekly editorial calendar
-
Simple metrics integration to drive contribution & usage dashboard
-
Enabling localization
- pulling strings out (informed by MVC model)
- setting up transifex project
- merge & deploy process
- Surfacing localization in UI
-
Strengthening existing core:
- sign-in gets you redireted to user.appmaker.mozillalabs.com (security)
- pick test framework, write tests, mandate test for designer UI (quality)
- pick component test approach, write tests, mandate tests for new tier-1 components? (quality)
- pick MVC model, refactor UI (quality/agility). ember vs. angular?
-
Facilitate contribution
- land load-components-from-arbitrary-URL-in-personal-domain
- write /getinvolved page
- highlight contributions at mozfest on blog
-
Facilitate community around apps
- Allow apps to opt-in to disqus conversations about the apps
- per-app URL with disqus integration
- design the URL & page
- sign up for disqus w/ a wildcard domain (possible?)
- move to mozapps.org? better domain?
- per-app URL with disqus integration
- Allow apps to opt-in to disqus conversations about the apps
-
Make good components, esp. around data collection and use
- average # of components per app; avg. # of pages per app, avg # of page views per app.