The below is a proposed site IA is based on what Mori Sugimoto and I originally proposed. Looking forward to hearing feedback...
Home
-News
-Why you should attend (brief intro linked to full page in Attend/logistics section)
-About DrupalCon (can be brief intro, linked to full page)
Program
- Submit a session call to action
- Sessions listing
- Core conversations and anything else that fits under Program
- Schedule
- Training
- Submit a BoF
- Official parties
Attend (or Logistics?)
- Register call to action
- Venue (Name, address, phone, map, floorplans)
- Travel (getting around, airports, trains etc)
- Accommodation
- Local information (restaurants, tourism)
- Put a badge on your site
- Activities for companions (could also be part of community section or in a Forum)
Speakers
- Featured/keynote speakers (name, session title & photo?)
- List of other speakers (name, session title & photo?)
- (Submit a session call to action could also go here)
- Speaker's responsibilities and other info
Community
- Attendees
- Forum
- Sprints
- Coder Lounge
- Volunteering
- Scholarships
Sponsors (this could be under program)
- Sponsor list
- Individual sponsors
- Become a sponsor
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | Sitemap | Drupal Association Intranet.pdf | 199.19 KB | isabell |
Comments
Comment #1
isabell commentedmaybe this will help the discussion. it is the discussion we had within the London group
Comment #2
justin2pin commentedThis looks great. I think one area that could potentially be improved / simplified is “Attend” / “Logistics”. I wonder if that could be separated into two navigation elements: “Venue” and “Register”. Under “Venue”, it seems likely that one would expect to find information about travel, accommodations, nearby attractions, and other “Place-specific” information. “Register” seems both distinct and important enough to warrant its own space in primary navigation.
I may be making too many assumptions about users’ expectations around “Venue”, though… thoughts?
Also, I think we may want to create distinction between what is navigation and what is content in the next iteration of the sitemap. For example, I wouldn’t expect “News” to be sub-nav under “Home”... I would expect that to be content on the home page.
Comment #3
coltraneAnd what if you're not on the homepage, and want to get news? Is the "news" page only the homepage?
Comment #4
justin2pin commentedBelow is a possible list, based on Ben’s initial post, but omitting sub-nav for each navigation element:
PRIMARY NAVIGATION
Home
Program
Speakers
Venue
Community
Sponsors
Register
SECONDARY NAVIGATION
News
About
Contact
Press
Questions:
Comment #5
lisarex commented1. It's a nice thing to provide a contact link everywhere.
2. Press seems like a good area, but I wonder if an About section would suit Press, News and 'here's how to convince your boss to let you attend'-type info
3. Schedule is pretty specific to What Is Happening When. If that section only contains that sort of info, that's great. A lot of other great conference sites use 'program' e.g. http://confab2011.com/program and http://2011.uxlondon.com/programme/
4. Logistics is a better choice than Venue for content such as travel, hotels etc.
Comment #6
oadaeh commentedAttention getting device:
I think changing things just because we can doesn't make sense. People who are used to attending these events are used to finding certain information in certain locations. If it makes sense to change something because it didn't work well before or because something else works better, then okay, but not just because.
Stinky opinions:
IMO, yes. Don't make important things hard to find.
I think so, and according to London site (which is the only one to have it), they think so, too.
Although "Program" was used for the Copenhagen site, "Conference" was used for the other three sites of the last four conferences. Personally, "Schedule" and "Sessions" are what I look for when I want that information, but the other terms may convey the information better. "Conference" is more broad and encompassing, while "Program" and "Schedule" have more specific meanings. (BTW, I totally missed the large "Conference" labels while looking for "Schedule".)
I do not believe "Venue" adequately covers everything, but if I didn't see words like "Travel", "Accommodations", etc., "Venue" is where I would go, so if they are not going to be broken out, they should be clear sub-sections or areas on the "Venues" area. The Copenhagen and San Francisco sites used "Logistics", while the London and Chicago sites split the information between "Conference" and "London"/"Chicago". While I like the idea of a "Denver" label, I think "Logistics" works better.
In other news:
Regarding news on the front page, while I will concede that some news items are appropriate there, I do not believe that should be the only content or the main content. The front page's purpose should to sell the conference and/or encourage people to dig deeper and get more information about the conference. The river of news should be on a separate page with only the top one or two items occupying only a small part of the front page.
Keeping on track:
Regarding the various session tracks, there are a core 5ish tracks (sometimes one is dropped or two are combined) and usually 1 or 2 that are different for each Drupalcon. I did some research into this for our Las Vegas DUG meetings a couple of months ago. If anyone's interested, I can look for it and post it, but my conclusion can be found here: http://groups.drupal.org/node/150219.
Closing thoughts:
I guess, in a nutshell, what I'm saying is don't reinvent the wheel. Change what makes sense and leave the rest alone. We don't want people feeling frustrated when they use the site.
For reference:
http://london2011.drupal.org/
http://chicago2011.drupal.org/
http://cph2010.drupal.org/
http://sf2010.drupal.org/
Comment #7
justin2pin commented@lisarex: My only concern with "Logistics" is that it doesn't have the same "destination" connotations as venue. It might not matter at all... this is something that would be great to test, though. In general, do you agree with the idea of separating that content from "Register"?
Comment #8
lisarex commentedSure, it would be great to test London and some non-Drupalcon sites. If a couple of us could do some guerilla testing based on 3 tasks, we could then compare notes? Maybe we can take the task writing separate from this issue.
Another approach is to do a card sort, or perhaps better yet, Treejack? We can survey 10 people on 3 tasks for free http://www.optimalworkshop.com/treejack.htm
As for 'Register', I do see it as a totally separate call to action, and the page can be on it's own, not part of another section.
Comment #9
kenwoodworth commentedHi everyone,
The following list represents content to be included on the home page for the DrupalCon Denver website. Items are listed in order of priority, with highest priority given to item 1, second highest to item 2, etc. This list will be used as a guide in the design process for creating an effective layout and design system. Once we have all of the elements and hierarchy established we can jump right into designing the page. So please take a look and let me know if anything is missing or should be higher priority.
Note: Things like logo, search, and navigation are assumed and will not be listed in the content map.
Home
Rotating Feature - This area will feature speakers, training, events, etc
Latest News - This section will pull the latest content from the News section of the site
Important Dates/Times - An area to highlight upcoming or important dates - session submission deadlines, ticket price changes, event details
Audience-specific Content Feature - This section will guide users who might be new to Drupal or DrupalCons. It may feature multiple tracks that could help users learn what to expect or which sessions they may want to attend. Some example audiences could be Business, New to Drupal, Designers, etc.
Sponsors
Join our Mailing List - Mailing List sign-up form
Attendees - A random list of attendee photos
Twitter feed - Recent tweets from @drupalcon or with the drupalcon denver hash tag - Might be universal throughout the site
Comment #10
justin2pin commentedAfter a brief discussion with Lisa Rex this morning, we are moving ahead with the structure from #4. Marking as fixed for now; we can reopen if need be during the feedback cycle after initial designs are produced.
Comment #11
coltraneJust a note that we could continue this thread (or just start a new one) for possible plans for adaptive IA. Adapting the IA as our timeline continues and we pass significant markers, like session submission, etc. There is great overlap here with general "onboarding", and we should consider the use of the forthcoming Onboarding API: http://drupal.org/sandbox/tcarmona/1120194
But, this can all pick up after initial launch.
Comment #12
lisarex commented+1 to #11. Specifically, site visitors have different needs depending on what stage the event is at (if sessions submissions are open, then making it obvious they should be submitting sessions is key; prior to the event, make it easy for them to see/find all sessions, but during, ensure that the schedule broken down by day is default)