Refactor deployment, default branches about vf-core

[khawkins98]

I think we need some way for, say, WP to opt in to changes. So it might be running on alpha.1 but not be ready yet for alpha.2

[khawkins98]

I need to rope Peter into this one, so we won't get here until alpha.3

[sturobson]

We could have an NPM package of the versioned compiled CSS … and use unpkg for the urls that people use?

[khawkins98]

I've pinged Peter on this earlier in the week, him and Sandeep should hopefully be tackling soonish.

[peter-walter]

Do we want the tags so granular in the deploy path?
assets.emblstatic.net/vf/v2.0.0-alpha.1
or
assets.emblstatic.net/vf/v2.0

[peter-walter]

Discussion outcomes
https://docs.google.com/document/d/1ZtTR8V28orNgqsOwuKpAGfFOgtlBPQn3dOgh22GhM3c/edit

Pull request
#304

[khawkins98]

Now sorted by #304:

• https://dev.assets.emblstatic.net/vf/develop/
  • https://dev.assets.emblstatic.net/vf/develop/css/styles.css
• https://dev.assets.emblstatic.net/vf/{tag}/ (eg v2.1.2)
  • https://dev.assets.emblstatic.net/vf/v2.0.0-alpha.1/css/styles.css
• https://dev.assets.emblstatic.net/vf/{minor}/ (eg v2.1)
  • https://dev.assets.emblstatic.net/vf/v2.0/css/styles.css
• https://dev.assets.emblstatic.net/vf/{major}/ (eg v2)
  • https://dev.assets.emblstatic.net/vf/v2/css/styles.css

Won't be available until we merge to master, leaving this issue open until we have confirmation,

[khawkins98]

Looks like this is now working with @pwalter-ebi 's most recent edit (#309).

Tagged releases will be added as they're made (so no alpha.1/2/3).

Leaving open as a documentation task.

[khawkins98]

It works 🎉

https://dev.assets.emblstatic.net/vf/v2.0.0-alpha.4/css/styles.css