The Drupal Event Platform (DEP) committee within the Drupal Event Organizers Working Group (EOWG) is working to reduce the time and resources it takes to create an event website site through the creation of a flexible and customizable website starter kit for event organizers. In this post, we'll update you on our massive 1.0 stable release. Check out our latest demo video too.

In its current form, the Event Platform is a collection of modules:

• event_platform

  • Installs all the submodules, except event_platform_olivero. Provides no code or configuration of its own

• event_platform_details

  • Creates a config_page entity to store details about the event, such as name, year, description, and so on. It also provides two custom blocks that leverage data from the config_page: a CTA block intended for the header, and a copyright block intended for the footer

• event_platform_job_listings

  • Creates a content type for job listings and a view to display them. By design the job listings are associated with sponsors (so this module depends on event_platform_sponsors) and job listings are displayed according to the level of sponsor that posted them

• event_platform_olivero

  • Installs all the other submodules, and places the blocks into the intended regions of the Olivero theme

• event_platform_scheduler

  • Provides a dedicated scheduler interface for drag-and-drop assignment of sessions (and potentially other content types) to rooms and time slots. Filters can be added to help organize sessions based on common audience, category, and so on. This module also provides a tool to quickly bulk generate time slots for scheduling

• event_platform_sessions

  • Creates a content type for sessions and a variety of taxonomy vocabularies and views to help manage them. Also creates Speaker and Session Moderator roles. Using the Registration Role module, the Speaker role is automatically assigned to new registrants. Workbench Email templates use tokens to send out emails whenever sessions are submitted, accepted, or rejected.

• event_platform_speakers

  • Creates a content type for featured speakers and a view to display them

• event_platform_sponsors

  • Creates a content type for sponsors and a view to display them, grouped by sponsor level (platinum, gold, etc)

Heard enough? Want to get started?

An event organizing team can use the Event Platform in at least three different ways:

1. With a fresh install of Drupal, they can install the event_platform_olivero submodule to install all the submodules and place the available blocks in the intended places

2. If using a custom theme, they can install the main module to activate all submodules but not place any blocks

3. If they only want to use some of the capabilities provided by the Event Platform, they can selectively install one or more submodules

Further instructions for getting started, managing sessions, creating schedules, and more are in the Event Platform User Guide.

Future Considerations

• The long term vision for the Event Platform is for it to be a set of recipes, potentially with some associated contrib modules. As an interim step, we are considering using Features to help with maintenance

• Drupal camps and conferences commonly have an ability to flag sessions, and then view these flagged sessions in a “My Schedule” view. A similar capability could be provided as a submodule

• Many camps also have Birds-of-a-Feather or BOF sessions, meant to encourage peer-to-peer discussion. A new submodule could simplify adding these for camps that want to include this type of session

• Eventually Workbench Email may be replaced by the ECA and Easy Email modules, to allow for more sophisticated, custom logic around when and how emails should be sent. This could also include sending an email once a session is scheduled, to ask the session author to confirm they can present at the chosen time

• Commonly camps run over several years (hopefully indefinitely!) but don’t want to rebuild or reset their site every year. The plan is to provide an Event entity, so that each year the camp could create a new entity, effectively resetting the site, while potentially still allowing content from previous years to be accessed

Get involved

• Check for updates on the initiative page.
• Install the project and dive into the issue queue.
• Join #event-organizers on Drupal Slack.
• If your event ends up using the Event Platform, let us know.

The EOWG would like to thank Martin Anderson-Clutz (mandclu) for his incredible commitment to moving this project forward.

Welcome to the future of web development, where Artificial Intelligence (AI) is changing the game in ways we could never have imagined. AI presents web developers with a host of exciting opportunities, from enhanced user experiences to more efficient development processes. 
How do you like the previous paragraph? It was written with AI. Is that impressive? Let's talk about the role of AI and web development today. Are you wondering if AI will be able to replace programmers shortly? Read our new blog today for the latest news on machine learning, artificial Intelligence, and website development.

