For this project, you'll be creating a familiar game with HTML, CSS and JS! Please choose one of the following:
- Tower of Hanoi
- Trivia (Self-scoring)
- Flash Cards
- Simon
- Hangman
This is an opportunity to be creative, and work through some tough programming challenges.
You will be working individually for this project, but we'll be guiding you along the process and helping as you go. Show us what you've got!
Your app must:
- Render in the browser
- Include separate HTML / CSS / JavaScript files
- Stick with KISS (Keep It Stupid Simple) and DRY (Don't Repeat Yourself) principles
- Use Javascript or jQuery for DOM manipulation
- Deploy online, using Github Project pages.
- Use semantic markup for HTML and CSS (adhere to best practices)
- A hosted copy of your game or app, built by you, hosted on Github Pages
- Your HTML/CSS should pass the HTML5 Validator and CSS Validator
- A git repository hosted on Github with frequent commits dating back to the very beginning of the project
- A link to your hosted project in the URL section of your Github repo
The URL section of your Github repo:
Create a new repository - DO NOT FORK THIS REPO. Then, submit your project as an issue to this repo:
github.com/ga-dc/project1-gallery
You must turn in something before presentations begin. However, you're welcome to continue working on it over the course of WDI and beyond!
With your submission please include any questions you'd like answered, or specific things on which you'd like us to focus.
DO NOT follow the instructions provided by GitHub for creating your Project Pages. Why not? They expect gh-pages to be a separate informational site about the project contained in the repo. What we want is to use the gh-pages functionality to actually host our application.
Instead, try these steps:
git checkout master
git checkout -b gh-pages
git push -u origin gh-pages
Browse to <your_github_username>.github.io/<repo_name>
After making further changes, deploy via push:
git push origin gh-pages
Create your bronze, silver, and gold plan.
- Break the project down into different components (data, presentation, views, style, DOM manipulation) and brainstorm each component individually. Use whiteboards!
- Use your Development Tools (console.log, inspector, alert statements, etc) to debug and solve problems
- Work through the lessons in class & ask questions when you need to! Think about adding relevant code to your game each night, instead of, you know... procrastinating.
- Commit early, commit often. Don’t be afraid to break something because you can always go back in time to a previous version.
- Consult documentation resources (MDN, jQuery, etc.) at home to better understand what you’ll be getting into.
- Don’t be afraid to write code that you know you will have to remove later. Create temporary elements (buttons, links, etc) that trigger events if real data is not available. For example, if you’re trying to figure out how to change some text when the game is over but you haven’t solved the win/lose game logic, you can create a button to simulate that until then.
Pre-load your app with some data, and let the user flip through them quickly (back or front), and use the keyboard flip the card, and to mark whether they got it right or not. Track which cards were incorrect, and re-display them until the user gets them right!
Bonus:
- Track scores over time (even if the page is reloaded)
- Include images on one or both sides of the flash card
- Let the user add flash cards (don't need to be saved across refreshes)
Pre-load your app with some questions and answers.
Test the user's wits & knowledge with whatever-the-heck you know about (so you can actually win). Guess answers, have the computer tell you how right you are!
Bonus:
- Add time-based scoring
- Track scores across games (even if the page is reloaded)
- Allow users to compete against each other on a high-score board.
Have a player enter a word that will be guessed during the game. The word is then hidden and represented by blank spaces. The second player then chooses letters, which are revealed if present.
Bonus:
- Add timer-based scoring
- Track scores across games (even if the page is reloaded)
Tower of Hanoi is a mathematical puzzle where the objective is to move a stack of discs from one rod to another. There are three rules:
-
Only one disk can be moved at a time
-
Every move involves taking the top disk from one of the stacks and placing it on top of another stack
-
No disk can be put on top of a smaller disk
Bonus:
- Add time-based scoring
- Track scores across games (even if the page is reloaded)
Simon is a test of memory. Have your program choose a sequence of different colors at random and then prompt your player repeat the sequence allowing them to go to advance to next round if the player is successful.
Bonus:
- Add timer-based scoring
- Track scores across games (even if the page is reloaded)
- MDN Javascript Docs (a great reference for all things Vanilla Javascript)
- jQuery Docs (if you're using jQuery)
- Github Pages (for hosting your game)
Your instructors will use this rubric to assess your project:
We expect everyone to attend all presentations in their entirety and will provide breaks between each session.
This means no working on your code while others are presenting. This is your chance to ask others how they tackled their project.
Each session of presentations will be science-fair style. Several people will set up at a given time, and other students will walk around asking questions like:
- What would you do differently?
- What are you most proud of?
- What would you do next?
- How did you plan your project?
- What did you learn?