Description
Go to the GoPhlGo home page and hover on the "Learn" nav link. The browser status bar says gophillygo.org/learn/
. Click and you land on the Learn page, with the browser address bar reflecting that same URL (gophillygo.org/learn/
). Click browser Back and you return to the home page.
Contrast that to…
Start on the home page and hover on the "Explore" nav link. The browser status bar says gophillygo.org/explore
. Click and you land in Explore mode, but the browser address bar still has the home page URL (gophillygo.org
). Click browser Back and instead of returning to the home page, you return to the page you were on prior to visiting GoPhlGo.
I think we should normalize these behaviors.
Given the single-page nature of our home and map views, I reckon there are implications I'm overlooking, but here's a strawman:
- Establish a new URL at
gophillygo.org/map
. - Whenever the app is in map view, the URL should reflect the above
/map
URL. gophillygo.org/explore
should redirect togophillygo.org/map
with the destination picker set to explore mode (ie, "within").- Browser history should consider visits to
/
and/map
as distinct entries
Thanks @designmatty for bringing this up.