Proposed - Lesson 3 - Using GitBooks to transparently share progress and content

[jduckles]

This lesson aims to demonstrate how GitBooks can be used to help manage funded Catalyst projects and other activities. GitBooks provides a coherent documentation

Prerequisite: Assumes basic understanding and familiarity with GitHub from Lesson 1 and Lesson 2

Objectives:

• Understand how GitBook and its structure can help you capture and share key progress indicators
• Demonstrate how distributed/shared contribution can lead to GitBook documentation that stays current.
• Build familiarity with text-based Markdown being "rendered" to styled web content.
• Beginning to understand how templates and structures can help to coordinate projects of many different type.

Key questions to community members (please respond below):

• What makes GitBooks a useful model for Catalyst projects?
• What are the limitations of GitBooks?
• Where have you become most confused if/when you've contributed to a GitBook repository?

[cauechianca]

What makes GitBooks a useful model for Catalyst projects? . .GitBooks is useful, in my point of view, for auditability and transparency (meetings/projects follow-up/general documentation), as well as knowledge transfer. . What are the limitations of GitBooks? . .Customization . Where have you become most confused if/when you've contributed to a GitBook repository? . .I had no problem in setting up the GitBook and adding content to it, but the interface is not quite intuitive.