Breakout Room 1

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.

The Voluntary Product Accessibility Template (VPAT) is a standardized document used to describe how well a digital product meets accessibility standards such as WCAG. It’s commonly required by government agencies and large institutions, but increasingly affects smaller teams and open-source projects as well. 

I'm working on a 2.x version of the Opera theme and would love to get feedback on the design and features. 
https://backdropcms.org/project/opera

I also want to talk about the idea of Design Tokens, a module that could potentially take the place of the Color module. No release yet, but available for testing and feedback here:
https://github.com/backdrop-contrib/design_tokens

This is a time for reflection on what we have learned at Backdrop LIVE, what we plan to do with our new found knowledge/experiences, and where we are headed as an opensource community. 

We welcome everyone to participate and share your Backdrop LIVE experiences.

Bee is the command line tool for Backdrop.

One relatively recent request that I have been thinking a lot about recently is having the ability to define settings for Bee and I have been thinking about what that might look like. I will share my thoughts so far and hopefully get ideas for what regular users of bee would find useful.

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.

One of our community members shared an article (link below) about Dashboards and using them to help give editors actionable, real time (mostly) insights on their site content.

Backdrop has quite a flexible Dashboard system but there is a module to provide advanced options (link below).

This is an opportunity to explore what people in the community are doing with dashboards, and what modules or Views can help.

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.

I want to talk about developments since the last Backdrop LIVE.  

Multiple provider modules have been released and I am also working on ai automators.