Status

Development status

The mile-high picture of where we're at. When all boxes are checked in the following 2 lists, we've reached cruising speed.

Glossary content

• Issues created for initial terms:
  • Dropped terms
  • Primary terms (about 50% done)
• Source files started for initial primary terms (1%)
• Initial term definitions production ready ( <1%)

"Initial" means the glossary terms that collaborators came up with when the project was kicked off in Google Drive. We're migrating the project to GitHub as Phase I, so the initial set of terms is a convenient way to monitor status until a rolling (Phase IV) state is achieved.

Development

• Collaborative protocols established (using issues and using issue labels)
• Glossary architecture conceived (production glossary structure)
• Wiki docs written
• Production site set up with Google Page & Jekyll (Glossary Index
• Definition template created (writers can use this now, see Using the definition template)
  • Semantic schema (JSON-LD) added ⬅︎ Development currently here!
  • Accessibility attributes added to template
• Glossary index template fully constructed and file tree functioning as index lists
• Custom subdomain set up (e.g. glossary.csf.community ) — TENTATIVE

If we go forward with the custom subdomain, it won't be secure "https", because you can't set up true Secure Socket Layers (SSL) on GitHub Pages if you use any kind of custom domain. (It's currently secure with GitHub's default URL.) It's possible to use Cloudflare as an intermediate solution, but we're not setting up a Cloudflare account for the sole purpose of this project.