Sorting

(10 additional points.)

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.

Data Model

(5 points total.)

We'll be primarily working with Idea objects.

An Idea has a title, a body, and a quality. (1 point)
title and body are free-form strings.
quality can be represented however you feel best in the database, but in the user interface it should manifest as the options "genius", "plausible", and "swill" (2 points)
By default, the idea's "quality" should default to the lowest setting (i.e. "swill"). (2 points)

Viewing ideas

(10 points total.)

On the application's root, the user should:

See a list of all existing ideas, including the title, body, and quality for each idea. (2 points, mandatory for specification adherence)
Idea bodies longer than 100 characters should be truncated to the nearest word. (5 points)
Ideas should appear in descending chronological order (with the most recently created idea at the top). (3 points)

Idea Filtering and Searching

(15 points total.)

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". (3 points)
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. (6 points)
Clearing the search box should restore all the ideas to the list. (6 points)

Student Directed Extension

(10 additional points.)

Student chooses an additional feature or performance optimization to add to the project. The extension must be intuitive and should not detract from the user's experience in any major way (i.e. not buggy or incomplete).

Adding a new idea

(15 points total.)

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. (3 points, mandatory for specification adherence)
When a user clicks "Save":

A new idea with the provided title and body should appear in the idea list. (5 points, mandatory for specification adherence)
The text fields should be cleared and ready to accept a new idea. (2 points)
The page should not reload. (3 points, mandatory for specification adherence)
The idea should be committed to the database. It should still be present upon reloading the page. (2 points, mandatory for specification adherence)

Deleting an existing idea

(15 points total.)

When viewing the idea list:

Each idea in the list should have a link or button to "Delete" (or 𝗫, etc). (2 points)
Upon clicking "Delete", the appropriate idea should be removed from the list (5 points, mandatory for specification adherence).
The page should not reload when an idea is deleted. (5 points, mandatory for specification adherence)
The idea should be removed from the database. It should not re-appear on next page load. (3 points, mandatory for specification adherence)

Changing the quality of an idea

(15 points total.)

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 a "thumbs up" and "thumbs down" button. (3 points)
Clicking thumbs up on the idea should increase its quality one notch ("swill" → "plausible", "plausible" → "genius"). (4 points)
Clicking thumbs down on the idea should decrease its quality one notch ("genius" → "plausible", "plausible" → "swill"). (4 points)
Incrementing a "genius" idea or decrementing a "swill" idea should have no effect. (4 points)

Editing an existing idea

(20 points total.)

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. (8 points)
Clicking this link should not take the user to a separate "edit" page for the given idea. (4 points, mandatory for specification adherence)
The user should be able to "commit" their changes by pressing "Enter/Return" or by clicking outside of the text field. (4 points)
If the user reloads the page, their edits will be reflected. (4 points, mandatory for specification adherence)

Tagging

(20 additional points.)

Add an optional third text field upon idea creation for "Tags". Tags should be a comma-separated list of short text tags, and should be processed on the server such that any existing tags are re-used, and any new ones are created. Once there are tags to display, a list of existing tags should appear at the top of the idea list. Clicking one of these tags should show only ideas that include it. When viewing ideas filtered by tag, be sure to include a link to take the user back to "All Ideas". This filtering could be implemented either as a separate page or via javascript within the same interface.