I know that we support multiple versions of a template where one can be set as active. But should we actually recommend customers doing it? How is it more preferred than maintaining two different templates for stable and staging?
I would also like@bpmct and@ammario thoughts on this example.

We've just been operating on the assumption that the functionality is there, if people want it.
I only include this example as we currently don't have a great way to otherwise communicate that these versions in the list don't represent a single version on the Coder deployment, and rather are a 'branch' of versions. Though maybe that can be reasonably deduced with one item in the list?

I agree that this example is a best demonstration of the full capability of the provider.