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.

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:

We've been grappling with this problem for years, lacking any consensus on the best way forward. With discussions of Backdrop CMS 2.x underway, now seems like a good time to figure this out and make a decision. 

In this discussion, I'd like to review the options available and see where the current consensus is at. Much time has passed since this was discussed in detail and some folks may have changed their opinions. Can we build towards a consensus solution?

This is one of those issues that might require a real-time discussion to break the log jam.

Backdrop 1.27.0 released January 15, 2024, and included a new major version of the popular rich text editor CKEditor. The jump from CKEditor 4 to 5 is a big one, with an entirely new plugin architecture.

This session we'll be reviewing the upgrade process for sites using CKEditor 4, starting with sites that are simply upgrading to the latest version. Then we'll go over common issues and differences from CKEditor 4, such as loading CSS into the editor.

Finally, we'll take a look at upgrading modules and plugins to the new API.

Join us for a lively discussion on what should (or should not) be included in Backdrop 2.x.

The lifespan of Backdrop 1.x has been extended several times as the lifespan of Drupal 7 has been extended. Initially, our goal was for Backdrop 2.x to be released at least 2 years after the end of Drupal 7 support. Our hope was to give Drupal 7 site owners they time they need to both move to Backdrop, and prepare for the first Backdrop major version upgrade.