Schedule

With the help of the Custom Elements module you can decouple your frontend, while keeping Drupal's features like full page caching, layout builder or editorial controlled path aliases! The module enables you to render your site's content into custom elements and to turn Drupal into an API backend for a component-based, decoupled frontend.

Session content The challenge with large static sites involves efficient generation of a large number of pages as well as providing an agile experience for content editors. This session will be an inside look at our solution for decoupling XXL sites overcoming JSON:API limitations for efficient Drupal data extraction and creating an instant editing experience.

If you are hosting any Drupal sites on Kubernetes or are in the process of moving to a Kubernetes cluster infrastructure, this session is for you. As most of us have experienced already, debugging production Kubernetes clusters running Drupal can be a tremendously complex task leading to unplanned downtime, overhead and toil. What is Distributed Tracing and why do we need it?

Putting trust at the core of your communications will help build better connections, better businesses, and better communities. “Whatever matters to human beings, trust is the atmosphere in which it thrives.” - Sissela Bok, philosopher and ethicist

Everyone who uses Drupal believes in the concept of “Open.” But for marketers, Open doesn’t just mean open-source -- it means so much more.

Drupal allows building highly complex content structures ranging from simple blogs to online stores to advanced enterprise publishing with complex content approval workflows. Migrating content into such complex structures is a complex problem for which Drupal provides a simple framework in the form of the migrate module.

The TL;DR is that sketching is a fast way to communicate intentions clearly, iteratively, and collaboratively, and is crucial in my lean discovery and UX processes. Let me show you what works for me. ________________________________________________________________________________

There are two types of people – those who suffer from the Impostor syndrome and those who never heard of it. Of course, there are some exceptions, but they only prove that Impostor syndrome is a significant topic, and its effects are more intense than considered.

Personalization: Go or No? In the era of consent, privacy and GDPR it may no longer seem acceptable to do behavioral personalization.

The session will cover the importance of local communities in promotion and development of Drupal. We will find out why leading or supporting domestic group has at least the same impact as direct code/documentation contribution. We will also have a look at vital hints for starting or reviving the community in your own city.

Selling 60.000 festival tickets within a few hours isn't that big of a deal anymore. It does get more challenging when you also want to sell products from different vendors within the same transaction. Next to that, our client also demanded to go serverless, challenge accepted! Are you interested in finding out what you can do with AWS Step Functions? This is for you!

A session to introduce Open Data challenge for governments, and focus on how Drupal is used in multiples French governmental entities to deploy Open Data portals, with advanced data visualisations interfaces.

Drupal 8 comes with a whole new caching system which is designed to allow caching of as much of a page as possible. In this session we'll look at making the most of this for your pages which contain a mix of cacheable and not-so-cacheable content.

The way we build CMS systems has changed: Today we build frontends independently from backends. Because the frontend can easily be changed, the editorial experience in the backend has become an important differentiation criterion for choosing the right CMS system.

Join us on this panel to discuss with project maintainers, users, business owners and other actors in the open source community what's the future of open source, the challenges we are facing in our different roles, and what can we all do to make the whole ecosystem fair and future proofed. As discussed, three simple questions:

The Drupal agency landscape is always changing. And for many Drupal agencies in a post COVID-19 world, the terrain has become rough—and in some cases, inhospitable. Let's look at what data we have on the state of Drupal business at agencies today, listen in to the perspectives of Agency Leaders, and explore new ways of being better, together.

Some say the only certainties in life are death and taxes. We face uncertainty in the world every day: how clients will react to budget constraints and deadlines, how employees will deliver the end product, and where the next contract is coming from are uncertainties I regularly face. It is possible to commit no mistakes and still lose, because there is always uncertainty.

There is a huge demand on developers and software engineers while companies everywhere are struggling to cover the demand for them. That may sound like good news for us as developers and people working on the IT industry, but there are some dangerous details hidden on apparently those good news.

How will advances in technology change the way that we deliver and build digital experiences in the future? How can we, as technology providers, influence the digital experience of consumers across multiple touch points, without juggling several tools and creating a tech stack that limits our ability to scale?

QA is not simply a profession. It's a state of mind. Are you a fan of the "Money Heist" series? Well, there we have a great technical QA engineer who identifies the bugs by looking at the documentation/architecture and at the end provides steps to reproduce for the biggest exploit ever.

The ideal environment is one where you feel included, supported and heard. How can a company strive to provide that environment for every member, regardless of status or position? Besides the social responsibility, what are the advantages to a company or organisation in fostering an open culture?

"There is a module for that" is an old saying when you're looking for a solution to a problem that probably occurred to someone else. So you go to drupal.org, search for relevant keywords, and (hopefully) find a solution - and not "reinvent the wheel"

Last year in Amsterdam we confirmed that everyone had their own favorite Drupal Development Tool. Is the same happening this year? Are we on the way to standardizing on top of something more uniform? https://drupal.kuoni-congress.info/2019/program/abstract/321