WordCamp Organizers: Add a custom taxonomy for teams

[Kau-Boy]

I am part of the WCEU organizing team and as we are currently around 50 organizers, we are split into different groups. We want to show these different groups on the organizers page and therefore need a custom taxonomy as well as a shortcode argument.

I already implemented this new custom taxonomy and we tested it on our staging site. All looks good so far.

I also tried to stick as close to the current code as possible. The new custom taxonomy and shortcode argument should also not create any issues with current WordCamp sites.

It would really help us a lot, if this could be merged in as soon as possible :)

[sonjanyc]

Thanks Bernhard for working on this!
We wanted to extend this functionality so any WordCamp, especially larger ones like WordCamp U.S. and WordCamp Europe, with bigger organizing teams can take advantage of it, and structure the org team page better.

[SergeyBiryukov]

2159.diff​ seems like a good first step to extend this functionality for all WordCamps.

[iandunn]

Hey Bernhard, thanks for the patch. It does look good, but the Community team will need to discuss the idea before the Meta team can implement anything. Check out ​the process for feature requests for more details.

I'm closing the ticket for now, but it can be re-opened and committed if the Community team approves it.

[iandunn]

Re-opening since this was ​approved by the Community team.

[iandunn]

In 4349:

WordCamp Post Types: Add a taxonomy for organizer teams

Fixes #2159
Props Kau-Boy

[iandunn]

I modified it slightly so that it can support multiple teams, so you now call it like:

[organizers teams="foo,bar"] (plural)

[sonjanyc]

Great!! Thanks Ian! Do we need to provide any copy for documentation on how to set this up?

Replying to iandunn:

I modified it slightly so that it can support multiple teams, so you now call it like:

[organizers teams="foo,bar"] (plural)

[Kau-Boy]

Great enhancement @iandunn.

@sonjanyc: I wanted to update the Organizers Handbook after the merge, but it looks like @iandunn was faster :)