wdi-sg · strisen · Dec 6, 2017 · Dec 6, 2017 · Dec 6, 2017 · Dec 6, 2017
diff --git a/README.md b/README.md
@@ -1,96 +1,65 @@
-# Project Name (Start editing here)
-<!---
-Read Me Contents
--->
+# Project #1: Memory Game
 
-# ![](https://ga-dash.s3.amazonaws.com/production/assets/logo-9f88ae6c9c3871690e33280fcf557f33.png) Project #1: The Game
+### Table of Contents
 
-### Overview
+* **Introduction**
+* **How To Play**
+* **Technical Limitations**
+* **Future Updates**
+* **Acknowledgements**
 
-Let's start out with something fun - **a game!**
+**Click [here](https://strisen.github.io/project-1/) to try out the game!**
 
-Everyone will get a chance to **be creative**, and work through some really **tough programming challenges** – since you've already gotten your feet wet with Tic Tac Toe, it's up to you to come up with a fun and interesting game to build.
+___
 
-**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!
+### Introduction
 
+This is a simple memory game for 2 players. 
+The objective of this memory game is to match the pairs of cards together and get more points than your opponent.
 
----
+___
 
-### Technical Requirements
+### How To Play
 
-Your app must:
+* To start, click on the "New Game" button. Player 1 will start first, and will be highlighted in red as the active player.
 
-* **Render a game in the browser**
-* **Any number of players** will be okay, switch turns will be great 
-* **Design logic for winning** & **visually display which player won**
-* **Include separate HTML / CSS / JavaScript files**
-* Stick with **KISS (Keep It Simple Stupid)** and **DRY (Don't Repeat Yourself)** principles
-* Use **Javascript** for **DOM manipulation**, jQuery is not compulsory
-* **Deploy your game online**, where the rest of the world can access it
-* Use **semantic markup** for HTML and CSS (adhere to best practices)
-* **No canvas** project will be accepted, only HTML5 + CSS3 + JS please
+![](https://github.com/strisen/project-1/blob/updates/images/newGameButton.png)
 
----
+* Each player will have up to 10 seconds to get as many matching pairs as possible.
 
-### Necessary Deliverables
+* A player switch will occur whenever a non-matching pair is flipped.
 
-* A **working game, built by you**, hosted somewhere on the internet
-* A **link to your hosted working game** in the URL section of your GitHub repo
-* A **git repository hosted on GitHub**, with a link to your hosted game, and frequent commits dating back to the very beginning of the project
-* **A ``readme.md`` file** with explanations of the technologies used, the approach taken, installation instructions, unsolved problems, etc.
+* The game will continue until either player gets 5 points, or if both players end with 4 points each.
 
----
+* Click the "Try again?" button to start over again.
 
-### Suggested Ways to Get Started
+![](https://github.com/strisen/project-1/blob/updates/images/gameRestart.png)
 
-* **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.
+___
 
----
+### Technical Limitations
 
-### Potential Project Ideas
+* Latest versions of Chrome / Safari / Firefox will be able to run this game with full animations.
 
-##### Blackjack
-Make a one player game where people down on their luck can lose all their money by guessing which card the computer will deal next!
+* IE will load a fall back version that does not utilise 3D transforms.
 
-##### Self-scoring Trivia
-Test your 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!
+___
 
----
 
-### Useful Resources
+### Future Updates
 
-* **[MDN Javascript Docs](https://developer.mozilla.org/en-US/docs/Web/JavaScript)** _(a great reference for all things Vanilla Javascript)_
-* **[jQuery Docs](http://api.jquery.com)** _(if you're using jQuery)_
-* **[GitHub Pages](https://pages.github.com)** _(for hosting your game)_
-* **[How to write readme - Markdown CheatSheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet)** _(for editing this readme)_ 
-* **[How to write a good readme for github repo!](https://gist.github.com/PurpleBooth/109311bb0361f32d87a2)** _(to make it better)_
+* Difficulty Settings
 
----
+* Single Player Mode
 
-### Project Feedback + Evaluation
+and more!
 
-* __Project Workflow__: Did you complete the user stories, wireframes, task tracking, and/or ERDs, as specified above? Did you use source control as expected for the phase of the program you’re in (detailed above)?
+___
 
-* __Technical Requirements__: Did you deliver a project that met all the technical requirements? Given what the class has covered so far, did you build something that was reasonably complex?
+### Acknowledgements
 
-* __Creativity__: Did you add a personal spin or creative element into your project submission? Did you deliver something of value to the end user (not just a login button and an index page)?
+[Fisher - Yates Shuffle](https://bost.ocks.org/mike/shuffle/)
 
-* __Code Quality__: Did you follow code style guidance and best practices covered in class, such as spacing, modularity, and semantic naming? Did you comment your code as your instructors have in class?
+[CSS3 3D Flipping](http://css3.bradshawenterprises.com/flip/)
 
-* __Deployment__: Did you deploy your application to a public url using GitHub Pages?
-
-* __Total__: Your instructors will give you a total score on your project between:
-
-    Score | Expectations
-    ----- | ------------
-    **0** | _Incomplete._
-    **1** | _Does not meet expectations._
-    **2** | _Meets expectations, good job!_
-    **3** | _Exceeds expectations, you wonderful creature, you!_
-
- This will serve as a helpful overall gauge of whether you met the project goals, but __the more important scores are the individual ones__ above, which can help you identify where to focus your efforts for the next project!
+___
diff --git a/assets/css/stylesheet.css b/assets/css/stylesheet.css
diff --git a/assets/js/script.js b/assets/js/script.js
diff --git a/images/ace.png b/images/ace.png
diff --git a/images/cardBack.png b/images/cardBack.png
diff --git a/images/eight.png b/images/eight.png
diff --git a/images/five.png b/images/five.png
diff --git a/images/four.png b/images/four.png
diff --git a/images/gameRestart.png b/images/gameRestart.png
diff --git a/images/newGameButton.png b/images/newGameButton.png
diff --git a/images/seven.png b/images/seven.png
diff --git a/images/six.png b/images/six.png
diff --git a/images/three.png b/images/three.png
diff --git a/images/two.png b/images/two.png
diff --git a/index.html b/index.html
@@ -1,11 +1,67 @@
 <!DOCTYPE html>
 <html>
-  <head>
-    <meta charset="utf-8">
-    <title></title>
-    <link rel="stylesheet" href="css/style.css">
-  </head>
-  <body>
-    <script src="js/script.js" charset="utf-8"></script>
-  </body>
+<head>
+	<meta charset="utf-8">
+	<meta name="viewport" content="width=device-width, initial-scale=1.0">
+	<meta http-equiv="X-UA-Compatible" content="ie=edge">
+	<script src="https://code.jquery.com/jquery-3.2.1.js"></script>
+	<link href="https://fonts.googleapis.com/css?family=Orbitron|Vollkorn+SC" rel="stylesheet">
+	<link rel="stylesheet" type="text/css" href="memoryGame.css">
+	<title> Memory Game </title>
+</head>
+<body>
+
+		<!-- Game Interface -->
+
+		<div class="gameBoard">
+		<div class="gameTopSection">
+			<div class="gameTitle"> Memory Game Versus </div>
+			<div class="playerOne"> Player One <div class="playerScore" id="p1">0</div></div>
+			<div class="statusMenu">
+
+				<div class="currentPlayer"> Time Remaining: <div class="timerDisplay"> None </div></div>
+
+				<div class="newGame">
+
+					<button class="reset"> New Game </button>
+
+					<!-- Modal Functionality -->
+
+					<div class="modal" id="prompt">
+
+						<div class="modalContent">
+
+							<div class="modalHeader"> &nbsp; </div><span id="closeBtn"> X </span>
+							<div class="modalBody"></div>
+							<div class="modalFooter"><button class="reset" id="modalReset"> Try again? </button></div>
+
+						</div>
+
+					</div>
+
+					<!-- End of Modal Functionality -->
+
+				</div>
+			</div>
+			<div class="playerTwo"> Player Two <div class="playerScore" id="p2">0</div></div>
+		</div>
+
+		<!-- End of Game Interface -->
+
+		<!-- Card Board -->
+
+		<div id="mainBoard"></div>
+
+		<!-- End of Card Board -->
+
+		</div>
+<div class="container-fluid">
+	<footer class="footerBar">
+		<p id="viewed"> Best  Viewed  in  Chrome / Firefox / Safari </p>
+	</footer>
+
+</div>
+
+	<script src="memoryGame.js"></script>
+</body>
 </html>