WDD 430: Web Full-Stack Development

W03 Team: Project

Overview

This week, your team transitions from planning to building. You will get the project running locally for every team member, practice your branching and pull request workflow, and make the key architectural decisions that will guide development for the rest of the course. By the end of this week, every team member will have a working local environment, the GitHub Project Board will be populated with prioritized issues, and the team will have agreed on component structure, data models, and visual branding — so that individual feature work can continue.

Before the Meeting

Individually complete the following before the meeting:

1. Complete the learning activities.
2. Review the project description as needed.
3. Review and refine the specifications document created last week based upon feedback received and the asynchronous check-ins with your team on Microsoft Teams.
4. If you are this week's Group Leader:
   • Send a meeting reminder to all team members at least one day before the meeting.
   • Prepare a meeting agenda based on the objectives below and the action items captured last week.

     That shared document was created last week to track discussions and decisions. If it still does not exist in your MS Teams channel, create a new one.

During the Meeting

1. Invite the Spirit: Open the group meeting with prayer and invite the Spirit into your discussion.
2. Project Specifications: Briefly review the specifications document as a team.
   • Identify any ambiguous or missing requirements
   • Discuss feasibility concerns or scope adjustments needed
   • Update your specifications document if necessary
3. Local Setup: Get every team member's environment running before any design or architecture work begins.
   • git clone [repo-url]
   • npm install
   • Verify the project runs: npm run dev and open http://localhost:3000
   • Practice the branching workflow: create a branch, make a small change, commit, push, open a pull request, have a teammate review it, and merge into main
4. Component Architecture: Design the structure of your application.
   • List the MVP pages/routes your app will have (For example, /, /login, /products, /products/[id], /seller/[id])
   • Identify the essential reusable components (Header, Footer, ProductCard, FilterBar, and so on.) and create a component hierarchy diagram
   • Decide which pages/components are highest priority for Week 04 implementation
5. Data Model: Define the core data entities and their relationships.
   • Identify 2-5 core data entities
   • Define key fields for each entity
   • Sketch relationships between entities (For example, one-to-many, many-to-many)
   • Decide on a database solution (For example, PostgreSQL, MongoDB)
6. Design Theme & Branding: Establish the visual design language for the project.
   • Choose a color palette and typography that fits the application's purpose
   • Agree on layout patterns, spacing conventions, and any shared UI library (For example, Tailwind component classes, shadcn/ui)
7. GitHub Project Board: Update and expand the project board using the decisions made today.

   Use the component architecture and data model decisions to create concrete, well-scoped issues. Break each feature into frontend and backend tasks where appropriate.

   • Add new issues based on the architecture and data model decisions (aim for at least eight total issues on the board)
   • Assign issues to team members based on interest and expertise
   • Create a Week 04 milestone and attach the highest-priority issues to it
8. Document Plan: Finalize initial feature ownership and async coordination.
   • Confirm who will build which pages and components
   • Identify dependencies (For example, shared TypeScript types must be defined before data fetching begins)
   • Agree on an asynchronous check-in cadence for the week (For example, a daily Teams message with progress and blockers)

   Looking Ahead: Your Team's AI Agent

   The decisions you made today — tech stack, component structure, data model, naming conventions, and database choice — are exactly what a GitHub Copilot custom instructions file needs to give your whole team accurate, project-aware AI suggestions throughout development. Before you close the meeting, draft an initial .github/copilot-instructions.md in your repository that captures these decisions. Your team will test, refine, and submit it as a deliverable in Week 04.

   See the GitHub Copilot custom instructions documentation for the format and what to include.

9. Group Leader: Select a new group leader for the next meeting.

Submission Instructions

Each team member submits the following sections as a text entry in Canvas:

Team Meeting Summary

This brief, written summary must include:

1. The names of the team members who were present at the synchronous meeting and the name of the team leader.
2. A summary of the major decisions made and the responsibilities assigned to each team member.

Project Setup

1. A valid URL to the team's public GitHub repository. The repository must include a README that lists all team members.
2. A screenshot of VS Code showing the cloned project running locally (npm run dev visible or the browser showing localhost:3000).
3. A valid URL to the team's GitHub Project Board. The board must contain at least 8 issues, with the highest-priority issues assigned to a Week 04 milestone.

Architecture & Design Planning

1. A data model sketch (photo, diagram, or written description) showing core entities, key fields, and relationships.
2. Evidence of design planning: color palette, typography choices, and layout or spacing conventions the team agreed on.

W03 Team: Code Review Report

This content comes from your Week 03 Team: Code Review assignment.

1. The URL of the GitHub Pull Request where you submitted your code review comments on your assigned teammate's repository.