Wed 10:45am to 11:30am (7/19/23)

We have all heard this from a client: “I have a small marketing website and I want it in English too.” It sounds simple, and it can be, but do not make the error to think “it is just a copy of each page, add the language switcher and voila, we’re done!” In this talk we will dive into the technology decisions we have made, and committed to the Drupal community, in order to answer the question "How can translations of our content for our (Drupal 10-based) website relaunch, also using the layout builder, be managed?" In this case study we used our company's website. We had to take our Drupal stack into consideration. It is based upon Lupus Decoupled, a fully integrated solution for a headless Drupal which builds upon Custom Elements and Lupus Custom Elements Renderer. On top of that we also use a custom solution that turns our backend into a contentpool that delivers content to multiple frontends. That was our starting point on top of which we added a multilingual functionality layer. Drupal Core gives us many tools to start with, but to make it manageable, we had to make some decisions. When an entity exists in one language and then it is translated, all the layout builder blocks are cloned and attached to the new translation. How should the system manage an added block of text? The language switcher must also be designed. There are accessibility guidelines and decisions to make about how the language switcher works when a translation is not available. The list goes on. We will highlight the overall strategy that we have developed, as well as go into some of the finer points of the code.

In this session we will discuss the much awaited feature automatic updates. We ll also discuss how you can set up automatic updates for your site to make maintenance for drupal sites easy. Attendees will be able to take away the following from this session: - Setting up Automatic updates for your local site and on the server. - How we can ensure our site is ready for automatic updates. - Customizing the update process. - Caveats and limitations of automatic updates.

There are certain javascript-based interactive components that we front-end developers build over, and over, and over, and over again. What's more, we often adhere rigidly to the requirements of the current project when we do so meaning that the end products are not easy to re-use. The end result is a lot of javascript-based components that are buggy, inaccessible, and outdated. Well, we can do better. This session outlines and demonstrates a general approach to building small interactive components with progressive-enhancement, re-use, customisation, and responsiveness in mind.