add next.strudel.cc or similar

[felixroos]

• [ ] use next.strudel.cc (or similar) to deploy the main branch
• [ ] use strudel.cc only for released versions
• [x] add each version as a separate url, like v1.0.0.strudel.cc/

[felixroos]

thanks to @yaxu, the subdomains for each version now exist through slab.org:

• http://v0.0.2.strudel.cc (ah the tutorial didn't build)
• http://v0.0.3.strudel.cc
• http://v0.0.4.strudel.cc
• http://v0.3.0.strudel.cc
• http://v0.4.0.strudel.cc
• http://v0.5.0.strudel.cc
• http://v0.6.0.strudel.cc
• http://v0.7.0.strudel.cc
• http://v0.8.0.strudel.cc
• http://v0.9.0.strudel.cc
• http://v1.0.0.strudel.cc

[felixroos]

related ideas:

• redirect from strudel.cc to the latest released version immediately, like right now, strudel.cc would redirect to http://v1.0.0.strudel.cc/ . The benefit of this would be that shared links will also be versioned, so they can't break in the future.
• The web component of @strudel/embed, the one that embeds the website as an iframe, should use its package version to pick the version of the site to embed, for example @strudel/embed@1.0.0 should embed http://v1.0.0.strudel.cc/. The used version could potentially also be set using an attribute
• When someone presses share, the used strudel version could be saved as well. This info could then be used to filter the list of shared patterns to only show patterns shared with that version (maybe all can be toggled on as well).

The underlying theme of these idea is: When you share a pattern in any way (by copy pasting the long url or by generating a share link or by embedding it on your website), the version should be pinned + the user should not have to do extra steps to make that sure that happens.

Maybe there could even be a version select box in the website, to change between subdomains, allowing you to test / share your pattern in a different version.