Project phases
We'll remain a little flexible on this, but following are the high-level stages of development from draft to production.
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:
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:
As outside collaborators (writers and editors) continue to develop glossary definitions in phase II, project managers will begin adding the production resources to the master repository. This effectively turns the master repository into a kind of flat-file database that powers a live glossary website, as depicted in the following figure.
Anyone with Jekyll website design/development experience is welcome to help with this phase, if it doesn't get done sooner.
See Production glossary structure for more specifics about production development and design.
Basically this is phase II in "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. And when phase III is complete, such changes are automatically reflected in the production site.
Using issues will be central to the ongoing collaboration process.