Remove slide deck reference from design.login.gov.

Remove "Coming soon!" pages from the design system.

* Toggle hidden content visible for visual regression tests

**Why**: Check for regressions of content which may be collapsed (hidden) by default.

* Apply lint fixes

Remove accessibility statement from design.login.gov in favor of it being on login.gov

**Why**: So that accessibility redirect introduced in #178 does redirect.

**Why**: The layouts are overly prescriptive, may fall (or have fallen) out of alignment with current recommendations, and are not the most useful of resources for referencing appearance or markup of page sections (footer, navigation, etc).

This removal should be complemented by future work to either:
- Reference base components from USWDS for additional guidance
- Document and list differences between USWDS footer / navigation and the login.gov Design System

* Remove Spinner component button variant

**Why**: This is out of sync with current guidance, where buttons which trigger a waiting experience have since been refined within the IdP to display with a pulsing dot animation.

See: LG-3730, LG-3787, 18F/identity-idp#4517

* Merge 3.0.1 into unreleased changelog

A 3.0.1 hasn't yet been published

**Why**: As someone using the login.gov Design System, I want to know when a component is implemented as an extension of the U.S. Web Design System, so that I can reference guidance from the USWDS documentation, and see specific implementation differences contained in the component stylesheet.

* Remove accessibility policies page

**Why**: As of #178, this page is no longer referenced.

* Exclude external redirect pages from sitemap

**Why**: Since removal, not intended to be content of the site to be indexed.

Reference: https://twitter.com/JohnMu/status/1031867308434759680

* Keep sitemap entry for redirected accessibility page

**Why**: Maybe it is useful, so that Googlebot can find the new canonical resource?

See: https://twitter.com/maxjpeters/status/1034288751030104064

* Add Images page with as adaptation of accessibility policies

* Update decorative text hidden guidance

See: #181 (comment)

* Move Illustration brand guidance principles to Images page

* Add introduction content to the images page.

* Remove unused illustration from images page.

* Remove outdated link to Illustration subsection

Moved to Images page in c722baa

* Remove unused id-confirm.svg image

Removed in 0ff6281

* Remove unused "Decorative Illustration" screenshot

Replaced with illustration graphics in c722baa

* Update header content for accessibility.

Co-authored-by: Julia Elman <julia.elman@gsa.gov>

**Why**: It's expected that the intention of these selectors was to match headings within `.usa-prose` following any other content in that prose block. Instead, due to the behavior of `&` in expanding the full selector ancestry, the generated output was along the lines of...

```
*+.usa-prose>h2,*+.usa-prose>h3 {
    margin-top: 1.7em
}
```

This can be interpreted as "any content, followed by a prose block with a heading".

**Why**: So that we're publishing a consistent set of favicon icons, all of which use the Login.gov logo shield.

**Why**: So that projects importing subpaths from identity-style-guide don't fail if they respect native ES module `exports` definitions.

See: https://nodejs.org/api/packages.html#packages_package_entry_points
Co-Authored-By: Jessica Dembe <17969963+jmdembe@users.noreply.github.com>

Co-authored-by: Jessica Dembe <17969963+jmdembe@users.noreply.github.com>

Co-Authored-By: Jessica Dembe <17969963+jmdembe@users.noreply.github.com>

Co-authored-by: Jessica Dembe <17969963+jmdembe@users.noreply.github.com>

This pull request seeks to resolve an issue where focused buttons appear with two focus rings. The button styles included in the design system intend to unset the inherited focus styles from USWDS, but are not of high enough specificity to override the styles.

Reference: https://github.com/uswds/uswds/blob/1f9bb1cc/src/stylesheets/global/_focus.scss#L1-L11

* Improve README guidance for release process

**Why**:

- Changelog should be edited to replace "Unreleased" with the release version.
- Main branch is protected, so you cannot commit the version bump directly. Improve text to include steps for creating a branch, opening a pull request, and merging before creating a new release.
- Dry-run testing is all well and good, but there wasn't any guidance around what exactly one should be looking for in considering whether "everything looks alright".

* Add prerequisites text describing permissions process

* Advise main branch pull to ensure latest changes are included

* LG-4226: Remove deprecated button variants

This is the first of a couple pull requests toward LG-4226, and includes only removal of button variants no longer supported in the design system.

