Code
How h5bp/html5-boilerplate is laid out, and where to start for common changes.
There is no import map for this report yet.
Where to start reading
- Repository root
- Repository root
- Likely start-up file
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
Find files for a task
AIAdd a new page or template variant
- If page needs custom JavaScript, create or extend src/js/ modules and import in src/js/app.js.
- Update build references in gulpfile.mjs if new static assets or special processing is needed.
- Run 'npm run build' to generate dist/ output and verify test/file_existence.mjs passes.
Customize CSS and styling
- Review current CSS architecture and responsive design patterns in docs/css.md.
- Extend or replace CSS by modifying source files referenced in webpack.common.js.
- Run 'npm run build' to compile changes into dist/css/style.css.
Add JavaScript functionality or vendor library
- Import and use new libraries in src/js/app.js following CommonJS or ES6 module syntax.
- Webpack config in src/webpack.common.js will automatically bundle dependencies.
- Run 'npm run lint' to validate code style, then 'npm run build' to bundle.
Enforce code style across the team
- Review linting rules in eslint.config.mjs and formatting rules in .prettierrc.json.
- Run 'npm run lint' to identify violations and 'npm run prettier' to auto-fix formatting.
- CI workflows in .github/workflows/test.yml enforce lint checks on every pull request.
Trace runtime behavior
Add or update tests
Change build or automation
RepoPilot lists up to 500 files, so a file missing here may still exist.
- Files marked “likely” are guessed from their names.