Initial commit

.browserslistrc

@@ -0,0 +1,4 @@
+# Supported browsers
+> 2%
+last 2 versions
+not dead

.circleci/config.yml

@@ -0,0 +1,102 @@
+version: 2.1
+
+orbs:
+  snyk: snyk/[email protected]
+
+references:
+  container: &container
+    docker:
+      - image: cimg/node:20.9.0-browsers
+        environment:
+          CHROME_PATH: $(which google-chrome-stable)
+
+  restore_deps: &restore_deps
+    restore_cache:
+      keys:
+        - v2-uswds-dependencies-{{ checksum "package-lock.json" }}
+
+jobs:
+  build:
+    <<: *container
+    steps:
+      - checkout
+      - restore_cache:
+          keys:
+            - v2-uswds-dependencies-{{ checksum "package-lock.json" }}
+      - run: npm install
+      - run: npx playwright install
+      - save_cache:
+          paths:
+            - node_modules
+          key: v2-uswds-dependencies-{{ checksum "package-lock.json" }}
+      - snyk/scan:
+          organization: uswds
+      - run:
+          name: Run test
+          command: npm run test:ci
+      - run:
+          name: Check formatting
+          command: npm run prettier:check
+
+  deploy:
+    <<: *container
+    steps:
+      - checkout
+      - restore_cache:
+          keys:
+            - v2-uswds-dependencies-{{ checksum "package-lock.json" }}
+      - run: npm install --ignore-scripts
+      - run: npm rebuild node-sass
+      - run:
+          name: Build the USWDS package
+          command: npm run build
+      - run:
+          name: Publish to NPM
+          command: |
+            npm config set "//registry.npmjs.org/:_authToken=$NPM_TOKEN"
+            npm publish --access public
+  deploy-alpha:
+    <<: *container
+    steps:
+      - checkout
+      - run: npm install --ignore-scripts
+      - run: npm rebuild node-sass
+      - run:
+          name: Build the USWDS package
+          command: npm run build
+      - run:
+          name: Publish to NPM with `alpha` tag
+          command: |
+            npm config set "//registry.npmjs.org/:_authToken=$NPM_TOKEN"
+            npm publish --access public --tag alpha
+  deploy-beta:
+    <<: *container
+    steps:
+      - checkout
+      - run: npm install --ignore-scripts
+      - run: npm rebuild node-sass
+      - run:
+          name: Build the USWDS package
+          command: npm run build
+      - run:
+          name: Publish to NPM with `beta` tag
+          command: |
+            npm config set "//registry.npmjs.org/:_authToken=$NPM_TOKEN"
+            npm publish --access public --tag beta
+workflows:
+  version: 2
+  circle-uswds:
+    jobs:
+      - build
+      - deploy:
+          requires:
+            - build
+          filters:
+            branches:
+              only: main
+      - deploy-beta:
+          requires:
+            - build
+          filters:
+            branches:
+              only: library--main

.codeclimate.yml

@@ -0,0 +1,12 @@
+version: "2"
+plugins:
+  duplication:
+    enabled: true
+    config:
+      languages:
+        - javascript
+exclude_patterns:
+  - config/**/*.js
+  - dist/**/*.js
+  - src/**/*.spec.js
+  - src/js/vendor/**/*.js

.editorconfig

@@ -0,0 +1,17 @@
+# IDE settings for the Midas project. Many IDE's support this as a starting point
+# for a project. For more info, see http://EditorConfig.org.
+
+# top-most EditorConfig file
+root = true
+
+# Unix-style newlines with a newline ending every file
+[*]
+end_of_line = lf
+insert_final_newline = true
+charset = utf-8
+indent_style = space
+indent_size = 2
+
+[{*.md}]
+indent_style = space
+indent_size = 4

.eslintignore

@@ -0,0 +1 @@
+src/styleguide/

.eslintrc.yml

@@ -0,0 +1,24 @@
+extends:
+  - airbnb-base
+  - prettier
+plugins:
+  - import
+  - no-unsanitized
+env:
+  node: true
+  browser: true
+  es6: true
+  mocha: true
+rules:
+  import/no-extraneous-dependencies:
+    - error
+    - devDependencies: true
+  no-unsanitized/method: error
+  no-unsanitized/property: error
+overrides:
+  - { files: ['*.spec.js'],
+      rules: {
+        no-unsanitized/method: off,
+        no-unsanitized/property: off
+        }
+      }

.gitattributes

@@ -0,0 +1,2 @@
+# Auto detect text files and perform LF normalization
+* text=auto

.github/CODEOWNERS

