Meeting notes

Met with Phil McCreanor & TCO Faculty to discuss notes and plan. Overall it looks tight, but reasonable.

Notes (reflected in text below where possible)

1. Basic and custom construction steps are not separate and should be merged.
2. Include safety guidelines
   • General construction tips
   • Child safety tips
3. Add section to documentation for Physical Therapists
   • Can be done after build
   • Contact P.T. Intern after build to discuss
4. Documentation (use case) should be "car-centered" as opposed to "step-centered."
   • i.e. one team will build one car as opposed to one team performing the same task(s) on all cars.
   • Documentation should be written to support self-paced assembly.
5. Video topics were discussed but the group decided that might be too complicated for this effort, however, individual tasks that would be suitable for video will be identified and prioritized with other tasks

Priorities for first round

1. Deliver before build date
2. Support access from stand-alone (LAN-based) host
3. Deliver documentation of "Basic construction" tasks
   • Identify basic tasks that SHOULD NOT be followed (e.g. those that are replaced by a custom step)
   • Include customization tasks
   • Detailed descriptions of fitting to the child are not required
   • General safety and construction guidelines
   • Produce overview video
4. Consider for follow on projects
   • Adding content targeted for Physical Therapists
   • Add more video content
   • Integrate documentation involvement with senior design projects
   • Investigate documenting follow-up studies and feedback after cars have been used for a while.
   • Consider additional "care and use" topics

To do

1. Phil to give Bob an assembly manual
2. Bob to have kickoff meeting, Mon 1/23
3. TC Faculty to pass the word to Engineering students in writing classes and recruit volunteers

---

Go Baby Go Build Documentation Plan

8 weeks until build (Mar 24-25, 2017) –less Spring Break

Key milestones

• March 13-17 Final integration and deployment
• March 6-11Spring break
• Feb 27-Mar 3 Implement edits identified during usability test
• Feb 20 – 24 Usability test content
• Feb 13 – 17Write procedural content based on SME interaction
• Feb 6 – 10 Conduct trial build with SMEs: document and photograph’
• Jan 30 – Feb 4Review tools and web site
• Jan 23 -27Kickoff and recruiting
• Jan 18 Prioritize content requirements

Key documentation content requirements (confirm and prioritize)

• Tools, parts and supplies list
  • Generic
  • Per car model
• Basic construction details
  • how much of the manual to follow
  • clarify confusing steps in the manual
  • what to build
  • what to customize—add, modify, remove (in the next step)
  • what NOT to build
• Common customizations
  • Horn button replacement
  • Master On/Off switch
• Child-specific adaptations
  • General guidelines
  • Gallery

Development and Deployment Details

• Use GitHub & Markdown for content, publishing, source code, and project management
• Jekyll produces a static HTML site
• Hosted at https://merceru-tco.github.io/GoBabyGo/ for free (on the web)
• Can be installed on any web server (e.g. AWS, PC running Apache or IIS)
• Basic site is running.
• Adding content can be as simple or as fancy as time and talent allow.