WHS Mint Final Project
Project Manager: Braden Amorozo
Developers: Isaiah Harris, Alex Aguinaldo, Braden Amorozo, Maddie Kawakami
- Final project: Minimum of 6 commits a week and Pull request when a task is complete
- Quizzes: Take home quiz every other week
- Research assignments: Given every other week and turned in as a medium blog or Journal entry
Teams will meet daily for the first 5-10 mins of class to report the following:
- Progress on their task. What did team members accomplish in the previous class?
- What each team member is going to work for the current class period
- Any road blocks per task or clarifications they may need from other team memebers or instructors
Project Manager reports daily to the instructors the following:
- Progress per task that the group is currently working on
- Projection as to what will be accomplished by the end of the week
- Any road blocks per task or clarifications the team may need
Developers are to notify the project manager and an instructor (in person or in Slack) when:
- A task is complete
- A pull request is made
If there are questions about a task, code questions, road blocks (challenges) please notify an instructor via Slack.
HTML, CSS, and Project Images
- File, class and id names should be all lowercase with dashes for spacing (if needed).
- Any nesting must be properly tabbed, and every element should be returned as a new line.
Javascript
- Function names and variables should be camelcase.
- Any nesting must be properly tabbed. No one liners for multiple lines of code.
- Use block comment for each a task.
- Each Javascript task should have a block comment of psuedo code.
Sublime Text
- Set spaces: 2
Git Flow
Github Commit Messages
- What was completed, any current bugs.
- Example: ‘completed top navigation in html, links do not work yet’
Creating the Views
- Follow the design views found under the Assets folder.
- If the view is not the home (first page/index.html), create a new file in the root folder with the view name.
Adding CSS
- All of the css will be in the css/styles.css
- Assign classes to reusable styles.
- Create a block comment if styles are for a specific view or user interaction, otherwise it's considered a general style.
- Colors
- Green: #99FF99
- Font Gray: #838383
- Light Gray: #EDEDED
- Dark Gray: #4A4A4A
- Red: #E77979
- Fonts
- Logo Ubuntu Medium
- Headings Raleway Semibold
- Body: Lato Regular
User Interactions
- All of the javascript will be in the js/app.js
- Start each task with a block comment and include your pseudo code.
- Create array objects of mock data per page and store them in a variable
- Dynamically display mock data per view.
- Create interactive buttons for the top navigation
- Sort - display data based on a keyword. Make the first items data show as default.
- Create image slider
- Add C3 for mock data comparison pages
- Create Sort All page
- Create a dynamic drop down menu
- Display data dynamically
- Make the voting.html into the index.html
- Create a comparison.html page (at least one)
- Need styles. =(
- Create a folder in images named dress. Add all of your dress images there
- Still need slider logic
- Link the comparison button to the comparison page
Improvments
- Braden and Issah: Lets add psuedo code to the js. Outline your tasks. Let's start knocking them out!
- Maddison and Alex: Start adding general styles. Create the comparison page, add colors and fonts.


