Make queso-ified templates the default

[mandicai]

Todos:

• Have a meeting with design to audit some of our graphic styles. Before moving our templates to fully use queso, we should make sure our current graphic styles are what we want. Once we do the audit, we can figure out which custom styles we want to keep and which to start getting from queso.

Changed

• templates/__common__/_package.json - bump version of queso-ui.
• templates/feature/app/index.html - changed ad inputs, added comments, set variable for feature data
• templates/feature/app/templates/macros/processors.html - added CSS classes to list component, fixed ad component inputs (to allow us to process ads fetched in the ArchieML text)

Removed

• Old common typography.scss and prose.html, feature index.html, main.scss and processors.html files were replaced by the queso-ui versions.

To test

• Checkout this branch in data-visuals-create
• Go to another folder and generate a feature by running path/to/data-visuals-create/bin/data-visuals-create feature test-feature
• npm run data:fetch
• npm run serve
• Make sure everything looks OK on desktop and mobile locally

Default feature ArchieML text (what is fetched when you run npm run data:fetch)

[ashley-hebler]

Oh this is neat! I might also suggest bumping up to the latest version to get the new helper classes listed there

[ashley-hebler]

Fortunately, we can now get rid of the sass-mq import here (lines 16 and 17). We import it through line 2, which links back to this file

[ashley-hebler]

This is looking great and I'm so excited to see the shared styles as a default. I introduced a bug when I didn't include the unused CSS task in the parser so I went ahead and committed that fix with f0a5111 since it was my fault in the first place. We didn't notice it before because graphics used the old location for CSS (not in the /min folder.)

Feel free to ignore this, but I noticed that the grays used in the graphics are a little light. Their contrast is being flagged in some of my accessibility testing tools. Maybe a question to take up with the rest of the team though.

Thanks for doing this!