Navigating in the guidebook

[asaunier]

I had several feedbacks saying that making the "guidebook" menu pointing to the routes list page and that having then to select an entry in the document types dropdown is not that intuitive. In addition it makes an extra request to the API to show the list of routes even though the user is trying to reach the list of WP or outings.

We need to find a solution. At least 2 possibilities:

• replace the guidebook "home page" by a somehow static page asking "what are you looking for" and showing buttons towards the routes, WP, outings, images, books, ...
• making the later item directly available in the menu (but not as first level entries - even though having "outings" in the main menu would make sense since it's rather a "live conditions" section whereas the routes/WP/books are a kind of knowledge database). A bit like post.ch ?
• ???

The aim is to avoid having to open several pages to find what you want in the guidebook and to make the guidebook structure (WP, routes, outings, ...) more obvious.

[asaunier]

Related to https://github.com/c2corg/v6_ui/issues/244

[fjacon]

@ginold @asaunier where do we stand for this issue ?

[tsauerwein]

replace the guidebook "home page" by a somehow static page asking "what are you looking for" and showing buttons towards the routes, WP, outings, images, books, ...

Yes, I agree that it would be very useful to have a "home page" for the guidebook. Maybe something similar to http://www.outdooractive.com/en/guide/ where you have a list of activities, areas/regions, waypoint types, ... which link to a search for routes, waypoints, ...

And a quick search "I'd like to go climbing/hiking/... in ..." like here would also be nice.

[asaunier]

Some people at the association could not find the way to open the advanced search pages for WP or outings (default is routes) => the current dropdown to choose the document type seems not intuitive enough.

[ginold]

don't forget to have a look at #267

[fjacon]

To be discussed after alpha 3

[stef74]

@asaunier @fjacon can we close ?

[tsauerwein]

I am preparing a proposition on how this "homepage for the guidebook" could look like. I will share something in the next days.

[asaunier]

Anyway I think this issue is still relevant and should not be closed.

[tsauerwein]

Something like this:

[stef74]

:+1:

[asaunier]

That's nice indeed.

About the header:

• would the activity icons be clickable? leading to what?
• how would the "region" input work?

[tsauerwein]

would the activity icons be clickable? leading to what?

The idea is that you can select activities like with the advanced search filter. They probably should rather be gray than orange.

how would the "region" input work?

Either we simply search for areas (like in the user filter preferences), or we do a real geo-coding (like with the search component in the map) and search in a bbox of ~20km around the position.

[asaunier]

Either we simply search for areas

So that would open an area detail view page? Not sure that's really what people want. Or maybe the advanced search page (of outings? routes? WP?) with the bbox of the selected area?

search in a bbox of ~20km around the position.

You mean it would use the geonames service of the map search component? https://github.com/c2corg/v6_ui/blob/master/c2corg_ui/static/js/map/search.js That sounds interesting indeed. Then:

• it should rather be named "places" than "regions"
• the bbox (actually the zoom level of the map recentering) should be the same than when searching a place in the map component (actually same tool)
• then again: outings? routes? WP? I guess "routes" would be more consistent with the "Find a tour" title.
• it could be a bit confusing because it would not work for people looking for a summit or whatever c2corg document (not a geonames place).

[stef74]

Open area page view is not probably and good idea.

By default we can open search on route (most use) on selected area or place (with geoname) ... use the simplest !

if you use geoname solution change the string by "near to" or something like that ...

[tsauerwein]

So that would open an area detail view page? Not sure that's really what people want. Or maybe the advanced search page (of outings? routes? WP?) with the bbox of the selected area?

No, you select activities and an area, and then hit "Go". This will open the advanced search for routes with the made filters.

[asaunier]

Pros of having that kind of "static" guidebook homepage (as the one suggested by @tsauerwein at https://github.com/c2corg/v6_ui/issues/254#issuecomment-254614823):

• we avoid requesting routes to the API (cached?) whenever someone clicks on the "guidebook" menu entry (maybe not interested by routes but by outings)
• the page can be used to give tips about what the document types are (what's a WP? what's an outing?) => to avoid having a bunch of text in the page (people don't read when there's too much text), we could show a small piece of text when users hover the images (a bit like when hovering thumbnails in the v5 homepage http://www.camptocamp.org/)
• we can have shortcuts towards some kind of searches, eg. huts, summits, etc.

[asaunier]

A basic version here: https://github.com/c2corg/v6_ui/pull/857 I need help to go further. @ginold ?

[ginold]

@asaunier you want me to take your branch and finish it? to make it similar to the example of Tobias ?

[asaunier]

Use my branch, @tsauerwein 's or create a new one. Up to you :)

[ginold]

Do we have some images to use in cards for each doctype or should we rather use the default icons ? (like for example on the "not found" page).

[stef74]

To be quick use the same icon

[tsauerwein]

Images would probably be nicer.

[ginold]

@tsauerwein where did you get the photo you used for your mockup?

[tsauerwein]

I used photos from the "Concours Photo": https://www.camptocamp.org/articles/809627/fr/concours-photo-sophie-2016 https://www.camptocamp.org/articles/673796/fr/concours-photo-sophie-2015

[desnoes]

The icon for the WP 'atterissage parapente' is not the correct one. Otherwise, it is ok.

[mgerbaux]

OK for me at this stage; nice work ! (we can discuss later what type of WP should be dispayed after some users' feedbacks) A detail to improve later : words caesura is not correct in the circle when not enough place to display on one line

Take car that forum menu does not hit this page (but probably it is due to the bug on this menu ?)

[celinestern]

@mgerbaux It's only with zoom 100%! Smaller or bigger zoom didn't make this thing!

[stef74]

@celinestern it's depend of your size of screen ... i have this rendering on my laptop not on my desktop

[desnoes]

Unconnected mode: when i click on the button 'topoguide' at the bottom of the page, it does not open the topoguide home page but the previous one. The behavior should be the same wether you click on the topoguide in the left menu or on the button at the bottom.

Same bug when i click on the left menu from the forum.

[asaunier]

@desnoes Good catch! Fixed by https://github.com/c2corg/v6_ui/pull/1352 I have also updated the link in the forum menu template (should be applied by hand in Discourse - except that this problem will probably prevent from doing it https://github.com/c2corg/v6_forum/issues/67)

[Kryst0f]

The top of this guidebook static "home page" is almost empty, with only six icons !

[Kryst0f]

If we will add this "guidebook static home page" including outings, should we still have the outings link on the home page ?

I don't like this "static topo-guide home page" because it's one more clic to get information from the home page (in comparison to the V5). Nevertheless, we should be logical. If we're implementing a topo-guide home page, we should remove the outings links from the home page.

[brunobesson]

@Kryst0f IMHO those comments should no happen on github, but at an earlier step (that doesn't mean it's too late to change anything, only it shouldn't be discussed here). The forums are more appropriate to discuss association-related issues. On github, we focus more on the technical and implementation part.

(and please try not to edit your comments as often)

[asaunier]

@stef74 What's remaining with this issue? Perhaps the styling changes done by @brunobesson ? Since they all have been merged I think, perhaps we can tag this issue as "ready for demo"?

[stef74]

Yes some little improvement are needed in term of content font-size (not very homogeneous ... but not critical)

[stef74]

@asaunier just a little comments ... the police are too "bold"

[asaunier]

just a little comments ... the police are too "bold"

I don't think the SA will make more styling changes. Up to the association to do them.

[desnoes]

The icon for the WP 'atterissage parapente' is still not the correct one. The other bug (access in non-connected mode) is fixed.

[brunobesson]

@desnoes I think it's best to close this issue and open another one for the problem you're mentioning. Do you agree?

[desnoes]

@brunobesson: that's fine for me. I open a new issue

[brunobesson]

All the more because the problem exists for paragliding landing cards too.