[placeholder]

[placeholder]

• Recap
  • OPW Project finished on 3/9
  • Project Blog
  • Project Branch
• Gists for quick review
  • Introduction
  • Design Principles
  • Page Layout and Structure
  • Visual Design
  • UI Elements
• Next Steps (Proposed)
  • Add "Work in Progress" disclaimer heading to each document, then move immediately to official repository
  • Establish a "Design Team"
    • Goals
      • Review the current guide, focusing on completeness and consistency
      • Expand the guide with rationale for design choices, ideally with references to external research
      • Establish an internal consensus, particularly in areas of high subjectivity
      • Create working HTML/CSS prototypes of all recommended UI elements
      • Present the result of the above steps for community review (and hopeful ratification) no later than June 30, 2015
    • Governance
      • The Team will be composed of volunteers, with at least two committers and two non-committer community members
      • Team members will agree to meet weekly until the guide is ratified
      • After the guide is officially accepted, the team will agree to meet every other month as caretakers to discuss ongoing application of the guide and potential refinements
    • Rationale
      • A style guide does not fit neatly into 'code' or 'docs', but has aspects of both, so the existing management structures are not ideal
      • The initial phase will be brief, but require committed focus
      • Good design for a group project means rising above individual instinct; doing so takes significant time and effort

• follow-up discussion from Kathy Lussier's message to the dev list