@@ -0,0 +1,67 @@
+*       @uswds/admins
+
+# This is a comment.
+# Each line is a file pattern followed by one or more owners.
+
+# These owners will be the default owners for everything in
+# the repo. Unless a later match takes precedence,
+# @global-owner1 and @global-owner2 will be requested for
+# review when someone opens a pull request.
+# *       @global-owner1 @global-owner2
+
+# Order is important; the last matching pattern takes the most
+# precedence. When someone opens a pull request that only
+# modifies JS files, only @js-owner and not the global
+# owner(s) will be requested for a review.
+# *.js    @js-owner #This is an inline comment.
+
+# You can also use email addresses if you prefer. They'll be
+# used to look up users just like we do for commit author
+# emails.
+# *.go [email protected]
+
+# Teams can be specified as code owners as well. Teams should
+# be identified in the format @org/team-name. Teams must have
+# explicit write access to the repository. In this example,
+# the octocats team in the octo-org organization owns all .txt files.
+# *.txt @octo-org/octocats
+
+# In this example, @doctocat owns any files in the build/logs
+# directory at the root of the repository and any of its
+# subdirectories.
+# /build/logs/ @doctocat
+
+# The `docs/*` pattern will match files like
+# `docs/getting-started.md` but not further nested files like
+# `docs/build-app/troubleshooting.md`.
+# docs/*  [email protected]
+
+# In this example, @octocat owns any file in an apps directory
+# anywhere in your repository.
+# apps/ @octocat
+
+# In this example, @doctocat owns any file in the `/docs`
+# directory in the root of your repository and any of its
+# subdirectories.
+# /docs/ @doctocat
+
+# In this example, any change inside the `/scripts` directory
+# will require approval from @doctocat or @octocat.
+# /scripts/ @doctocat @octocat
+
+# In this example, @octocat owns any file in a `/logs` directory such as
+# `/build/logs`, `/scripts/logs`, and `/deeply/nested/logs`. Any changes
+# in a `/logs` directory will require approval from @octocat.
+# **/logs @octocat
+
+# In this example, @octocat owns any file in the `/apps`
+# directory in the root of your repository except for the `/apps/github`
+# subdirectory, as its owners are left empty.
+# /apps/ @octocat
+# /apps/github
+
+# In this example, @octocat owns any file in the `/apps`
+# directory in the root of your repository except for the `/apps/github`
+# subdirectory, as this subdirectory has its own owner @doctocat
+# /apps/ @octocat
+# /apps/github @doctocat

.github/DISCUSSION_TEMPLATE/component-proposals.yml

@@ -0,0 +1,98 @@
+title: "Component proposal: [Component name]"
+labels: ["Type: New component proposal"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for suggesting a new component for the U.S. Web Design System (USWDS).
+        
+        To get the discussion started, you just need to fill out the three fields marked with an asterisk (*). Then collaborate with the community to add supporting evidence and research, and get feedback. The work you do now can help the USWDS team create a formal component proposal.
+        
+        [Learn more about the component proposal process](https://github.com/uswds/uswds/discussions/5764).
+        
+        ## The basics
+  - type: textarea
+    id: name
+    attributes:
+      label: Component name
+      description: |
+        Share the common name (or names) for this component.
+      value:
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: 'Component description'
+      description: |
+        Briefly tell us the purpose of this component.
+      value:
+    validations:
+      required: true
+  - type: textarea
+    id: need
+    attributes:
+      label: 'Why USWDS needs this component'
+      description: |
+        Include key interactions, current gaps in USWDS, and the problems this component solves. Explain how the component supports federal laws, guidance, or policies.
+      value:
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: |
+        ## Component details
+  - type: textarea
+    id: design
+    attributes:
+      label: 'How the component works'
+      description: |
+        Describe how the component works. Include any interactive states and variants. Diagrams, images, wireframes, and prototypes can help you make your case.
+      value:
+    validations:
+      required: false
+  - type: textarea
+    id: implementation
+    attributes:
+      label: 'Real-world examples'
+      description: |
+        Link to examples of other sites — preferably government sites — that use this kind of component.
+      value:
+    validations:
+      required: false
+  - type: textarea
+    id: when_to_use
+    attributes:
+      label: When to use this component and when to consider something else
+      description: |
+        What kind of content works best with this component, and what kind of content would work poorly with it? What are common misuses of this type of component?
+      value:
+    validations:
+      required: false
+  - type: textarea
+    id: usability
+    attributes:
+      label: Usability considerations
+      description: |
+        Include conditions that would make this component more usable or less usable. Also include common pitfalls or implementation mistakes associated with this component.
+      value:
+    validations:
+      required: false
+  - type: textarea
+    id: accessibility
+    attributes:
+      label: Accessibility considerations
+      description: |
+        Include how this component interacts with assistive technologies such as keyboard navigation, screen readers, zoom magnification, and voice command. Are there audiences that might struggle with this component? How might the component become inaccessible?
+      value:
+    validations:
+      required: false
+  - type: textarea
+    id: involved
+    attributes:
+      label: Who’s involved
+      description: |
+        Please tag volunteers who may be willing to help design, develop or test this component. Note agencies that can offer significant support for the component, and tag any stakeholders. Be sure to share a list of those who helped research and prepare this proposal. Include your name and/or GitHub username if you’d like credit as a contributor.
+      value:
+    validations:
+      required: false

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,29 @@
+<!-- Please feel free to remove whatever sections/lines in this aren’t relevant.
+
+Use the title line as the title of your pull request, then delete these lines.
+
+## Title line template: [Title]: Brief description
+
+Website: For issues that impact designsystem.digital.gov’s look, feel, or functionality, please open an issue on the uswds-site repo (https://github.com/uswds/uswds-site/issues/new).
+
+-->
+
+## Description
+
+Include a high-level description of the issue. What did you expect to happen? What happened instead? What would you like to see changed?
+
+Include any benefits, challenges, or considerations. This can be short and sweet.
+
+## Steps to reproduce the issue
+
+1. Step one
+2. Step two
+3. Step three
+4. etc.
+
+## Additional information [optional]
+
+* Relevant research and support documents
+* Screen shot images
+* Notes
+* And so on