Timeline for deleting parts of the url to get to the page above
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 27, 2015 at 17:29 | comment | added | Devin | Then you might also need to re-think the site organization. Anyways, the idea is that you send people to a default (let's call it "hub") page, and then you "train" the user to follow your flow, not to wander freely across your site. Also, if the user is savvy enough to go to /events/ , they're savvy enough to expect an index, not a "per event" detail page | |
| Apr 26, 2015 at 17:28 | comment | added | fxck |
"just use htacces to redirect", no, this wouldn't help. The whole problem is, that those two urls could be conflicting. Imagine two routes /events/:list-event-type and /events/:name-of-detail-event, when user hits /events/past-events, there's no way for the router to recognize that this is supposed to go to list of all past events, rather than detail of event called "Past events".
|
|
| Apr 25, 2015 at 16:12 | history | edited | Devin | CC BY-SA 3.0 |
minor edit
|
| Apr 24, 2015 at 20:57 | history | answered | Devin | CC BY-SA 3.0 |