Client side route structure

/

• Landing page
• Should contain a text input for searching algs
• Should contain lists of new and trending algs
• Include a list of popular algsets
• Include fun extra data like number of algs / sets / users?

/puzzles

• Provide UI to select a puzzle

/puzzle/:puzzleId/

• Contains a list of the root algsets that fall under it

/puzzle/:puzzleId/:algset/

• Will either contain a list of subsets, or the algs contained under it

/puzzle/:puzzleId/:algset/:subset?/:caseId

• Contains the list of algsfor the case

/search?query=?

• This will take whatever search query and return algs based on it
• TODO: think of all the different ways we might want to search
• Search for a puzzle, algset, subset, specific case.
• Filter by tags using hashtags
• Autocompleted/Validation for search as user types
• Search UI
  • # tags
  • @username
  • ?? algset
  • ?? puzzle

/users Returns a list of users

/users/:userId

• Shows a users’ “profile”? Lists their favorite algs
• Group algs by algset?

/admin/

• Provide UI to manage users
• Provide UI to change users’ roles
• Provide UI to create algsets / subsets