Friday Before Build Week
- All Team members
- Work together to fill out their relevant pieces of the Technical Design Document (TDD) - https://docs.google.com/document/d/1PRuUblVfB9gsop6rZ4gl-piXrkPA5qsSKkP9Rg0Duh0/edit?usp=sharing
- Your Team Lead will copy the document above and give you all access to contribute to it.
- Please find time to do this before Monday morning and get a link to this TDD into your main Github Organization Readme.
Monday - Milestones
- Morning Block
- Continue on-boarding the team and ensuring that features are made available and shown to the team.
- Finish up TDD.
- User Interface Developer
- Marketing landing page scaffolded with common layout structure implemented,
- Mobile screen width features starting to come into play.
- Lorem ipsum can be used to fill in your content on your pages. Links listed below.
- All Projects
- All Project's file structures scaffolded and project architecture decided.
- Each project is deployed to Netlify or Heroku by end of day.
Tuesday - Milestones
- User Interface Developer
- ****Marketing site including all pages fully responsive to Mobile and Desktop screen widths.
- All pages laid out all that's left for each page are styling tweaks.
- ****Marketing "Login" call to action links user to the Deployed React app login screen.
Wednesday - Milestones
- User Interface Developer
- Marketing site replace placeholder copy with description of product. Be creative here. Really try and describe your project, your project's features and of course have a cool "About Us" page with relevant copy that describes your team members and their roles.
- All marketing site pages fully responsive and built out, may still need to polish up styling and layout.
Thursday - Milestones
- All Team Members -
- Strong emphasis on bug fixes and UI/UX.
- Web - If your Front end needs help, mob program. All web members in the group could be able to contribute to finalizing the styles.
- All Team Members - Document your projects within the Readme files in their Github repositories. Without having to talk to you specifically, any developer should be able to install, contribute to, and run your project based on the descriptions found in your readme.
Friday - FEATURE FREEZE 🥶 + Demo Day
- Morning Time before Lunch is all dedicated to polish and Demo Day prep.
- There will be a sign up sheet delivered to sign up to demo in the hour long school-wide demo.
- There will be a school wide demo held on Friday for 1 hour during the morning.
- Students will volunteer their projects to be demoed to their PMs.
- Only 10 Projects will be demoed across the entire student body.
- Group wide demos will take place in your PM groups - PMs will use the project rubric to assign a score.
- Sprint Retrospective to happen before students break for the week.
You have learned all about the foundations of the Web over the past eight weeks. Now you will build a static landing page that links to a your group's application.
- User Interfaces 1 - 3
- Git for Web Development
- Responsive Design 1 - 2
- Pre-Processors 1 - 2
- JavaScript Fundamentals 1 - 4
- DOM 1 - 2
- Components 1 - 2
For your project this week, you will demonstrate proficiency by working with a group of students cross section to deliver a minimum viable product (MVP) over the course of the week.
- You will build a multi-page marketing website that matches the theme chosen by your group and provides the user with details about the product your team has selected to build.
- Your marketing website must include responsive mobile and desktop screen widths. Please see the "Responsiveness" portion of your rubric for more information on this.
- The call to action on the website should be a login button that links the user over to the React application that your Front End Architect is building.
- Your marketing website must be hosted on a hosting platform like "Netlify" or "Github Pages".
- For this Marketing site's home page you need to have content and copy that relates to the product that your team is workinfg on.
- Descriptions about the product and about the features it provides would be key.
- For a second page, you could do an about us section that includes images of the members of your team, and links to one another's socials/Github.
| Objective | 1 | 2 | 3 | Score | Total |
|---|---|---|---|---|---|
| MVP work - Project should incorporate all of the listed MVP features | Student did not achieve all of the MVP features of the project. | Student's work demonstrates that all MVP features were built | Student's work demonstrates that all MVP features were built and the student went above and beyond the project. | ||
| Team contribution | Participated by contributing but didn't communicate changes or updates. | Communicated changes to team, performed proper git merges and pull requests to get code to the codebase. | Pair programmed with the Front End Architect | ||
| HTML/CSS | Student did not match the layout design, there are visible user interface inconsistencies across the project. | Student layed out the design that matches the example well. CSS fundamentals such as: box model, flexbox, and positioning were used appropriately. | Student's code is clean and organized, proper indentation is apparent, a library or framework was researched and used. | ||
| Responsiveness | Site is not very responsive, horizontal scroll bars are vizible throughout the app, desktop view does not respond to a mobile view of 500px or below | Phone views look professional at 500px and below and Desktop views look professional at 1000px and above. No horizontal scrollbars exist. | Tablet views look professional at 800px and above. Responsive units are used for font-sizing. | ||
| JavaScript Fundamentals | There is JavaScript in the page but there are errors in the console when running the page. Code is there but not readable. | Objects were created, Array methods were used, code is readable. No errors in the console when opening the web page. | Any of the following were used: .map(), .reduce(), .filter(), .sort(), constructors were used to build new objedects | ||
| Applied JavaScript | 1 or two event listeners were used and or little to no DOM manipulation occured | Event Listeners were used, DOM manipulation occured | A reusable component was built. The component should be able to take any number of elements and continue to work well. Example: Accordion with any amount of panels. |