2 implementations we've discussed:

1. Create a migration to add default templates to all_campaign. If changes need to be made to these templates, updates will require a new migration to be written as well as a new Spoke release.
2. Maintain a JSON document that contains the set of default templates in a public S3 bucket. A daily running graphile-worker job can upsert these templates into the DB. If changes need to be made to these templates, they can be synced to all instances by edits to the document.

A variation on 2 is to have the JSON (or YAML) manifest publicly accessible (GCS bucket or GitHub pages for this repo) and then have a "Create from Library" option that lets the user pick from the list. Rather than loading everything into Spoke ahead of time.

A variation on 2 is to have the JSON (or YAML) manifest publicly accessible (GCS bucket or GitHub pages for this repo) and then have a "Create from Library" option that lets the user pick from the list. Rather than loading everything into Spoke ahead of time.

@politics-rewired/organizing thoughts on the above?

@bchrobot We like that!
There could be a third option from the create campaign + with "Create from Library" or "Create from Spoke Rewired Library"

@kohlkenn @politics-rewired/client-success I'm starting implementation of the Campaign Library mentioned above - I'd love to have some examples of potential "default campaigns" to use for testing; specifically the title, interaction steps and campaign variables for campaigns that might be included in the library.

pinging @ajohn25 about the above as well!