junior-devleague / focus-like-crazy

WHS Focus Like Crazy Final Project

focus-like-crazy

WHS Focus Like Crazy Final Project

Project Manager: Ian Acosta
Developers: Ian Acosta, Jessica Lopez, Kelli McCrary, Kayla Diniega

Final Project Breakdown

Assignments and Grading for the 4th quarter

• 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

---

Daily Scrum

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.

---

Formatting Structure

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.

Formatting example

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’

---

Task Breakdown - Part 1

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
  • Blue: #4990E2
  • Light Gray: #4990E2
  • Medium Gray: #9B9B9B (font color)
  • Dark Gray: #4A4A4A
• Fonts
  • Logo and Buttons: Chewy
  • Headings: Lato Black
  • 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 interactive buttons for the navigation
• Create array objects of mock data for tips and store them in a variable
• Randomly display 'tips' on Pause Page

Task Breakdown - part 2

• Create Game logic
• Add CSS(or image assets) for game UI
• Add progress bar logic to game UI
• Create timer
• Add Pause screen to Game UI as an overlay
• Make Pause screen 'appear' on timer increments
• Allow user to resume from Pause screen

After review: 4/14

To do

HTML

• Move header and script into body tag
• Still need end-game screen
• Polish how to play. Add game rules, etc.
• Change welcome-screen to index.html and index.html to game.html
• Link Keep it simple button to game.html.
• On the welcome screen wrap buttons with a tags and link to games
• On pause screen change div tags into button tags instead.

CSS

• Add a font-weight of 300 to the body.
• Add Chewy font to title.
• You can add text-transform on title and buttons to uppercase.

JS

• Polish Game:
  • At the end of game show end-game screen
  • Add game UI
  • Add pause and end game logic to game UI
  • Add timer + pause logic

Awesome start! Game mechanics are looking good and the button actions are great. Keep it up.

Improvments

• Ian: Keep going the game is coming together nicely. Let's task out more js to your team mates. If you need, take a day to pair program the psuedo code and work out the logic your game needs. Just a quick outline in your js. LMK if you need help.
• Jess, Kayla, Kelii: The other pages are looking good. Just one more view needs to be made and lets polish the ones that are there. Would be great to have one of you help with the js and the game ui.