These include:
  - Success (`usa-button--success`)
  - Dropdown (`usa-button--dropdown`)
  - Small (`usa-button--small`)
  - Tiny (`usa-button--tiny`)

See LG-4226 for more detail.

* Remove references to Other Buttons

See: https://github.com/18F/identity-style-guide/pull/191/files#r582962658

* LG-4226: Improve support for unstyled button

The unstyled button variant had previously existed in that it was inherited from USWDS, though it was not documented, and did not always display correctly, particularly in hover, active, and focus states. These changes improve this support, and adds documentation for the unstyled option.

* Fix button heading hierarchy

Don't skip heading levels

https://dequeuniversity.com/rules/axe/3.5/heading-order

* Improve unstyled button preview partial

- Use utility classes
- Improve mobile display

* Add wide button variants

Adds two new button variants:

1. Minimum width occupies full width on mobile, and a minimum width on wider viewports
2. Full width always occupies full width

* Remove redundant mobile width style

**Why**: Already full-width at small viewports

* Switch wide buttons to min-width at mobile-lg

**Why**: Match USWDS cut-over.

See:

- https://github.com/uswds/uswds/blob/1f9bb1c/src/stylesheets/elements/_buttons.scss#L24-L26
- #192 (comment)

* Update documented text to match Figma

* Rename "Secondary" as "Outline" in buttons documentation

* Document big buttons

* Rescale buttons per Figma

* Increase border radius to 0.5rem for big buttons

Per design

See: #193 (review)

* Match button hover, active text color to border

Inherit most styles from USWDS

**Why**: As a consumer of the login.gov Design System, I expect to be able to override the default full-width button appearance on mobile to allow for flexible-width buttons, so that I can create interfaces where the button is shown adjacent to other text or controls.

Currently, all buttons are shown as full-width at mobile viewports. There are a few instances in the IDP of buttons appearing as "flexible width", with text or interactive content shown next to the button. These are not the majority, so an override option is included to let the developer choose to force the width to shrink as flexible, while retaining the current default behavior.

In discussing this with @anniehirshman-gsa , it was considered whether a similar exception override class should be included for minimum-width buttons (e.g. `usa-button--minimum-width`). There are currently no use-cases for this, so it was decided to defer this for future consideration if ever it becomes relevant.

* Remove password strength meter component

* Remove zxcvbn dependency

Unused after removal of password strength component

