shuttle-hq
Add warning about outdated code in blog posts
Shuttle is in rapid development and code snippets in blog posts may be out of date, we should add a warning about this to the posts as well as a link to examples/docs.
If we're looking to do this, how far back would we say is enough for this? As soon as we update to a new version?
The reason we never got to this is we had hopes that we could keep them all up-to-date, but I think it's fair to say now that we won't (or at least not until we stabilize). I think we should add a small warning to the start of all of them, to be honest. cc @ivancernja
As an update on this: I think we should just bite the bullet and keep updating the articles. It will help our SEO in the long run and is not such a big deal.
cc @ivancernja