diff --git a/README.md b/README.md
index 49093dd2..0343c7ca 100644
--- a/README.md
+++ b/README.md
@@ -1,48 +1,80 @@
# Project Cinema
-We want to create a movie search engine. To power it we will use the [Open Movie Database](http://www.omdbapi.com) API.
+> # A movie search engine powered by the [Open Movie Database](http://www.omdbapi.com) API.
+>
+> ## _”A mobile-first, responsive design that looks great at different screen widths“_
-To start using the OMDB API you will first need to sign up with them to receive and API key. The key issued to you will allow you 1000 requests per day and you will need to include this key as part of every request.
+---
-To get started, fork and clone this repo. Please submit a pull request after your first commit and push commits regularly.
+---
-You should complete as many of the following tasks as you can.
+## UX
-- [ ] Work using mobile first, that is create the mobile version first and add tablet and desktop versions after.
-- [ ] Create an HTML page which should have a `form` at the top which contains a text input and a submit button. Below it should have a placeholder element for the returned results.
-- [ ] Use JavaScript to capture the `submit` event in your search form, extract the query string from the text input and use that to make an API call to the Open Movie Database API to search for films which match the query string using `fetch`. `console.log` the results
-- [ ] Display the data returned by the API including title, year and poster picture
+- Type in your search query and hit the button.
-**Movie details**
+
-- [ ] Adjust your layout to create room for a detailed view of movie information
-- [ ] Capture clicks on your movie results items and use that information to make another request to the API for detailed movie information. Using event delegation will help you here. `console.log` the returned result
-- [ ] Display the detailed movie result in the in the details view you created earlier
-- [ ] Make your design responsive and ensure it looks great at different screen widths
+- Search results are loaded below and the screen scrolls up automatically.
-**Your own feature**
+- Load more search results by paging through. You get 10 results at a time.
-- [ ] Implement any feature you would find useful or interesting
+
-**Stretch goals**
+- Just tap on any of the films in the search results to see more information. This loads below the search results and the screen scrolls up automatically.
-- [ ] Implement pagination so that users can navigate between all movies in search results rather than just the first ten
-- [ ] Create a favourites list. It's up to you how you would add items to favourites. You could add a button or otherwise. Display a list of favourites somewhere on your page.
-- [ ] Make the favourites list sortable. Add `up` and `down` buttons to your favourites which on click will move the result in relevant direction
-- [ ] Save favourites locally using `localStorage` so that favourites persist in browser after refresh
-- [ ] Let's create a search preview. It should listen for change events on input events and submit a search request with current query string. Display the search preview results in an absolute positioned container just below the search box.
-Hint: You may want to kick of the searching after at least 3 characters have been typed.
+
-## Objectives
+- Save your favourite films - just click the button on the film detail view.
-* We want to see great looking webpages that work well at all screen widths
-* Your code should have consistent indentation and sensible naming
-* Use lots of concise, reusable functions with a clear purpose
-* Add code comments where it is not immediately obvious what your code does
-* Your code should not throw errors and handle edge cases gracefully. For example not break if server fails to return expected results
-* Use BEM methodology to style your page
-* Try to use pure functions as much as possible, but keep in mind it will not be possible to make all functions pure.
+
-## README.md
+- You can see your list of favourites by clicking the account button in the header. You can delete films from the list individually or delete them all with a single click.
-When finished, include a README.md in your repo. Someone who is not familiar with the project should be able to look at it and understand what it is and what to do with it. Explain functionality created, mention any outstanding issues and possible features you would include if you had more time. List technologies used to create the app. Include a screenshot of your app in the README.
+
+
+## Technology used
+
+- **HTML & CSS** (Flexbox, Grid)
+ - BEM methodology used in markup and CSS.
+ - Individual media queries for tablet and desktop in separate files to make the styles easier to maintain.
+- **JavaScript** (Fetch, OMDB API, localStorage)
+ - Functions are pure as much as possible – concise reusable and each with with a clear purpose.
+ - Well commented throughout.
+
+## Surprise feature
+
+- If the film you‘re looking for doesn't have a poster then look out for the ’Fill Ferrell‘ placeholder image.
+
+
+
+---
+
+## Challenges, learnings and TODOs
+
+- **localStorage**
+
+ - Favourites currently stored individually in localStorage.
+ - Working with a database that stores strings of information is challenging.
+ - TODO: Need to refactor to store a single object in localStorage. On page load this can be retrieved and parsed. Stored in an object the user favourites can then be manipulated and updated. On any interaction even the object can be stringified before re-setting in localStorage.
+ - [ ] TODO: Make the favourites list sortable. Add `up` and `down` buttons to your favourites which on click will move the result in relevant direction. Also sortable by date saved and film title.
+ - [ ] TODO: Implement a watch list feature to save films that you want to see as well as favourites.
+
+- **Search**
+
+ - [ ] TODO: Create a search preview. It should listen for change events on input events and submit a search request with current query string. Display the search preview results in an absolute positioned container just below the search box. Kick of the searching after at least 3 characters have been typed.
+
+- **Refactoring**
+
+ - [ ] TODO: Refactor code to make use of export/import to keep JS easy to navigate and maintain.
+
+---
+
+### The original brief
+
+- We want to see great looking webpages that work well at all screen widths
+- Your code should have consistent indentation and sensible naming
+- Use lots of concise, reusable functions with a clear purpose
+- Add code comments where it is not immediately obvious what your code does
+- Your code should not throw errors and handle edge cases gracefully. For example not break if server fails to return expected results
+- Use BEM methodology in your markup and CSS to style your page
+- Try to use pure functions as much as possible, but keep in mind it will not be possible to make all functions pure.
diff --git a/index.html b/index.html
new file mode 100644
index 00000000..98a03af6
--- /dev/null
+++ b/index.html
@@ -0,0 +1,46 @@
+
+
+
+
+
+
+
+ The Reel Thing - Find Your Favourite Films
+
+
+
+
+
+
+
+
+
+