Instruction

1. Fork the repository
2. Clone the forked repository with git clone <your fork URL>
3. Create a branch with git checkout -b your-branch-name
4. Finish the challenge on your branch
5. Once you are ready to submit, create a pull request, the destination is your forked repository's master
6. Submit the pull request URL to us

---

Envoy is hiring! We're trying to build an easter egg in our site to hire a talented JavaScript developer. Here is how it'll work: There is a sign up form in Envoy's webpage. (index.html) When the user's e-mail has keywords such as "JavaScript" or "Ruby", we'll display a modal that covers entire screen says "Looks like you're a kickass coder, do you want to play a game?"

Please implement the following features by updating app.js and index.html

1. When the user enter their email address, as soon as it has a keyword that we are looking for, display the modal
2. When the user clicks "No", it should hide the modal
3. When the user clicks "Yes", it should redirect them to challenge.html
4. Sign up form and modal are provided in index.html

---

In the challenge page, we’d like to test the user’s ability to sort list of numbers. We'll give them a set of numbers, and their job is to sort those numbers in ascending order. There's an input on the page for them to type their answer into. Since we don’t want every candidate to see the same set of numbers, we need to randomize them every time the challenge page loads.

Please implement the following features by updating challenge.js and challenge.html:

1. Replace content inside <p class="numbers">10,3,1,2,5,9</p> to display a list of random numbers. The length of these numbers are also random.
2. When the user clicks "submit", if the answer is correct, then redirect them to pass.html
3. When the user clicks "submit", if the answer is incorrect, then redirect them to retry.html

Bonus points:

1. We also want the user to drop any number if it’s a duplicate. For example, if we display this list of numbers: "2,1,5,3,2,6", the correct answer would be "1,2,3,5,6"
2. Limit the number of retries to three. After the users fail to answer the question for three times, redirect them to fail.html