stevennooijen / stairwaytotravel-frontend Goto Github PK

After moving the map you have to click "search here" again. It would be more user friendly if you can toggle on/off a "search while move" functionality such that you can more interactively explore the map.

As a user, I want my search query and liked places to remain visible when I refresh the page, so that I don't have to start all over again after a page refresh.

This could probably be resolved by storing session history in the session storage and fetching it from there again upon refresh.

The weather data is already available in the backend, we just need to visualise it to the place page.

A bit of backend work is still required to adjust the API for fetching weather data.

After querying on a region, you cannot delete the query and reset.

Something like a small cross within the searchbar on the right would fix this.

Currently filtering of destinations can only be done on the main activity groups Nature, Culture, Active, City and Beach.

However, people would also like to be able to filter on specific activity types like "surfing" or "mountains".

This issue is about creating the filters in the frontend. To make the functionality work, the backend API will also need to be adjusted to facilitate this type of filtering.

Data needs to be gathered first. Goal, be able to know cost of living for a place.

For example, Google reports:
"3-star hotel averaging €35, 5-star averaging €85"

Capturing user searches, views, likes and other interactions will lead to valuable information to improve recommendations or offer analytical services.

As a user, I would like to filter places based on cost of living / required budget.

Dependency: issue number #6

Having the weather data available for each place, users would like to filter on weather by month to select places with their preferred weather conditions for their holiday.

As a user, I want to be able to easily share a place with my friends so that I can share my enthusiasm for a place with fellow travellers.

As a user, I want to be able to share my bucketlist/itinerary, so that I can enthousiast my fellow travellers about the trip that I hope to make.

Currently people receive the bucketlist/itinerary by email after checkout. This feature would enable people to share earlier using WhatsApp or other media and link straight back to the website.

When looking at a place, users would like to know more about what can be done at that place.

We could display top items to do using APIs with for example Airbnb experiences, Tripadvisor, ...

As a user, I want to login and save my likes and searches in my profile so that I can revisit what I looked at later.

Currently users have to checkout to receive an email with their bucketlist. We don't store any data from them, so each time a user comes to the platform, they will have to start all over again. Users have said they would like to build up different bucketlists, like one for wintersport, one for the summer, one for diving holidays, etc...

Currently 3 different icons are used for displaying the place type on the map depending on Wikivoyage placeType and placeStatus. This could be improved in something more sensible, possibly connected to the user (activity) search query.

Users often requested to filter based on place popularity. E.g. what are the must-see places, and which are only visited by locals?

Such a filter could be based on Wikivoyage page views per place, to give a first estimation on what is popular and what not. Data will need to be analysed in the backend before such a feature could be added.

As a user, I expect the ordering of places in the stream to be the same when I click on a place and then go back so that I am not confused about which places I have already watched and which not.

Comment of a user: "What is a little bit annoying is that when you open a destination and then press the back button, the list is shuffled again."

Cause: the API returns destinations with a certain order, we are just losing that now with the async call in the frontend.