BONUS: 3‌ CHECKPOINTS AWARDED WORTH ‌$50‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to the CS-STEM Level Editor Wireframe contest. The NoNameSite.com has a number of games (e.g., Bewildering Booleans, The Claw, Treasure Hunter, The Ball, etc.), that each involve a series of "levels," with each level being a screen or page in the game that is a different puzzle for the player to solve (e.g., Level 1, Level 2). The goal of this wireframe is to create the pages to allow NoNameSite members to create, edit, and modify sets of levels using a "Level Editor," and to share those levels with other NoNameSite members in a "Member-Created Levels area" for each game. The focus here is on workflow and ease of use.

You will need to think about the user scenarios described and "wireframe" how you think the user will most easily use this new functionality. Focus on the functionally and goals of the application and what is the best workflow for enabling the creation, editing, and playing of new levels. At the end of this contest we want to have a clean, intuitive, and easy-to-use set of wireframes that will be a great input for development.

Round 1

- All required features mentioned in the requirements section
- Any notes for the client about your submission 

Round 2

- All required features mentioned in the requirements section
- Any notes for the client about your submission 


Primary Goal & Design Considerations

The objective of this contest is to update the existing wireframe and to add the feature of a game Level Editor.

Currently, the games' set of levels are stored in a text file that describes the starting locations/positions/formulas for the game objects. By editing this text file, a game developer can modify the set of levels.

We currently do not give members access to the text files or the capability to create or modify game levels, but now we want to allow NoNameSite members to create, edit, and modify sets of levels. In order to do this we need to have a "level editor" and a "member-created levels area" for each game.

 

Requirements
1) Level Editor

- Provide a functionality for the members to create or edit levels for each game
- Each game has different settings of levels and objects
- As part of the level creating process, a member goes to the "level editing" area, and selects a set of levels to edit.
- The selected set can be a set of levels previously created by that same member.
- A "New" set of levels can be selected, which is a copy of a default set of levels, or a copy of a "published" member-created set of levels.
- The member can create/edit metadata about the selected level, specifically, a name for the set of levels, a few lines of description, and whether the level is ready to be published.
- A set has Level 1, Level 2, Level 3, etc. The various game objects or metadata are configured differently in each level.
- There are different types of metadata for each games and they are included in the provided document
- The member can develop the selected set of levels by going back and forth between editing the set of levels with an editor and testing the the set of levels by playing them.
- When the member determines the levels are complete, the member can "publish" the set of levels by clicking a box that says that the level is ready for publication.
- When the publication box is clicked, the set is made available in the "published levels" area for that game, once published, the member won't be able to edit it.
- The member can decide at any time to unpublish the level by unclicking the publish checkbox, edit the level, and then again click the box that it is ready for sharing.
- There should be an easy capability (e.g., a button) for the member to use to notify their friend about a published set of levels, or to post it on that member's own Facebook wall if they have Facebook integration in place.


2) Member Created Levels Area
- For each game there needs to be a "member-created levels" area where members can find sets of levels created by members and try them
- This area should have a list of the published sets of levels, and show with the name of the set, the name of the member who created it, the description, the date published, and some stats about the set - the number of times it has been played, the last time it was played, the number of people currently playing, as well as a picture of the first level in the set.
- When a set is selected to be played, the page around it provides descriptive information and stats mentioned above, as well as a leaderboard for the set of levels, and also has a place where members can post comments on the set of levels.


Target Audience

Please note our target audience will be 13-18 year olds in the USA who may have little to no experience with programming. We want to make sure the flow of this update will be user friendly for all skill sets. It should be a fun experience for them and not frustrating.


Judging Criteria

Your submission will be judged on the following criteria:

- User Experience
- Completeness and accuracy of the wireframe as defined in the requirements.
- How well your wireframes provide a consistent user flow
- How well you implement the required data and any suggestions, interactions and user flow you recommend (provide any notes or comments for the client)

 

Submission & Source Files

Preview Image

Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

 

Submission File

Generated HTML files with all the requested contest requirements stated above.

 

Source Files

Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.

Final Fix

As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.

Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

ELIGIBLE EVENTS:

2012 TopCoder(R) Open

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • HTML
  • description

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30024726