Feature Request: Give WordCamp attendees ability to mark/save sessions of interest on camp schdeule

Attending WordCamp is great, but as an attendee I have to repeatedly refer to the schedule to see which talks I wanted to go to next and which room I should be in, etc. I’d like to suggest a new feature to enable users to create a custom track from a published schedule on a WordCamp website. A way for users to select their desired session and somehow save this “custom” track or collection of sessions.

What does saving mean?

I think the MVP would be save and print or email the custom schedule/agenda. The user would select one talk (maybe more? if they’re interested in multiple sessions) per time slot to attend by clicking that slot in the schedule, and visually the schedule would highlight marked sessions. Perhaps selecting a session would even create a new list of sessions as that attendees custom agenda for the Camp and that agenda can be printed. I’m sure proper UX would deem it necessary to include some type of buttons or interface to add a session to an agenda and then to remove selected sessions too. As MVP, this could be front-end only and not even save any data. It could populate an email or be ready to print – or even simply allow users to keep the page open on their phone for quick glances during the conference.  I especially see this agenda layout being useful on mobile, where it’s tough to fit a complex schedule.

For a nicer experience though, the site would save the user’s selections and allow them to return to the schedule to see their saved/selected sessions. Ideally this would be tied to their .org account or something so either on the computer or phone they could log in and view their saved agenda.

How could it be useful to more than just the attendee?

Then if we end up being able to save this data, why not allow users to opt-in to share their schedule with other attendees or even the public. Attendees and sessions are displayed, let’s connect them. Each session abstract could indicate interest either by how many attendees have selected this talk or even list all interested attendees. I could see this being useful information to gauge general interest for talks and may help ensure to have ample space for each session. For example, if one session has a high level of interest it could be moved to a larger room to account for more attendees. Anyways, I digress…

Here I’ve mocked up a quick and ugly schedule with some marked sessions:

wordcamp raleigh schedule with marked sessions

Here’s a nasty screenshot of a schedule for WordCamp Raleigh with sessions marked as proposed. Notice there are two sessions saved at 11am, while only one session for later times.

The main point here is to have a way that when viewing the WordCamp schedule, attendees can select which sessions they are most interested in to create their own agenda during a WordCamp, and then a convenient way for users to save this agenda for quick reference during WordCamp. Sharing this interest may help attendees network and connect with others before and during the event. This data could possibly provide general feedback to organizers for planning purposes too.

I don’t believe this is the first time this type of idea has come up and I’ve had positive feedback from others and hope this can generate a useful discussion and roadmap. Thoughts?

#improving-wordcamp-org, #wordcamp-org, #wordcamps #feature-request

WordCamp Central Admin Maintenance

We’re planning on rolling out some possibly breaking changes to the WordCamp Central admin on Tuesday, April 5th between 16:00 and 17:00 UTC. During that time, the Central admin will not be accessible by deputies and WordCamp organizers. Other parts of the WordCamp.org network should not be affected.

We apologize for any inconvenience and we’ll post more information about what has changed after the rollout is complete. As usual, we’re available in the #meta-wordcamp and #events channels on Slack.

#wordcamp-org, #wordcamps

WordCamp.org URL Migration Status

The URL structure for all WordCamp.org sites has been migrated to the newest year.city.wordcamp.org format, all the redirects are in place, and all the SSL certificates stuff has been taken care of.

All new event sites created in the network should now use the new structure, and the deputies handbook has been updated to reflect this change. Please note that SSL certificates for new domains are issued only twice daily. This means that after creating a new site in the network, you’ll have to wait up to 12 hours before it gets a valid certificate. Previously issued certificates auto-renew every 60 days unless the site has been deleted.

If you have any questions or come across any issues that might be related to this change, please feel free to leave a comment or ping us in #events or #meta-wordcamp on Slack.

#wordcamp-org, #wordcamps

We’ve recently deployed our WordCamp org + Let’s…

We’ve recently deployed our WordCamp.org + Let’s Encrypt integration and it looks good so far. This means that all newly created WordCamp.org sites will get a valid SSL certificate within 12 hours after creation, and all SSL certificates will be renewed every 60 days.

