Back in the D6 COD release, it was suggested that schedule, sessions, bofs, etc all exist under the program url structure as follows:

mysite/program/sessions/accepted
mysite/program/schedule
mysite/program/schedule/mine
.... etc

Due to a limitation in path auto, this doesn't work very well with basic pages as program items. We could have a view or panel on the program page that links to a basic page, but after talking to some stakeholders, they suggested they'd rather not see program in the url at all. IE:

mysite/event/program
mysite/event/sessions
mysite/event/schedule
mysite/event/schedule/mine

Comments? I think for drupalcon we're going to move this route. Its more intuitive than the existing UX propose it seems.

Comments

stephelhajj’s picture

For DrupalCon, our urls are very clean, setup as domain/[node] for the most part. The only times we force hierarchy are instances where we want to be able to make intentional separation of content (ie Schedule, Training, and Sessions), but that's as deep as we go.

For example:
domain/schedule/monday
domain/training/bob-the-builder-construction-101
domain/session/shelf-building-101

I think a lot of websites have moved to this more clean, intuitive url method (twitter got rid of the twitter.com/u/name and replaced it with twitter.com/user, for example).

Since I'm not excellent at writing up my reasoning, I'll let others who are better at words do it for me: http://derivadow.com/2010/02/18/the-problem-with-breadcrumb-trails/

TL;DR Tim Berners-Lee says don't use forced url hierarchy

mrconnerton’s picture

I am a big fan of this. For DCAVL I set paths to node/%/whatever and used the subpathauto to translate that into /event/whatever.

+1 is my vote.

japerry’s picture

Great. we use subpathauto already, and that was another hickup, we had to set it to FIVE in order for the sessions/proposed view to work correctly.

This will greatly simplify things and should speed up load times.