Core

Lots of people want improvements and fixes in core, but it can be daunting to know how to help get the issue queue moving. Even if someone else is adding code, the wheels can grind to a halt at this point, when people don't know what to do next. Some people will comment, but feel hesitant in saying that they've tested and reviewed and officially updating the status of the issue.

Hopefully this session can help you to become more comfortable and braver in reviewing and testing core issues.

With the recent core commit to allow specifying Layout types, the next Backdrop release will better support the development of Layout Paragraphs that is underway. We've reviewed the status of this work at a previous Backdrop Live, but it makes sense to give an update on where things stand in preparation for the next Backdrop core release and the 2.x branch of Paragraphs that will follow.

Over the last 2 months, the Backdrop leadership (core committers + project management committee) have been working on a draft of a new AI usage policy. This policy is intended to guide use of AI tools in core and contributed module development. While the details are still being worked out at the time of this session submission, by the time Backdrop LIVE happens most of the details should be completed. We'll talk through the policy and I'd like to hear from the wider community further suggestions or changes they would like to see.

I'd to facilitate a discussion around the lessons I learned through porting the Drupal Media and CKEditor 5 Ecosystems to Backdrop. This will mainly focus on developers and includes topics such as configuration management (converting ctools plugins to config, config performance, return values), changes to entity information, nested modal dialogs, file display fallback support, non-writeable stream wrappers and more. We'll discuss each topic, including what was learned, what was done about it and what improvements can and have already been made to Backdrop core as a result.

How do people in the know develop under Windows? WSL? MAMP PRO? PhpStorm? Others?

How to deploy to Ubuntu?

For beginners and people of all levels who may be able to share their tips and suggest solutions on getting started working on core Pull Requests.  I am happy to be the facilitator and kick it off with some of my experiences getting started with core PR's and setting up a useful local environment.

Saving the slot, more info coming soon. 

Can and should Backdrop CMS compete with Wordpress, Squarespace, and/or WIX as a tool for individuals with limited (or without any) coding skills, to build their own website?

Not everyone will agree that this is possible or even something worth trying for. But, if you would like to see Backdrop CMS moving in that direction, this session is intended as a discussion about what we can do to move in that direction. Most likely, we’ll focus on contrib ideas, but we may also discuss ideas for Backdrop CMS core.

Without any special action, the Backdrop CMS user interface is presented in English. But of course the system can also be operated in other languages, e.g. Arabic, French, Hebrew, Persian, Spanish, Swedish, and many more.

In this session let's talk about,

• how to equip a Backdrop website's user interface with multiple languages,
• which tools can be used to translate the user interface individually,
• how to help improve translations for the community on the Backdrop translation server.

In short, config recipes are simple modules that add functionality to your site mostly by adding some prepared configuration. They do not add new features that are not already available through Backdrop Core or existing contrib modules. 

Available config recipes at this time: