Add Session Tags and Classes to WordCamp Schedule

[dustyf]

I'd like to have more control over styling WordCamp Schedules and separating out different types of sessions. The current method only allows for tracks.

Not every WordCamp has sessions in specific topic-based tracks. For instance, at WordCamp Milwaukee 2013 we named the rooms more randomly and did not have only one topic on one room. A Development talk may be in room 1 the first hour then in room 3 the seond, etc.

I still wanted to have the ability to put some type of mark to show the topic of each talk (in this case with background image icons). I managed to accomplish this by adding the topic at the end of the slug, then doing some fancy CSS Selectors. I feel this could be made much easier, but just adding tags to go along with the Tracks and by also adding some other classes to the <td> that holds the session within the schedule.

Attached is a diff of wc-post-types.php which includes this change.

• Added a new taxonomy called wc_session_tag
• Added this tax as a class
• Added the speaker name as a class
• Added the track name as a class
• Added the title of the session as a class

These classes could also be added to the sessions page too, but that is another ticket I can add later.

[dustyf]

Patch file for wc-post-types.php with necessary changes

[iandunn]

In 483:

Post Types: Add extra CSS classes to schedule shortcode.

props dustyf.
see #355.

[iandunn]

Adding the extra classes is a great idea. I went ahead and committed that.

I'm open to adding the new taxonomy too, but would like to discuss it a bit first. It sounds like the use case for that is a situation where the sessions are assigned to a track, but the room assignments don't necessarily match the track.

If that's the only use case, I'm wondering if it'd be better to use the new CSS classes to do something like this:

.speaker-name1,
.speaker-name2 {
   background-image: url( developer.png );
}

.speaker-name3,
.speaker-name4 {
   background-image: url( blogger.png );
}

Granted, that'd be a bit more cruft in the stylesheet, but it'd be less in the UI. Since most camps still assign rooms based on tracks, I think that might be a better option.

Or maybe we should label the new taxonomy "Room" or "Location". We might want to start collecting that data anyway for the GSoC WordCamp app, and it'd be a more structured way to do it than a generic tag. We'd then need to add a parameter to the schedule shortcode to build the table based on the room instead of the track.

[iandunn]

Closing since there hasn't been any activity here in years, but it can be re-opened if people are interested.