Developer guidelines

• We have three main branches on the code-gov-front-end repository that are never deleted:
  • master contains changes being prepped for a release, is always deployable
  • federalist-prod always points to the latest release
  • federalist-stag used for testing and review of new features

When introducing a change (feature, bug fix, etc.) to any @code.gov/* repository:

1. Branch off master:

        git pull origin master
        git checkout -b feature-foo origin/master
   

2. Name your branch pretty much anything except master, federalist-, or with the release- or hotfix- prefix. Suggested prefixes include refactor-, feature-, docs-, issue#, and patch-.

3. File your pull request to merge into the master branch.

The following standards and guidelines are used to guide development on this project. They are a great resource for insight into the 'why' and 'what' of many of the choices we make in development. Some, such as the Accessibility Standards, are requirements that must be met in order for code to be releasable.

• API Standards
• CSS Standards
• JavaScript Style Guide
• React Style Guide
• Code.gov Style Guide *Required
• Accessibility Standards: Meet all WCAG 2.0 AA accessibility guidelines and conforms to the standards of Section 508 of the Rehabilitation Act. *Required
• Accessibility Guide
• Design Principles
• Browser Support: We will officially support any browser above 2% usage as observed by analytics.usa.gov.
• Automated Testing Playbook
• Workflow Best Practices
• Security Best Practices
• Continuous Integration