How to contribute to design  

Anchor
how how

Design within the Fluid community is done in an open, transparent, and collaborative manner. All are welcome to contribute design thoughts, feedback, files, etc. to the community and all are encouraged to participate through the various communication channels.

Design is not done in any one place within the Fluid community, but all work is done in an open space that can be shared broadly. The work should be regularly presented to the larger community (with an intention of getting feedback or ideas). Designers should use appropriate communication channels to update the community with design progress, share current work, receive feedback, share and discuss ideas, ask questions about technical feasibility, and so on.

Best practices:

• use a service that allows collaborators to openly share file iterations with the rest of the community while maturing design thinking 
• at the point where the design is being presented, the file and any accompanying narrative is uploaded to the wiki and preserved there as a milestone in the design work

Sample Design Artifacts 

Anchor
sample sample

Design on Fluid projects produce a wide range of artifacts, both in-process and final delivery. The following list outlines and provides examples of some of the more common artifacts. The list should not be construed as a comprehensive catalog of artifacts that should be produced, but rather as a representative sampling of the artifacts that come out of Fluid's design process.

Conceptualization

• Mindmaps

  • (Floe) Concept design mindmap problem space and inclusiveness in OERs
  • (Floe) Landscape of Content Alternatives, Transformations, Customizations
• Flow charts
  • Decapod Workflow
  • PCP diagrams 
• User modelling
  • Fluid Personas
  • (Floe) User states and contexts
• Use cases & scenarios
  • (Floe) use cases
  • (Floe) Scenario Narrative: Vision of the future OER

Prototyping

• Sketches

  • Kiosk idea sketches (Dec. 15, 2009)
• Lo/mid-fidelity wireframes
  • Mobile wireframes (Draft 9), 
  • (Floe) OER Commons authoring tool wireframes, design iteration x + 1
  • (Floe) UI Options Design Wireframes, C.1
• Mid/hi-fidelity mockups
  • (Floe) OER Commons authoring tool high fidelity mockups (February)
  • (Floe) UI Options Design High Fidelity, C.1
• Annotations, storycards
  • Mobile storycards, home, draft 9
  • Floe video player wireframes (November 2011)
• Mockups for user testing

  • PCP mockups for paper prototype testing

User testing

• Protocols

  • (Floe) UI Options user testing protocol (February 2012)
  • Mobile user testing protocol (Draft 9, Engage 0.3)
• Data/results
  • (Floe) UI Options user testing report (April 2012)
  • Mobile user testing results (Draft 9, Engage 0.3)

Style & interactive guide

• Preference Management Ecosystem Features Functionality June 7 
• (Floe) UI Options Design Specifications, C.1

 In progress design files can be currently found in this Dropbox folder and older design files can be found in the Fluid SVN repository.