Closed Bug 899594 Opened 11 years ago Closed 11 years ago

[Documentation] MAKE best practices resource for Community produced documents

Categories

(Webmaker Graveyard :: General, defect)

Product:
Webmaker Graveyard
Component:
General
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: laura, Unassigned)

Details

We should create a best practice tips and tricks on how to create community produced documents to include on /teach. These notes from Doug & the WebLitStd community.

From the Webmaker Call:    

If you were to develop another community-driven document like this again, what would you do differently? What worked well? Seems like lots of great learning / practices to draft this together. (we should make a quick tip sheet for this, great for including in the /teach page ;) FILING! )  Yes - this really was a model project for effective work in a distributed team on a complex task - well done Doug.

    Overshare everything.+1

    Record calls.

    Listen to Gunner. :-)

    Use the tools that work, don't just get hung up on what you're initially using. 

    Listen to Dan Sinker. :-)

    Articulate the end-goal. 

    Have a call mantra. +1
@ Laura: I'm not sure I understand what this is, exactly.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Component: Community → General
You need to log in before you can comment on or make changes to this bug.