issue with the modal Vue component

Having issues with this…might create a PR sometime but Tristan would likely need to do last bullet.

documentation: no mention that an empty #mounted element needs to exist in markup - can we overwrite this name similarly to how we can overwrite other classes via a prop?
documentation: can we talk about how this relies on portal-vue as a dependency? this is not an issue if you use Boilerplate, but I brought this to an existing project Imarc project and wasn't sure what was wrong initially
- the notes say that this package sends the content to the end of <body> but I am not seeing that
documentation: we have an accordion mention in there
we give no z-index to this and it appears under other elements on a page that create a new stacking context
it's good we put focus into the modal when it's open but we should probably be limiting the focus to the modal. right now, a user can continue tabbing through the rest of the document
we might consider implementing the close button in a way that does not use font-size: 0. this way, if someone actually wanted text for their close button, they could
we might consider renaming props to be more intuitive. closeButtonElement to me implies that I could specify what DOM element to use (e.g. a <div> instead of a <button>) but it's just to control the naming. They all use this Element convention but the block prop does not
modal was stripping my HTML. Tristan's fix is: Modal should be able to discern between encoded content or straight html, whether by sniffing it out automatically, or via boolean prop.

Happy to check out a PR - seems like good stuff to address.

We can make the documentation clearer (maybe we can import portal-vue into just this component?), but in general, if you're using any part of boilerplate you should assume you need all the dependencies of boilerplate, and if you're going to try to use less you should expect to have to troubleshoot dependencies.
Re: the second to last bullet, it's referencing elements from BEM/ABEM; using block for the block and ${block}__${closeButtonElement} (for example) for a BEM element. Theoretically if we let people custom the a modifier class, I'd think we use something like ${block}__${someElement}--${someModifier} or ${block__${someElement} -${someModifier}.

imarc / boilerplate