Skip to content
Permalink
master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

projects/09 Game Reviews.md

Go to file
 
 
Cannot retrieve contributors at this time
Game Reviews Stage 1 Stage 2 Stage 3
38 lines (28 sloc) 2.29 KB
Raw Blame
Open in GitHub Desktop

Game Reviews

Build a community website to review games (you can choose what type). All the game details and reviews must be stored in a database.

Stage 1

The core functionality consists of three screens:

  1. The home screen should include all the games that have been reviewed. For each there should be the following:
    1. The name of the game
    2. The publisher
    3. The year of release
    4. A thumbnail of the game box cover
  2. There should be a link on the home page to a page that allow users to add new games. This screen should ask for the following:
    1. The game title
    2. The publisher
    3. The year of release
    4. A full-sized image of the game box cover
    5. A detailed, multi-line, formatted description.
  3. If a user clicks on the thumbnail or game title on the home screen they should be taken to the game review screen, this includes:
    1. Details of the game (see section 2)
    2. A list of the reviews given by the users with the most recent at the top and the oldest at the bottom. Each should include the name of the user, the date and the formatted text of their review.
    3. A multiline input box to allow users to post their review. If a user has already reviewed the game the input box should not be displayed.

Stage 2

The intermediate tasks require you to make changes to the functionality:

  1. The system should contain categories such as adventure and sport and each game should be placed in the most suitable one. There should be an admin user who can add and delete these.
  2. Each reviewed post should include the reviewer's first and last names as well as a profile picture (avatar) with a suitable default image used if this is not supplied. There will need to be a profile screen to allow users to update this information. Each user can only review each game once but they can edit their review.
  3. Users should be able to flag a review as being unsuitable or inappropriate. Once more then a specified number of users have flagged a review it should become hidden and the admin user should be sent an email with a link to the review and the choice of either deleting it or approving it.

Stage 3

  1. In addition, the site should be full-text searchable.
  2. Reviewers should be able to upload screenshots of the game they are reviewing.
  3. Users can comment on other reviews.