Project Evaluation Criteria

Use this checklist with the specific requirements in each project README. Project-specific requirements are always the source of truth, and staff will use these shared criteria to evaluate the quality of the work and the development process.

Required Project Evidence

• The project meets the stated feature, technology, and submission requirements.
• The README explains what the app does, how to run it locally, how to run tests when tests are required, and includes visuals or a deployed link when requested.
• The repository only includes files needed for the project. Do not commit node_modules, .env, API keys, or unrelated work.
• The code is readable, consistently formatted, and uses clear names for files, variables, functions, and components.
• The app handles expected user flows and common error cases.
• The UI is usable on relevant screen sizes and follows accessibility expectations from the project prompt.

GitHub Collaboration Expectations

• Commit working changes frequently with clear commit messages.
• Push work to GitHub regularly so mentors and partners can review current progress.
• Create focused pull requests for review instead of pushing large batches of unrelated work.
• Participate in code review by asking questions, responding to feedback, and making follow-up commits.
• Collaborate respectfully with partners, mentors, and staff, and document decisions or setup steps that others need to know.

Staff Evaluation Areas

Staff may evaluate:

• Completion of required features and deliverables
• Correct use of the required technologies
• Code organization, readability, and formatting
• Evidence of testing or manual verification requested by the project
• Git history, pull request participation, and feedback iteration
• Documentation quality, including setup instructions and project visuals
• User experience, accessibility, and responsive behavior