For my DrupalCon Amsterdam keynote, I want to try something slightly different. Instead of coming up with the talk track myself, I want to "crowdsource" it. In other words, I want the wider Drupal community to have direct input on the content of the keynote. I feel this will provide a great opportunity to surface questions and ideas from the people who make Drupal what it is.

In the past, I've done traditional surveys to get input for my keynote and I've also done keynotes that were Q&A from beginning to end. This time, I'd like to try something in between.

I'd love your help to identify the topics of interests (e.g. scaling our community, future of the web, information about Drupal's competitors, "headless" Drupal, the Drupal Association, the business of Open Source, sustaining core development, etc). You can make your suggestions in the comments of this blog post or on Twitter (tag them with @Dries and #driesnote). I'll handpick some topics from all the suggestions, largely based on popularity but also based on how important and meaty I think the topic is.

Then, in the lead-up to the event, I'll create discussion opportunities on some or all of the topics so we can dive deeper on them together, and surface various opinions and ideas. The result of those deeper conversations will form the basis of my DrupalCon Amsterdam keynote.

So what would you like me to talk about? Suggest your topics in the comments of this blog post or on Twitter by tagging your suggestions with #driesnote and/or @Dries. Thank you!


Torrey T (not verified):

Are there any disadvantages from trying to AJAXify a lot of the Drupal processes? Is this something that may be integrated by default in the near future?

Pavithra Raman (not verified):

With everything going mobile, a lot of businesses do not care much for the website or a web based app. How important is Headless Drupal in this context ? Drupal will be central to storing the business logic and content centrally, which can then distribute the content and functionality via any medium that the end user chooses. How does Headless Drupal reduce the effort on development across these multiple channels.
Android apps, Windows apps, iPhone, iPod, Mac apps, Smart TV, Smart Watchs, Google search and many much more to come.