Documentation
- Run and build VA.gov locally
- Frontend workflow
- Frontend architecture
- Best practices
- Standards
- Adding applications and features
- Isolated application builds
- Frontend testing
- Automated code quality
- Tools
- GitHub Actions usage for VA.gov frontend engineers
- VA Forms Library Overview
- How to opt-in to Drupal as the source of truth for Oracle Health-related apps and widgets
- How we use GitHub code owners
- Preparing your Pull Request for Platform Review
- Best Practices for Writing Pull Requests
- Vets API PR tips
- Personal Identifiable Information (PII) guidelines
- Coding best practices for PII
- Sensitive documentation guidance
- Creating New Github Repositories in VA Github Org
- GitHub code scanning policy
- Copilot on the Platform
- Sidekiq::AttrPackage Guidelines
- Backend Architecture
- Best Practices
- Backend Standards
- Tools and Debugging
- Running Vets API Locally
- Backend Workflow
- EKS
- Vets API on EKS
- Benefits Intake API Metadata Validator
- Polling the Benefits Intake API for Form Submission Status
- Supporting Code
- ClamAV Architecture, Behavior, and Failures (vets-api)
- Vets-API Helm Charts, Environment Values, and SSM Parameters
- Phase I: Before Starting Digitization Work
- Phase II: Discovery and Planning
- Phase III: Initial Digitization
- Phase IV: Collaboration Cycle
- Phase V: External Review, Testing & Release Prep
- Phase VI: Launch and Post-Launch
- Phase VII: Monitoring & Maintenance
- Zero Silent Failures
- Related Resources for Forms Digitization
- VA Forms Library 101
- Glossary
-
VA-Owned Gems