Submit a Session

15 March 2022 – Call for papers opens  
19 April 2022 – End of call for papers (23h59 CET - Prague Time) 
4 May 2022 –  New end of call for papers 
20 May 2022 – Selected session announcement to speakers 
26 May 2022 –  Speakers' confirmation
30 May 2022 – Preliminary Program
15 June 2022 – Conference schedule published/sessions announced to public

DrupalCon’s overall programming is now many conferences in one. The conference you participate in depends on who you are (your "persona") and how your role uses Drupal and the sessions you decide to attend. To see the various tracks please visit this page.

This track segmentation allows and encourages attendees to have a more targeted, well-spent time at DrupalCon, where they focus on topics specifically related to their persona. Attendees will also have many opportunities to come together in keynotes, social events, and the hallway track for cross-pollination, community building, and collaboration, which remain core benefits of attending DrupalCon.

When submitting your session, please don't neglect to select a tag/tags to assist with categorizing the content of your proposal. Acquaint yourself with the submission tags before beginning your submission.

Although submissions will be accepted for all tracks above, please submit a proposal to the track that will foster the most meaningful engagement for you and your audience. For example, a session about Drupal 9's Database Schema might not be very meaningful for the Agency + Business audience.

You can also download the slides (coming soon) and use it to spread the word about this year's theme.

• Sessions (20 minutes or 45 minutes)
• Panel discussions (45 minutes)
• Workshops (45 minutes or 2x45 minutes)
 

Please review the track descriptions and our list of topic areas, tags, to decide which topics you'd like to share your knowledge on.

You are free to submit a session to any track, but, obviously, you have a much better chance of your session being accepted if it is in a track relevant to the session's main topic.

We may consult with you to move your session from one track to another.

Speaking at a DrupalCon is considered a voluntary contribution to the Drupal project.

Although we do not financially compensate speakers for preparing a session submission or presenting a session, we are happy to offer one DrupalCon ticket per selected session. Note: if you are co-presenting with someone else, your session will still receive only one ticket, not two.

Speakers pay their own travel and lodging expenses incurred while traveling to and attending the conference.

We will do our very best to support you as a speaker. To this end, we offer:

• Pre-submission mentoring - We know submitting a conference proposal can be intimidating, especially for newer speakers. To help you become a speaker, we encourage you to use the HelpMeAbstract to obtain feedback from veteran open source speakers.
• Contact with the Selection Team - We encourage you to reach out to your Program Team. You can ask for their feedback on a part of your submission; ask a specific question about what they are looking for; ask about end goals of your session; etc. Please feel free to join #session-help on slack to get tips and request session proposal feedback from DrupalCon team members.
• First-Time Speaker Resources - Speaking at DrupalCon for the first time is exciting and fun, but it may come with some nerves. We will ask if this is your first time presenting at DrupalCon when you submit your session, and if it is, we’d like to support you by offering additional speaking resources, video calls with past speakers and trainers, and an open line of communication to ensure you feel comfortable and have a great session.
• Support during the conference in the form of quiet spaces and networking with other speakers

Before submitting a session, we recommend that you read the following information:

• Familiarize yourself with the conference Code of Conduct. All speakers will be required to adhere to this code.
• Read and agree to our Speaker Agreement.