diff --git a/.DS_Store b/.DS_Store
new file mode 100644
index 00000000..611e577e
Binary files /dev/null and b/.DS_Store differ
diff --git a/README.md b/README.md
index 49093dd2..d4e22426 100644
--- a/README.md
+++ b/README.md
@@ -1,37 +1,19 @@
# 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.
+This is a movie search engine and data is fetched from [Open Movie Database](http://www.omdbapi.com) API.
-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.
+There are two sets of html and js files; each is responsible for one page.
-To get started, fork and clone this repo. Please submit a pull request after your first commit and push commits regularly.
+The movie.html and movie.js are to create the movie search functionality. Within this page, the users can search for movies using key words, read expanded movie details, use pagination to switch between pages, and save movies to favorites. A preview window will appear once three or more letters are typed in the search box.
-You should complete as many of the following tasks as you can.
+The favorite.html and favorite.js are to save your favorite movies using local storage. The up and down buttons can be used to re-order them.
-- [ ] 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
+To switch between search and favorites, you can use the go to buttons at the top of the pages.
-**Movie details**
+Both pages are responsive to different screen widths using the same css style file.
-- [ ] 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
-**Your own feature**
-- [ ] Implement any feature you would find useful or interesting
-
-**Stretch goals**
-
-- [ ] 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
@@ -42,7 +24,3 @@ Hint: You may want to kick of the searching after at least 3 characters have bee
* 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
-
-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.
diff --git a/button.png b/button.png
new file mode 100644
index 00000000..486970be
Binary files /dev/null and b/button.png differ
diff --git a/favorite.html b/favorite.html
new file mode 100644
index 00000000..21c0de00
--- /dev/null
+++ b/favorite.html
@@ -0,0 +1,22 @@
+
+
+