Also:
- add MuiTab use case to bootstrap.modal
- add MuiTab stylesheet for portal
- remove outdated icon trump files
- add base stylesheets for clients to load

Client should always load base.css first.

| stylesheet      | root¹ | cms² | portal³ | header ⁴ |
| -               |   -   |  -   |    -    |    -     |
| base.css        |   ✓   |  —   |    —    |    —     |
| base.cms.css    |   —   |  ✓   |    —    |    —     |
| base.portal.css |   —   |  —   |    ✓    |    —     |
| base.header.css |   —   |  —   |    —    |    ✓     |

There may be a base.docs.css after TUP-264.

¹ everything except cms, portal, and header
² e.g. cms
³ e.g. cepv2, tup-ui
⁴ e.g. cms, cepv2, frontera-tech-docs

| stylesheet | root¹ | cms² | portal³ | header ⁴ |
| - | - | - | - | - |
| core-styles.base.css | ✓ | — | — | — |
| core-styles.cms.css | — | ✓ | — | — |
| core-styles.portal.css | — | — | ✓ | — |
| core-styles.header.css | — | — | — | ✓ |

There may be a core-styles.docs.css after TUP-264.

¹ everything except cms, portal, and header
² e.g. cms
³ e.g. cepv2, tup-ui
⁴ e.g. cms, cepv2, frontera-tech-docs

With layers, core-styles.header.css must overwrite core-styles.cms.css.

Sans layers, site.header.css relied on bootstrap to override site.css.

Avoid dupllicate custom property (a.k.a. variable) definitions in:
- `.core-styles.cms.css`
- `.core-styles.header.css`

- some changes may be for main branch
- some changes may be for task/base-cms-portal-header branch

1. testing pattern for Core-CMS djangco.cms.forms
2. new c-form component & pattern needs template
3. just begining form.cms pattern
4. update s-affixed-input-… accordingly (for: 2, 3)
4. initial change of partials to use core-styles.*.css

- some changes may be for main branch
- some changes may be for task/base-cms-portal-header branch

1. testing pattern for Core-CMS djangco.cms.forms
2. new c-form component & pattern needs template
3. just begining form.cms pattern
4. update s-affixed-input-… accordingly (for: 2, 3)
4. initial change of partials to use core-styles.*.css

This is for CMS, but was being tested here. it works now.

Latest real bug was misssing the .html extension inthe demo.

This pattern was just committed in TACC/Core-CMS:
- task/get-core-styles-beyond-0.11.0
- d13ca50

I am porting the polishes and fixes here just so that when I delete I am deleting at the time at which CMS resumes control of it.

- build
- removed import of settings by src/_imports files
- added `core-styles.settings.css`
- changed demo to always load `core-styles.settings.css` up front

BREAKING CHANGE: Clients must include `settings.css` OR `base.css` e.g.
- @import url('@tacc/core-styles/dist/core-styles.settings.css')
- @import url('@tacc/core-styles/dist/core-styles.base.css')

Loading manually meant clients were forced to build off of it. But clients may include core-styles.base along with other files and want to configure that to load. Without this change, and with a client doing that, the client receives duplicate (hard to track down) css.

This allowed npx serve and npm start to both load the file.

All clients must change font path replacement assumption:
- before, dist had ../fonts
- after, dist has ./fonts

- build dist
- changed c-form.hbs to use c-form markup
- changed django-cms-forms to not load bootstrap
- changed django-cms-forms to load component
- removed extra stuff from django-cms-forms.hbs
- fixed selector `:not` syntax in c-forms.css
- fixed message font-weight in django-cms-form-hacks.css
- removed outdated docs comment from django-cms-forms.css
- fixed URL copy-pasta in elements/form.cms
- added html-elements.css (for base)
- changed ….base.css to load html-elements.css

Without this, modules jsut don't work. Better to use modules than not.

Allow form aptterns to have buttons that
- toggle whether form errors are shown
- toggle whether fields are required

Add sample form errors.

Select error lists by query, not class.

So we can get `.field-errors` and `.form-errors`.

Notice: The c-message is not documented yet.

Multi-checkbox field cannot be required without Javascript. Also, Django CMS Forms does not require these.