You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be really useful to have an (optional) "tour icon" for each tour, so that they can be easily distinguished. We could put the icon (slightly larger) at the start of the tour, then keep it in the tour stops on the top right of the tour menubar, which would give good visual feedback for visitors.
I'm quite keen to not allow photos, but insist upon icons, and probably impose this by only supporting SVG files (https://www.phylopic.org provides lots of good "silhouette" type ones that are public domain and could be modified, e.g. below for the frogs tour)
If we do allow an SVG icon, we could, I suppose, store the SVG in the database, which I would find neater than having to upload an image.
The text was updated successfully, but these errors were encountered:
I like this idea a lot but don't think it's part of the "paradoxical frog" release.
I agree. However, if we do all think it is a good idea (and we can store the icons in the DB) then maybe we could make a DB field for them in the tours database, alongside the image_url one.
I think it would be really useful to have an (optional) "tour icon" for each tour, so that they can be easily distinguished. We could put the icon (slightly larger) at the start of the tour, then keep it in the tour stops on the top right of the tour menubar, which would give good visual feedback for visitors.
I'm quite keen to not allow photos, but insist upon icons, and probably impose this by only supporting SVG files (https://www.phylopic.org provides lots of good "silhouette" type ones that are public domain and could be modified, e.g. below for the frogs tour)
If we do allow an SVG icon, we could, I suppose, store the SVG in the database, which I would find neater than having to upload an image.
The text was updated successfully, but these errors were encountered: