examples should be listed and importable from UI

[nikhan]

/examples should contain only .json files that are ST patterns. it may be helpful to have a JSON manifest of examples, so that we can attach notes to each pattern (this may not be necessary if we add comment blocks of some sort). ie, "bikes.json": "in this pattern we use citibike data blah blah blah"

the entire /examples directory should be compiled into the binary, just as the /static directory is compiled into the binary. a list of patterns should be present in the UI, so the user can just select which example they want to import.

[mikedewar]

worth separating out instructive examples (like the citibike example) from useful patterns (like an http poller)?

[mikedewar]

AKA what's the use case?

[nikhan]

i think both are valid use cases -- it may be helpful to separate them out. I was wondering the same thing when I thought about an A/B test example. Is that a recipe (drop in the pattern and use with your own A/B test) or is it an example of an A/B test?

[jacqui]

I somehow missed this issue. I like the idea, and I'd like to further complicate it by adding in the idea of the streamtools patterns repo (unfortunately still in the works)... adding @friej715