Drupal and Artificial Intelligence have now come together to create a powerful and irreversible impact on the world of Drupal services. From generating content ideas to translating content to optimizing its quality, AI has slithered into almost all spheres of Drupal services. This is something Drupal developers have been eagerly waiting for long. Now that their wait has finally been over, they are doing wonders by leveraging the power of AI for rendering futuristic Drupal development services.

In this blog, we’ll take a plunge into how AI has revolutionized Drupal services for good.

Moving Beyond the Basic Chatbot With ChatGPT Integration

The integration of Drupal Chatbot with ChatGPT came as a huge surprise for Drupal developers across the globe. ChatGPT is a fabulous AI chatbot. It was developed by OpenAI. Its release in November 2022 caused a widespread sensation worldwide. Around 1 million people signed up to try it out within the first five days.

Performing behavioural testing on a Drupal project allows you to make sure that all of your features work as they should do. This is especially important when you update code as this can introduce bugs that are otherwise time consuming or difficult to spot.

One aspect that is important to behavioural tests is the content of the site, which is often integral to many Drupal sites functioning correctly. Many Drupal sites have taxonomy terms that are used in views to filter content in one way or another.

There are also structure pages that are used as signposts to other parts of the site, and they are often important in navigation. Whilst you could just visit the pages directly, it's often useful to test the user journey end-to-end, which involves being able to navigate to the functionality being tested.

One approach to ensuring the site contains content is to copy the production database into the testing environment. Using the production database for testing has several disadvantages, not least of which is the complexity of copying the data across in the first place. Some production databases are very large and so importing this into the test environment can cause tests to take many hours to complete.

The biggest problem, though, is making sure that your development site doesn't contain any personal information as this is a security concern and can even cause problems like sending test emails to users. Whilst there are ways around this, teams can often spend quite a lot of time ensuring that there is no personally identifiable information at rest in your test environment.

A better approach to this is to use default content to create a Drupal site so that is in a known state before tests are run. This means that the site will function in the same way as the production site, just without all of the personal information. The idea behind this approach is that you create a known test environment for tests to run.

Read more

At DXPR, we're always looking to learn more about Drupal, especially when it comes to how different languages are handled on the platform. We're starting a project to study this and we're inviting people with experience in this area to help us.

We've set up a 30-minute interview for Drupal practitioners who've had their hands on the ropes in setting up multilingual CMS or doing content translation. These conversations will add a lot to our study and they'll also help us all understand these important areas better.

The best part? If you take part in this, you'll get early access to DXPR's latest developments. Our team has been working hard to make improvements to the translation experience for Drupal content editors and translators. By being part of this project, you'll be among the first to check out these cool new features.

Interested in being part of this study? Reach out to us to set up an interview at a time that works best for you! Please also write a short introduction about your experience and/or ambitions with respect to web content translation.

Host Matt Kleve discusses a recent Lullabot Drupal project and its transformative impact on government websites. In this episode, we have an exciting conversation with a representative from the Office of the CIO from the state of Iowa and the Director of Strategy at Lullabot, as we explore the importance of structured content and its role in the groundbreaking work being done on Iowa.gov, powered by Drupal.

When you think of the most powerful tools in Drupal, it should come as no surprise that Views are always at the top of the list. Built into the Drupal core since 8.0.0, Views, together with their companion module Views UI, enable website administrators, site builders, and developers to display content listings on their websites in any format they need. 

My projects all use DDEV for local development. Regarding end-to-end testing, as part of my continuous integration process, I also use DDEV! This way, my scripts for running Cypress are the same locally and in my CI. Leveraging DDEV in your CI is especially useful if your project has multiple domains, which is harder to replicate using good old php -S 127.0.0.1:8080 -t web. Recently I wanted to speed up my end-to-end tests by avoiding full site installs for each job. A full site install could take a few minutes with the default content creation. But I knew a database restore could take a fraction of that time. Luckily, DDEV provides snapshots that can be used to restore your environment from a backup!

The approach was this: