Implement Routing

[zverev]

Suggested routes:

• /:categoryId - map without sidebar showing current category items
• /:categoryId/items - opened sidebar with a list of category items
• /:categoryId/imtes/:itemId - detailed item info (also displayed in sidebar; accordeon-style)

When user clicks item on the map, he gets /:categoryId/imtes/:itemId
When user switches a tab in the sidebar, he gets /:categoryId/items
When user closes sidebar, he gets /:categoryId

[oleksmarkh]

Do we want to handle multiple generic categories? If so, could you please mention some examples. If not, perhaps, it could make sense to maintain more explicit routes, such as <some_category>/items/:id, implying an :id being particularly attached to items. This is rather UX suggestion, in fact.

[zverev]

You mean, could multiple categories be selected at one time?
It is a good question. Lets simplify our job and consider answer to be no 🙂
At least, previous version of crisismap didn't support this feature.

[oleksmarkh]

I'm fine with "no" for now. @Godnik, what do you think?

[oleksmarkh]

Definitions themselves are described/discussed on Crisismap/crisismap-backend#1.

I assume, this task is rather about setting up the router, wiring it with simplistic data fetching module (to be introduced in #7).