When building mortar templates, include a full set of Mozilla-provided x-tag elements. This is likely to contain some sort of build-and-minify step, which may happen on the x-tag side or mortar, not sure.

The list of tags is actually defined in the Q4 devhub spec: We need a mechanism to bundle precisely these tags. https://docs.google.com/document/d/1--E8zdyU8hEJIpEId-RBt8f9JLD42WJBvs6NRvqqgLk/edit

I'm confused... is this for a long-term goal? I thought we decided that we need to build mortar into something useful without x-tags for the short-term, and see how x-tags plays out. When it matures we can see how it can benefit what we're giving user's with mortar.

Unassigning for now. This bug will be blocked by getting the individual tags ready for prime-time.

Just so we're clear, if we want to create templates that do not utilize custom elements for layout due to the October 20th time constraint, that is fine - but the deliverable for Q4 is an initial set of custom elements that adhere to the Gaia style set, thus bundling with Mortar needs to happen before Jan 1. To that end, we've create a repo that will house all the supported tags that are tuned for the Gaia interface norms and styles, they will live here: https://github.com/mozilla/gaia-custom-elements

That works for me. Pulling tags into mortar won't be a big deal, the real work needs to happen on the tag side: Gaia styles, solid functionality, and last but not least dev docs for every tag. Arron: I filed the first "vet this" bug for the individual tags yesterday, please let me know if that makes sense.

Closing this more generic bug in favor of the individual template bugs we opened.