Now that you’ve got the main foundations down to build out a frontend application, it’s time to prove to yourself that you own those skills! You’re going to be building a Tic Tac Toe game from scratch!
- Solidify and demonstrate your understanding of:
- localStorage to persist data
- event delegation to handle similar event listeners
- Understand the difference between the data model and how the data is displayed on the DOM
- Iterate through/filter DOM elements using for loops
- Use your problem solving process to break down large problems, solve things step by step, and trust yourself to not rely on an outside “answer” to a logical challenge
Solo Project Expectations
This project is an important step in demonstrating you are ready to start Module 2. To ensure we can accurately assess that, it’s important you meet the expectations:
- You are the only one who should type code - no copy-pasting code!
- For any code that you didn’t write entirely by yourself (mentor or rock supported), you should be able delete it and re-write it yourself
- The only resources you use are MDN, CSS Tricks, and lesson plans - no youtube videos or tutorials of programming Tic Tac Toe. If you have an opportunity and are tempted, do the right thing for YOUR learning and don’t do it!
- Any peer-to-peer collaboration should be discussions about IDEAS, not coding together or sharing code.
We want to see YOUR work.
Set Up & Submission
- Create a private repository and add your assigned instructor as a collaborator. (You cannot deploy private repositories to GitHub Pages; that’s ok.)
- Create a project board or other planning gist where you will outline your anticipated progress through functionality
- Begin wireframing your application and planning out the architecture of your HTML (in your notebook is fine)
By EOD on Kick Off Day: DM your assigned instructor with two links: Project Board/Planning Gist & Repo, and include photographs of your wireframing
Here is a video demonstrating most functionality of the game (the only functionality not explicitly depicted is data persistence using Local Storage):
In this project, we will not be providing detailed iterations. We want you to exercise your skills in planning out work!
- A timeout is used after a completed game to reset the board.
- YOU DO NOT NEED TO DISPLAY EACH INDIVIDUAL WIN BOARD. WE ONLY NEED TO SEE NUMBER OF WINS.
- No need to match colors or icons, but the overall layout should be the same.
player.jsfile that contains a
Playermethods must include, but are not limited to:
constructor- properties should include:
game.jsfile that contains a Game class.
- A way to keep track of the data for the game board
- A way to keep track of which player’s turn it currently is
- A way to check the Game’s board data for win conditions
- A way to detect when a game is a draw (no one has won)
- A way to save a winning Game’s board data to the correct player’s
- A way to reset the Game’s board to begin a new game
In a game like Tic Tac Toe, it is tempting to manipulate the DOM first. Remember that the game logic exists exclusively in the data model. The DOM simply reflects/displays that data model.
This workflow is not required, but will help you meet the overall requirements of the project.
- Plan out the HTML layout (colors and icons do not need to match, but overall layout should closely match the demo video)
- Create the Player class
- Create the Game class
- Make game fully playable without the DOM (manually updating the Game.board data, etc, from your console) to force yourself to think data-model-first
- Create central game board on the DOM
- Connect Game data model to the DOM
- Display the Player data in the sidebars
- Automatically reset the game board to allow for a new game to be played after the previous game is won
- Persist Player data using local storage (number of wins and mini-boards displaying won games should persist across page refreshes)
Rubric score key:
- 4: Over-achievement - student did self-teaching and accomplished beyond scope of project, without sacrificing code quality in the pursuit of extensions; all code demonstrates strong mastery of DRY principles and SRP conventions
- 3: Right on track - student is exactly where we want them to be, has a strong foundation, and demonstrates competency and comfort with the subject
- 2: A little behind - student needs to focus study in this area to catch up to where they should be in terms of proficiency
- 1: Very behind - student needs intervention to get back on track
Overall rubric scores will be averaged. Here is what the average score means in terms of completing the module:
- 4: - Student will complete module if prior project work, attendance, and final assessment corroborate readiness
- 3+: - Student will complete module if prior project work, attendance, and final assessment corroborate readiness
- 2+: - Student may complete module if prior project work, attendance, and final assessment corroborate readiness
- >2: - Student needs more time with concepts and work covered in module
- 4: Application is fully complete (matches all functionality from demo, without bugs), and implements additional functionality devised by the student
- 3: Application is fully complete (matches all functionality from demo, and persists across refreshes)
- 2: Able to play an entire game successfully (win, draw, displayed player data updates)
- 1: Unable to play an entire game successfully
We still expect you to use good workflow practices! Atomic commits, use of branches and PRs (you will be merging these PRs yourself).
- A PR template was used.
- A code review was requested and completed by a mentor
- developer can speak to how the feedback in code review was implemented (and point to the commit(s) that implemented the feedback).
- Developer is ready to clearly present the evolution of this app during the eval - from architecture decisions made in the planning process, to wins and challenges throughout.
- Developer is able to clearly answer questions regarding the evolution of this app during the eval - from architecture decisions made in the planning process, to wins and challenges throughout.
- A project board/planning document is used and updated throughout the project.
- Branches are used. Most commits are formatted correctly.
- The README is formatted well and contains:
- Overview of project and goals
- Overview of technologies used, your code architecture, challenges, wins, and any other reflections
- Screenshots/gifs of your app
- Developer is able to answer questions regarding the evolution of the app, but may need some prompts to clearly articulate or provide enough context.
- More than a few commits are formatted incorrectly.
- The README is formatted well but may be lacking in detail.
- Developer struggles to answer questions regarding the evolution of the app.
- OR: Commit and PR history does not tell a story of the application
- OR: A README has not been created/has minimal information.
- Code is well refactored and demonstrates developer empathy.
- No global variables are used aside from query selectors, start time, and instance of
Game. If you feel you need more because you are building out additional functionality that requires a global variable, please check in with an instructor.
- There are no instances of repetitive code
- No functions are longer than 10 lines
- The separation of data model logic and presentational logic is clear and can be explained by developer.
- The application correctly implements a data model for the
Gameclasses, including all required methods.
- Developer can speak to the role of each class.
- All DOM manipulation is handled exclusively in
- Developer demonstrates understanding and ability to refactor code by having at least 1 example of DRY code that was intentionally reused.
- SRP is evidenced by clear, concise function names; each function only does what the name describes.
- Arguments and parameters are used to limit global variables.
- The event object is used correctly, and is not accepted as a parameter if it is not necessary.
- Developer can speak to how the event object is utilized for any given event handler.
- Function and variable names describe their role in the program.
- Examples: The name of the data type should not ever be in a variable name (ex: “petArray”); the name itself should be clear enough to indicate the type of data it holds (ex: “allPets”).
- An event handler should not have “handler” in the name (ex: “clickHandler”); the name should indicate the handler’s purpose (ex: “addNewPet”).
- Style and syntax meets the criteria of the Turing JS Style Guide.
- Function declarations are used over anonymous functions in event listeners.