This is a Next.js project bootstrapped with create-next-app.
This project uses Husky to enforce code quality standards before commits:
- pre-commit: Runs on staged files before each commit
- ESLint with auto-fix for code style and quality
- TypeScript type checking
- commit-msg: Validates commit messages follow Conventional Commits format
- Required for semantic versioning and automated releases
Commit messages must follow the Conventional Commits specification:
<type>: <description>
[optional body]
[optional footer]
Common types:
feat: A new featurefix: A bug fixdocs: Documentation changesstyle: Code style changes (formatting, missing semi-colons, etc.)refactor: Code refactoringtest: Adding or updating testschore: Maintenance tasks
Example:
git commit -m "feat: add user authentication"
git commit -m "fix: resolve navigation bug in mobile view"This project includes automated PR checks that run on every pull request:
- Tests: Runs all tests with coverage reporting via Codecov
- Accessibility Tests: Automated accessibility testing with axe-core (see docs/ACCESSIBILITY_TESTING.md)
- Linting: Ensures code follows ESLint rules (including accessibility rules)
- Type Checking: Validates TypeScript types with
tsc - Build: Verifies the application builds successfully
- Performance: Runs Unlighthouse performance checks on configured paths
This project includes comprehensive accessibility testing to ensure inclusive user experiences. We use:
- axe-core for automated a11y testing
- jest-axe for Vitest integration
- Storybook a11y addon for visual accessibility checks
- eslint-plugin-jsx-a11y for static code analysis
For detailed information, see docs/ACCESSIBILITY_TESTING.md.
Performance tests are configured via unlighthouse.config.js. To add more paths for performance testing:
- Edit
unlighthouse.config.js - Add paths to the
urlsarray - Adjust performance budgets in the
ci.budgetsection if needed
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun devOpen http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.