Bumps [elliptic](https://github.com/indutny/elliptic) from 6.5.3 to 6.5.4.
- [Release notes](https://github.com/indutny/elliptic/releases)
- [Commits](indutny/elliptic@v6.5.3...v6.5.4)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* 5.0.0

* Bump CHANGELOG version to published version

* Remove re-application of unstyled button styles

**Why**: It should not be necessary, because USWDS handles hover and active unstyled states, but does not currently do so for the modifier classes. Previously, we worked around this by including the unstyled button mixin, which would have a higher specificity than the default button's hover styles. Unfortunately, this also comes with some unexpected consequences, such as the re-application of the USWDS focus ring, which we expect to override in our own default button styles.

* Add changelog entry

* 5.0.1

* Re-include (unprefixed) unstyled button styles to reset big, base overrides

**Why**: We customize big button padding and border radius, which should not extend to apply to the unstyled button. This is controlled in USWDS by applying unstyled styles last. We must similarly reapply unstyled button styles after our customizations. Unlike prior to afecbdd, don't give extra specificity and instead rely on style order, similar to as in base USWDS styles.

…ance (#201)

* Buttons: Use "inherit" for font smoothing reset

See: uswds/uswds#4115

* Buttons: Remove underline offset from unstyled buttons

**Why**: So that unstyled buttons appear visually identical to links

* 5.0.2

**Why**: These were applied to modifier states for unstyled buttons in #201, but should have also been applied to the base styles, to override USWDS unstyled button styles.

* Reduce border width on normal outline button

**Why**: Per Figma design reference, the outline button should only have a border width of 1px, not 2px. The "Big" outline button should still have a 2px border.

* Revert CHANGELOG entry to "Unreleased"

See: https://github.com/18F/identity-style-guide/pull/205/files#r603407014

Bumps [kramdown](https://github.com/gettalong/kramdown) from 2.3.0 to 2.3.1.
- [Release notes](https://github.com/gettalong/kramdown/releases)
- [Changelog](https://github.com/gettalong/kramdown/blob/master/doc/news.page)
- [Commits](https://github.com/gettalong/kramdown/commits)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

…earch bar

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

Add custom components to LGDS

**Why**: Resolve outstanding dependabot alerts

* Remove bundler install tasks from NPM prepare script

**Why**: Required for interoperability with Federalist pending upcoming platform changes.

* Remove npm install from Federalist script

**Why**: Previously needed because Federalist would only install dependencies, and we rely on devDependencies for the site build. This is changing in an upcoming Federalist release where all dependencies will be installed.

* Fix search input square corners

**Why**: Search input corners are intended to be squared in USWDS, but it is being overridden unintentionally by our `.usa-input` border radius customizations.

See: 18F/identity-dashboard#420 (comment)

* Remove right border from input

Original: https://github.com/uswds/uswds/blob/0f1f4d0a12bb3981a52cc882c78b79931e6b004c/src/stylesheets/components/_search.scss#L83
Customized: https://github.com/18F/identity-style-guide/blob/ba2b1f7863a59a1fcbd47b713cfb7a4455813ab2/src/scss/components/_inputs.scss#L7

* Load utility classes after components

**Why**: To match USWDS intended load order of stylesheets, to allow utility classes to take precedent over component styles, and to facilitate a potential future use of USWDS 2.11.0 package subsetting.

* Use symlink to point to uswds dependency for src files

**Why**: Avoid changing file structure for built output, while retaining the ability to point to dependency source in development in a way that's compatible with the copied dependency in the build distributable. Also, nicer paths.

* Ignore USWDS files for lint

* Run copy-scss tasks in series

**Why**: Guarantee USWDS always takes precedent over symlink

* Add package entrypoints for granular stylesheet loading

**Why**: To limit or control the loading of styles.

Use-cases:

1. Avoid specificity conflicts between utility classes and a consuming project's custom components
2. Load only required mixins and functions to support CSS code splitting

This also mirrors USWDS packages, with two main differences:

- Simplifies naming of `uswds-components` and `uswds-utilities` to just `components` and `utilities`
- Extracts `utilities-required` from `utilities` to allow non-rendering import of utility mixins.

See:

- https://designsystem.digital.gov/components/packages/
- https://github.com/uswds/uswds/blob/develop/src/stylesheets/uswds.scss

* Absorb utilities-required into required

**Why**: Simpler

**Why**:

- Account for missing `usa-button--unstyled:hover` and `usa-button--unstyled:active`
- Single point to remove in the future, as noted in the preceding comment

* Add changelog for side navigation component

* Bump version to 5.1.0

* Bump vulnerable y18n dependency

**Why**: Reduce audit reported issues

Bumps [rexml](https://github.com/ruby/rexml) from 3.2.4 to 3.2.5.
- [Release notes](https://github.com/ruby/rexml/releases)
- [Changelog](https://github.com/ruby/rexml/blob/master/NEWS.md)
- [Commits](ruby/rexml@v3.2.4...v3.2.5)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [lodash](https://github.com/lodash/lodash) from 4.17.20 to 4.17.21.
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](lodash/lodash@4.17.20...4.17.21)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [hosted-git-info](https://github.com/npm/hosted-git-info) from 2.6.0 to 2.8.9.
- [Release notes](https://github.com/npm/hosted-git-info/releases)
- [Changelog](https://github.com/npm/hosted-git-info/blob/v2.8.9/CHANGELOG.md)
- [Commits](npm/hosted-git-info@v2.6.0...v2.8.9)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [postcss](https://github.com/postcss/postcss) from 8.1.2 to 8.2.10.
- [Release notes](https://github.com/postcss/postcss/releases)
- [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md)
- [Commits](postcss/postcss@8.1.2...8.2.10)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

**Why**:

- Fix Federalist builds, which no longer support Node 10
- Avoid pinning to a specific version to reduce future maintenance overhead
- Use a version of Node which hasn't fallen outside the maintenance calendar, to avoid missing critical bug fixes or encountering other conflicts

See: https://nodejs.org/en/about/releases/

Bumps [browserslist](https://github.com/browserslist/browserslist) from 4.3.6 to 4.16.6.
- [Release notes](https://github.com/browserslist/browserslist/releases)
- [Changelog](https://github.com/browserslist/browserslist/blob/main/CHANGELOG.md)
- [Commits](browserslist/browserslist@4.3.6...4.16.6)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

**Why**: So that the build doesn't fail by exceeding the default timeout of 5 seconds, where allowing the compilation to complete would otherwise succeed.

* Upgrade USWDS from 2.9.0 to 2.11.2

* Apply perfect circular border-radius to all radio input states

* Add unchecked focused style examples to documentation

* Add unchecked radio focus styling

* Ensure unique IDs in documentation

* Use default focus highlight effect for radio

* Restore custom alert icons to alerts directory

**Why**: Avoid breaking changes for existing consumption. These files are still provided by USWDS (presumably for backwards-compatibility), and we want to continue overriding them. We should also avoid providing inconsistent, custom icons in place of only a handful of the broader icon set, which is intended to be used verbatim or masked with a default monochrome color.

Finally, ensure viewBox is included in the images themselves to scale properly in Internet Explorer.

* Remove preserveAspectRatio

**Why**: From local testing

* Update test CSS selector

**Why**: Image is not set as background of the before pseudo-class.

See:
- uswds/uswds@1048f9f
- uswds/uswds@8439f3b

* Single quotes

* Bump all dependencies to latest

**Why**:

- Reduce number of `npm audit` issues
- Minimize future maintenance burden caused by larger version drift
- Prepare for 6.0.0 release

* Bump all dependencies to latest

* npm dedupe

* Resync package-lock.json

Bumps [ws](https://github.com/websockets/ws) from 6.2.1 to 6.2.2.
- [Release notes](https://github.com/websockets/ws/releases)
- [Commits](https://github.com/websockets/ws/commits)

---
updated-dependencies:
- dependency-name: ws
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

**Why**: The USWDS upgrade in #219 changed default padding for most navigation menus. This was corrected in the side navigation, but mobile primary navigation still appeared more condensed than previously. Additionally, default scaling for the navigation close button was changed in USWDS to be much larger due to a change to use the new icon set, causing the icon to appear very large. The design system was not using our custom version of the icon anyways. This has been corrected.

Remove outdated research section from design.login.gov

Bumps [addressable](https://github.com/sporkmonger/addressable) from 2.6.0 to 2.8.0.
- [Release notes](https://github.com/sporkmonger/addressable/releases)
- [Changelog](https://github.com/sporkmonger/addressable/blob/main/CHANGELOG.md)
- [Commits](sporkmonger/addressable@addressable-2.6.0...addressable-2.8.0)

---
updated-dependencies:
- dependency-name: addressable
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Remove custom Accordion close button element

**Why**:

Maintenance:
- Limit divergence from USWDS, facilitating ongoing maintenance and reducing potential confusion introduced by enhancements exclusive to the login.gov Design System.

Accessibility:
- The button's behavior is duplicative with the toggle, where the additional tab stop may be excessive as repeated content.
- Collapsing an accordion by the close button causes a focus loss ([SC 2.4.7](https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html), [SC 2.4.3](https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html))
- The relationship between the button and controlled content is not clearly indicated (e.g. [`aria-controls`](https://www.w3.org/TR/wai-aria-1.1/#aria-controls))

* Remove unused variable $icon-size

* Restore border radius to accordion content bottom border

* Clarify removal of JavaScript exported member

* Remove custom Accordion close button element

**Why**:

Maintenance:
- Limit divergence from USWDS, facilitating ongoing maintenance and reducing potential confusion introduced by enhancements exclusive to the login.gov Design System.

Accessibility:
- The button's behavior is duplicative with the toggle, where the additional tab stop may be excessive as repeated content.
- Collapsing an accordion by the close button causes a focus loss ([SC 2.4.7](https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html), [SC 2.4.3](https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html))
- The relationship between the button and controlled content is not clearly indicated (e.g. [`aria-controls`](https://www.w3.org/TR/wai-aria-1.1/#aria-controls))

* Remove unused variable $icon-size

* Restore border radius to accordion content bottom border

* Clarify removal of JavaScript exported member

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>

Remove "Usage" section of design.login.gov

Update capitalization guidance in content guide