Change: don't write new HAML pages (make using Vue easy (and fun*))

Change pattern proposal: HAML to Vue

Old Pattern

1. Some pages use HAML only
2. Some use HAML to initialize a Vue app

New Pattern

1. For new code, Vue exclusively. Templates & data-passing from Rails will be standardised and you won't write haml files anymore
2. ongoing refactor/cleanup of existing HAML, and eventually aim to Vuenify our codebase?

Advantages of switching patterns

1. End the "we need to support haml + vue" argument that always stalls CSS decisions
2. Consistent codebase
3. No more basically-the-same-except-for-some-values for all our Vue initialization (template with a .js-whatever element and a bunch of data attributes. These files are pretty low value

Disadvantages of switching patterns

1. We have an insurmountable existing amount of HAML. This will probably require a codemod or some automation to effectively happen
2. Switching templates is risssssssky. Since we don't really test that integration point there is a lot that could potentially break.

What is the impact on our existing codebase?

We will continue to have HAML for a long time. But if we know that you don't create new HAML