workshop redux

GITHUB

1) stores content (WACs), which is cloned to learndot 

2) github is the authoring tool/editing; learndot the publishing tool  

Option 1: Github as a store, learndot as a source of truth 

PROS: 1) GIT functionality, 2) rapid workshop development

CONS: 1) less than ideal authoring experience, 2) requires a ton of work, 3) will need to generate a reliable slug/integration system for interweaving WCAs with workshop-related objects (assessments, etc), 4) workshop creation occurs on github AND learndot 

LEARNDOT

1) GUI for workshops 

2) stores associated resources ("rich actions", e.g. reflections, assessments)

GITHUB

1) stores content (WACs), which is cloned to learndot 

2) github is the authoring tool; learndot the publishing tool  

Option 1: Github as a store, learndot as a source of truth 

1) create associated objects in learndot (reflections, assessments etc)

2) get the mongo ids for these associated types and represent them as slugs in github

3) edit workshop by going between the db and github

LEARNDOT

1) GUI for workshops 

2) stores associated resources (reflections, assessments)

Option 1: Github as a store, learndot as a source of truth 

Possible Configuration: 

1) concepts would be folders

2) actions would be md files

3) workshops are the entire repo

4) various directives for various action types 

GITHUB

1) workshops and all associated objects (assessments, reflections, etc) live exclusively in github. workshops are programs 

Option 2: Github as the source of truth

PROS: 1) further modularizes learndot (step toward microservices); 2) GIT functionality: rapid workshop development 

CONS: 1) requires the creation of a complete schema/yaml file for representing workshops and associated objects; 2) we'll have to deal with versions of the yaml syntax; 3) workshop authoring training session; 4) less than ideal workshop authoring experience 

LEARNDOT

1) GUI for workshops 

2) validator for the schema (pushing curricula to github)

Option 3: keep everything in learndot

PROS: 1) we can definitely create CLONING functionality; 2) could develop a "proposed change" functionality; 3) better authoring experience

CONS: 1) no branching/diffing/full-featured version control 2) approximates GIT but not as good 3) slow workshop development process 

LEARNDOT

1) workshop authoring 

2) workshop "cloning"