Every developer has more ideas than time. As David Allen likes to say “the human brain is for creating ideas, not remembering them.” In this project, we’ll be building a simple application for recording and archiving our ideas (good and bad alike).

Throughout the project, one of our focuses will be on providing a fluid and responsive client-side interface. To this end, we’ll rely on JavaScript and jQuery to implement snappy filtering in the browser, and localStorage to persist our wonderful ideas between sessions.

For this project, we’ll be increasingly thinking about the “server” and “client” as separate entities. We’ll be using:

• JavaScript (with jQuery) to manage client-side interactions.
• JSON and localStorage to persist data between sessions.
• Your entire application will consist of one HTML page or template.

• An Idea has an id, title, a body, and a quality.
  • The id should be a unique identifier.
  • title and body are free-form strings.
• Quality should be one of the follow: “genius”, “plausible”, and “swill.”
• By default, the idea’s “quality” should default to the lowest setting (i.e. “swill”).

When visiting the application, the user should:

• See a list of all existing ideas, including the title, body, and quality for each idea.
• Ideas should appear in descending chronological order (with the most recently created idea at the top).

On the application’s main page, a user should:

• See two text boxes for entering the “Title” and “Body” for a new idea, and a “Save” button for committing that idea.

When a user clicks “Save”:

• A new idea with the provided title and body should appear in the idea list.
• The text fields should be cleared and ready to accept a new idea.
• The page should not reload.
• The idea should be persisted. It should still be present upon reloading the page.

When viewing the idea list:

• Each idea in the list should have a link or button to “Delete” (or 𝗫).
• Upon clicking “Delete”, the appropriate idea should be removed from the list.
• The page should not reload when an idea is deleted.
• The idea should be removed from localStorage. It should not re-appear on next page load.

As we said above, ideas should start out as “swill.” In order to change the recorded quality of an idea, the user will interact with it from the idea list.

• Each idea in the list should include an “upvote” and “downvote” button.
• Clicking upvote on the idea should increase its quality one notch (“swill” → “plausible”, “plausible” → “genius”).
• Clicking downvote on the idea should decrease its quality one notch (“genius” → “plausible”, “plausible” → “swill”).
• Incrementing a “genius” idea or decrementing a “swill” idea should have no effect.

• When a user clicks the title or body of an idea in the list, that text should become an editable text field, pre-populated with the existing idea title or body.
• The user should be able to “commit” their changes by pressing “Enter/Return” or by clicking outside of the text field.
• If the user reloads the page, their edits will be reflected.

We’d like our users to be able to easily find specific ideas they already created, so let’s provide them with a filtering interface on the idea list.

• At the top of the idea list, include a text field labeled “Search”.
• As a user types in the search box, the list of ideas should filter in real time to only display ideas whose title or body include the user’s text. The page should not reload.
• Clearing the search box should restore all the ideas to the list.

Go for it!! 💪

• When viewing the ideas list, the user should have the option to sort ideas by Quality.
• The default sort should be descending (“genius” → “plausible” → “swill”), and clicking the sort a second time should reverse it.
• The Idea list should be sorted client-side without reloading the page.