init

Author: “spb-superstruct”

README.md

@@ -0,0 +1,22 @@
+![Polycade.com](https://i.imgur.com/jcvsFKh.png)
+
+---
+
+# Polycade Engineering QA Challenge
+
+We need to add lots of features quickly and be sure not to break any existing functionality. We want to make sure that you can review our engineers' work and catch any issues before our users do. Can you review pull requests and communicate with engineers?
+
+## The Challenge
+
+We have a todo app that is using [todoMVC](http://todomvc.com/) as its base, we'd like to add new features. These features are described in two open issues. An engineer has created two new pull requests satisfy the issues. Your challenge is to investigate these two pull requests and make sure that the features work correctly and will not negatively impact the user experience.
+
+## Instructions
+
+How to attempt this challenge:
+
+1) Do not fork, comment, open issues, or otherwise interact directly with this repo.
+2) To see the current, deployed version of our app, visit https://qa.challenges.polycade.com
+3) View the [list of open pull requests](https://github.com/polycade/challenge-qa/pulls)
+4) We use [Netlify Deploy Previews](https://www.netlify.com/blog/2016/07/20/introducing-deploy-previews-in-netlify/). You may view a deploy preview for each pull request by clicking on the appropriate link in the "checks" section of the PR.
+5) Investigate the pull requests. Take note of any problems.
+6) Create a [Secret Gist](https://gist.github.com) with your notes, and send its URL to your hiring contact.

base.css

@@ -0,0 +1,141 @@
+hr {
+	margin: 20px 0;
+	border: 0;
+	border-top: 1px dashed #c5c5c5;
+	border-bottom: 1px dashed #f7f7f7;
+}
+
+.learn a {
+	font-weight: normal;
+	text-decoration: none;
+	color: #b83f45;
+}
+
+.learn a:hover {
+	text-decoration: underline;
+	color: #787e7e;
+}
+
+.learn h3,
+.learn h4,
+.learn h5 {
+	margin: 10px 0;
+	font-weight: 500;
+	line-height: 1.2;
+	color: #000;
+}
+
+.learn h3 {
+	font-size: 24px;
+}
+
+.learn h4 {
+	font-size: 18px;
+}
+
+.learn h5 {
+	margin-bottom: 0;
+	font-size: 14px;
+}
+
+.learn ul {
+	padding: 0;
+	margin: 0 0 30px 25px;
+}
+
+.learn li {
+	line-height: 20px;
+}
+
+.learn p {
+	font-size: 15px;
+	font-weight: 300;
+	line-height: 1.3;
+	margin-top: 0;
+	margin-bottom: 0;
+}
+
+#issue-count {
+	display: none;
+}
+
+.quote {
+	border: none;
+	margin: 20px 0 60px 0;
+}
+
+.quote p {
+	font-style: italic;
+}
+
+.quote p:before {
+	content: '“';
+	font-size: 50px;
+	opacity: .15;
+	position: absolute;
+	top: -20px;
+	left: 3px;
+}
+
+.quote p:after {
+	content: '”';
+	font-size: 50px;
+	opacity: .15;
+	position: absolute;
+	bottom: -42px;
+	right: 3px;
+}
+
+.quote footer {
+	position: absolute;
+	bottom: -40px;
+	right: 0;
+}
+
+.quote footer img {
+	border-radius: 3px;
+}
+
+.quote footer a {
+	margin-left: 5px;
+	vertical-align: middle;
+}
+
+.speech-bubble {
+	position: relative;
+	padding: 10px;
+	background: rgba(0, 0, 0, .04);
+	border-radius: 5px;
+}
+
+.speech-bubble:after {
+	content: '';
+	position: absolute;
+	top: 100%;
+	right: 30px;
+	border: 13px solid transparent;
+	border-top-color: rgba(0, 0, 0, .04);
+}
+
+.learn-bar > .learn {
+	position: absolute;
+	width: 272px;
+	top: 8px;
+	left: -300px;
+	padding: 10px;
+	border-radius: 5px;
+	background-color: rgba(255, 255, 255, .6);
+	transition-property: left;
+	transition-duration: 500ms;
+}
+
+@media (min-width: 899px) {
+	.learn-bar {
+		width: auto;
+		padding-left: 300px;
+	}
+
+	.learn-bar > .learn {
+		left: 8px;
+	}
+}