Project phases

We'll remain a little flexible on this, but following are the high-level stages of development from draft to production.

I) Migration from Google Drive

To get settled into GitHub, we need to get all prior work in Google Drive migrated over, including decision history of respective terms. For purposes of this stage, and because using issues will be central to our collaborative communication, we'll start with all terms considered so far. See instructions for:

• Migrating glossary terms
• Migrating initial drafts

II) Drafts development

This phase is basically the ongoing collaboration routine; developing glossary entries from approving target terms to production ready status.

Anyone can do this now, no matter your comfort zone with GitHub:

• You have a GitHub account and know how to make pull requests.
• You're new to using GitHub.

III) Production site development

The production glossary will be built as a flat-file, Jekyll website on GitHub. As such, the site will update automatically from the collaborative draft files in the repository. This offers many advantages over an otherwise awkward workflow step of manually porting repository files to an offsite location build with a dynamic database system.

This still enables using a custom domain, expected to be glossary.csf.community.

This work will be taking place now around the phase II collaboration of writers and editors, but the site won't launch until a majority of the glossary's terms/definitions are production ready.

IV) Evolution

Basically this is phase II again on "continuous" mode. The glossary is rolling, meaning it's always growing, reducing, refining... The repository is the collaborative epicenter where all evolutionary changes are made. Using issues will be central to the ongoing collaboration process.