We already spotted some SSL-related errors and fixed them in the past few hours, but if you come across anything strange that may be HTTPS related, let us know on Slack. We’ll be transitioning the rest of the network that is still using the city.wordcamp.org/year structure to year.city.wordcamp.org in the coming weeks. I’ll post an additional update about that when it’s done.

P.S. If you’re ever in the WordCamp.org SupportPress instance, we’re expecting a flood of e-mails from staging-expiry@letsencrypt.org or expiry@letsencrypt.org so don’t go crazy if you see one. Keep calm and ping @kovshenin on Slack and we’ll sort it out with some new filters.

#wordcamp-org, #wordcamps

Just a quick note on the WordCamp org…

Just a quick note on the WordCamp.org site creation flow for deputies. We’re still working on our new SSL setup and URL format change. Some cities have been migrated to the newest year.city.wordcamp.org URL structure, while most cities are still on city.wordcamp.org/year.

To work correctly, the newly created sites should follow the previous year’s structure, so if you’re creating a new 2016 WordCamp site for City:

  • If the last year’s site is on 2015.city.wordcamp.org, the new site should be created as 2016.city.wordcamp.org
  • If the last year’s site is on city.wordcamp.org/2015, the new site should be created as city.wordcamp.org/2016

In the future (hopefully very soon) all sites will be on year.city domains and this will no longer be a problem. Sorry for the inconvenience and thank you for your patience. If you have any questions feel free to ping @kovshenin on Slack or leave a comment.

#wordcamp-org, #wordcamps

WordCamp URLs

This has been discussed many times in several threads and IRL conversations over the past few months, and as many of you heard, a decision has been made. We’re currently in the middle of changing the WordCamp URL structures back to year.city.wordcamp.org from city.wordcamp.org/year. If you’ve noticed broken images, styles, insecure content warnings, invalid SSL certificate warnings, broken redirects or anything odd, please let us know here or via support@wordcamp.org.

Thank you for your patience!

#wordcamp-org, #wordcamps

After reading this post about adding random wapuus…

After reading this post about adding random wapuus as default avatars, I would like to suggest to add the mentioned plugin on wordcamp.org.

Do you like this idea? Want to see all the wapuus on the attendee list instead of the boring grey person? 🙂

#wapuu, #wordcamp-org, #wordcamps

Remote CSS Plugin Launched on WordCamp.org

The Remote CSS tool is now available on WordCamp.org. It’s one of the ideas that came out of last year’s Community Summit, and it allows WordCamp.org site developers to work with whatever tools they want, instead of Jetpack’s CSS editor.


What You Can Do

For instance, you can:

  • Work in a local development environment, like Varying Vagrant Vagrants.
  • Use your favorite IDE or text-editor, like PhpStorm or Sublime Text.
  • Use SASS or LESS instead of vanilla CSS.
  • Use tools like Grunt to automate your workflow.
  • Manage your CSS in a version control system like Git.
  • Collaborate with others on a social coding platform like GitHub.

You can use all of those tools, only some of them, or completely different ones. It’s up to you how you choose to work.

How It Works

Remote CSS works by downloading your CSS file from a remote server (like GitHub.com), sanitizing it to remove security threats, minifying it, and then storing a local copy on WordCamp.org. The local copy is then enqueued as a stylesheet, either in addition to your theme’s stylesheet, or as a replacement for it. The local copy of the CSS is synchronized with the remote file whenever you press the Update button, and you can also setup webhook notifications for automatic synchronization when the remote file changes.

Because of security concerns, it can only support specific hosting platforms, but it currently supports GitHub, and we can add others if there’s interest. If you want to use Beanstalk, Bitbucket, CodeForge, or something else, let me know.

Contextual Help

The plugin also contains detailed setup instructions inside wp-admin; just open the Help tab.


It plays nicely with Jetpack, so you can test it out today without losing any of your current CSS.

If you’re looking for something simpler, though, Jetpack’s CSS Editor is still a great option.

If you have any feedback or ideas to improve it, please leave a comment. If you’d like to check out the source code, it’s available in the Meta repository.

