Design doc review #3 - Backend and Frontend routes

[aracpyon]

Backend Routes

• Users
• [x] GET /api/users/:user_id/albums - return all albums associated with the artist move this under albums
• [x] GET /api/users/:user_id/tracks - return all tracks associated with the artist move this under tracks

Frontend routes

• [x] /artists/:artistId/albums/:albumId => should have Banner, SideBar and Detail. (Basically the same information you have on /artists/:artistId right now.
• [x] /artists/:artistId/albums will be rendered when the user clicks music button on the artist's page. And it will render the thumbnails of all albums that belongs to the artist.
• [x] /artists/:artistId => This route is working the same as /artists/:artistId/albums. When we go on to the artist's show page, it shows the albums thumbnails. So change fromDetailtoDiscog`

[aracpyon]

• [ ] For the search, your search bar basically searches for albums, tracks, artists, right? Because we don't want to make three different ajax calls on on search bar, you probably need to create a search controller that's is going to receive one ajax call from the search bar and search on the entire tables. That being said, remove the words for search feature from each table.