Simon Bennetts

Enable "Edit on GitHub" in more pages

1

Enable on: - [x] FAQs - [x] Guides - [ ] User Guide (requires changes in help converter) - [x] Blog posts - [ ] ? --- How about we...

Ideally lightweight and optional. Blog posts would be an obvious use for them https://cloudcannon.com/tutorials/2017/02/01/lightweight-social-share-buttons/ looks promising

We're now adding security headers via cloudflare, so we should also add as strict a CSP as we can. But this will need careful testing ;)

Scripts run from the command line should output in JSON, or at the very least have an option to do this.

And the cli should report the missing ones

All elements should define a standard text representation, so that we dont end up with different implementations using different notations. In theory someone could write a parser for these :)

There is no such thing as a regex standard: http://www.regular-expressions.info/refflavors.html So we need to define a subset of regex expressions that can be safely used in Zest scripts. eg see...

This was a pragmatic 'hack' which was useful at the time, but means that scripts have an 'index' field that doesnt really make sense.

As per the 'Int' one already added, but should allow rnadom 'sentances' to be built up. eg minWords maxWords minLettersPerWord maxLettersPerWord maybe even support different character sets?

It should be easy to create a JUnit test from a Zest script, eg using a simple wrapper?