W06 Team Project: Final Submission
Overview
This individual submission represents your team's working web application product demo. Submit your application as if you are presenting a targeted, functional, and professional product to a client.
Review the project specifications and requirements to confirm your final application still aligns with scope, audience, and core outcomes for this course.
You will include your production deployment link along with the repository link for grading convenience. You will not submit GitHub Project Board links. Your team workflow artifacts were already evaluated in team project reports.
Checklist
- Run and Access: Repository URL, deployment URL, and working access instructions are provided (including auth provider and test credentials when needed).
- Core Product Value: The app clearly communicates purpose/audience and demonstrates at least three distinct views with meaningful dynamic data.
- Feature Coverage: Required user/auth behaviors and two-model CRUD are implemented. Minimal CRUD is acceptable (for example, profile update as Update and soft delete as Delete when intended).
- Architecture Evidence: The repository shows App Router organization, database integration, and at least one client -> route handler -> database flow.
- Engineering Evidence: Reusable components, TypeScript usage, and consistent code quality/formatting are visible in the repository.
- Design and UX Quality: Design system/branding consistency, responsive behavior, accessibility awareness, and usable error/empty states are evident.
- Documentation Evidence: README is current and includes team members, setup/deploy instructions, API notes, and known issues/opportunities.
Rubric
The grader will evaluate quality against the project technical requirements and minimum functionality. Include the following evidence in your submission:
- Core Build and Delivery: A working deployed application (App Router) and the GitHub repository link using a feature-branch workflow.
- Data and Architecture: Database-backed data flow with at least one API Route Handler that is consumed by a client component.
- Feature Completeness: Minimum three views, authentication, user flows, and CRUD for at least two models (minimal CRUD interpretations allowed as defined in the checklist).
- Engineering Quality: Reusable components, TypeScript typing, consistent formatting, and overall code quality.
- Design and UX: Defined design system, cohesive branding, responsive behavior, accessibility awareness, and robust error/empty states.
- Documentation and Demo Clarity: A concise product demo summary plus project README quality (setup, deployment, API notes, known issues/opportunities).
- Lighthouse (mobile): Report scores for Performance, Accessibility, Best Practices, and SEO, and include one sentence describing your strongest and weakest category.
- CSS Overview: No color contrast errors should be found at any level (WCAG AA and AAA).
Submission
Each team member submits the following in Canvas:
- GitHub Repository URL: The team repository URL.
- Rendered Application URL: A public deployment URL for the final working application.
- Product Demo Summary: A short 2-3 paragraph walkthrough written as a client-facing demo:
- What problem your app solves.
- Who the intended users are.
- The most important user flow(s) and value provided.
- Access Instructions: If your app requires sign-in, provide demo credentials, note whether you used Auth.js v5 or Clerk, and include concise steps for the grader to test key features.
- README Verification: Confirm your repository README is up to date with project description, team members, setup/deployment instructions, API notes, and known issues/opportunities.