#git, #improving-wordcamp-org, #jetpack-css-editor, #official-websites, #wordcamp-org

Sponsor Info

Someone wanted information about sponsoring WCs so I went to central.wordcamp.org to look for it for them.

  • I went to https://central.wordcamp.org/global-community-sponsors/ because it was near the top of the list and bc I know that’s the current program. It lists the current sponsors but has no information on what the levels mean or how to become one.
  • Then I went to https://central.wordcamp.org/sponsor-multiple-wordcamps/, listed lower in the subnav. This is the old program, and links to the 2014 packages.

This is bad IA/content to have there. I’d like to suggest a change:

  • Make Sponsor a top level nav item.
  • First item should be Sponsor a WordCamp, a page that doesn’t exist yet. It should say how great WCs are, how they’re all run by volunteers, how we depend on the kindness of strangers money of helpful businesses to keep the events going, and outline the difference between sponsoring an individual WC and joining the global program. Should link to other subpages showing current sponsors, global program rates/benefits, the upcoming WCs schedule (for people interested in sponsoring a single WC), and an application form to become a global sponsor.
  • Change the Global page label to Current Global Sponsors.
  • Remove the 2014 rate sheet that is linked from the multi-event page. Create a current rate sheet (as a page, not a pdf) and update once a year. Each year, post the upcoming year’s rates as well by September so businesses can plan for the coming year.
  • Remove multi-event page since it’s not the current program.
  • Create the page with a sponsorship application form for those interested in global sponsorship.

Any objections to this update?

(Where is the 2015 global sponsorship plan info?)

#official-websites, #sponsorship, #wordcamp-org

Update on building a new WordCamp theme

This is a follow up to the @iandunn post on the WordCamp.org tools survey results.

I setup a Github repo for the new WordCamp theme with a fork of Underscores to get things started.

To start with I have been collecting feedback and ideas for a new WordCamp theme so that our design lead, @robertnienhuis, has something to work with. I haven’t gotten too much feedback online yet, but have gotten some good ideas from several other organizers offline. If you would like to share some feedback as well please post a comment below!

Theme Features

Here is the feedback that I have collected so far, as well as my own ideas:

  • Great Design: I would like to keep the theme light and minimalist, easy to build on, but also have it look good enough out of the box for a WordCamp without a strong designer to be able to use as-is.
  • Mobile First: I’d really like to include a strong mobile version that makes WordCamp sites easy to use at the event when you are on the go.
  • Widgetized: It’s always tough to get markup where you want it, I’d love a lot of widgetized areas so I can get the content I need in the right spot to match any design. I spoke with some other organizers who would also like more widgetized areas, sitewide and page specific. Particularly for the featured content sections typically found on a WordCamp site.
  • Widgets: Building actual widgets into the theme might be a step too far, but there was some interest in having a few featured widget styles built in, so that if you used the right markup in a text widget you could get a good looking featured section right out of the box that organizers can expand on from there.
  • Page Templates: Most of the people I talked to were interested in having more page templates to choose from. Like a homepage template with a page content area and multiple widget areas for featured content and also a similar homepage template with a smaller blog area setup as recent posts with excerpts. We’ll need a single column page template of course, but I’d also like to try to include a more minimalist template with little or no header or footer as well that people can use for whatever they want as a blank canvas.
  • 404 Template: I’d like to include a pretty minimalist template for this too that includes a widget area just for the 404 page, so that people can create a nice custom 404 page if they want to.

Website Examples

I also have a few examples of WordCamp sites that I like, please share your favorites in the comments!

  • WordCamp Minneapolis: Westwerk did an awesome job designing this site and if we can do half as good I’d be thrilled!
  • WordCamp Montreal: They had a sharp looking site this year, I really like the call to action block on the homepage below the header with the tickets/schedule spot, and the subscribe/ social media spot.
  • WordCamp Denver: A nice clean site, great for mobile, with a sweet camping vibe.

I’m pinging people that volunteered to help out in the previous post: @cheffheid, @valeriosza, @dnelle, @danielgcarvalho, @brettshumaker, @davidjlaietta

#improving-wordcamp-org, #official-websites, #themes, #wordcamp-org