Use case: Develop Backdrop sites and be able to continuously deploy patches, updates and features cleanly and easily on Pantheon. We, the Backdrop Community, hope to offer Backdrop local drush out of the box in the near future, but for now here are the steps to get you going on Pantheon, Terminus, Drush and Backdrop CMS right now!
Install Backdrop CMS with terminus:
In February, we added support for Backdrop CMS to DDEV-Local. In this post, I’ll show you how to use DDEV-Local to easily create local, PHP based development environments. Ultimately, this allows you to leverage the power of Docker while being much easier to use.
When I was first approached about being a Backdrop CMS core committer, I was both humbled and more than a little scared. I'm extremely grateful to the PMC for having the confidence in me to offer me this role in the community, but the amount of responsibility they were handing over made me a bit hesitant. Could I do this? What if I made mistakes? What did they expect of me time-wise? This article aims to pull back the curtain and show how easy (and rewarding) it is to be a Backdrop core committer.
Backdrop CMS is about 45 days away from our 22nd on-time release, version 1.21.0. Every 4 months, we release a new version which brings with it new improvements and features to Backdrop CMS. Feature freeze is scheduled for January 1, 2022 and the release will be on Jan 15th. In the final weeks of each release cycle, there is a frenzy of activity and we try to get new improvements finalized and approved.
There was much fun in the air at BADCamp 2017! It is so great to meet with coworkers, teammates, and friends. Beautiful brisk walks in the morning, great sessions, great networking, food, and company in the evenings.
We are very close to merging (this PR has now been merged) a pull request into the 1.20 branch of Backdrop CMS that will make it possible to create simple recipes in the form of modules with nothing but a .info file and a batch of config files. While not trivial to create, these "recipe" modules could in theory be downloaded from BackdropCMS.org, installed through the UI, and enabled just like any other module.
This weekend Jen Lampton will be working with a group of high school students, in the Oakland area, on contributing to Backdrop CMS. In support of these efforts, we have decided to announce an informal Backdrop CMS contribution day. If you are a supporter of the Backdrop project and have been looking for an opportunity to contribute, Saturday would be a great opportunity to jump in and help us with a task, regardless of where you are.
Is there a feature that you would REALLY like to see get into the next release of Backdrop CMS, but you don't think you have the skills to write the code for it? Then consider becoming an advocate for that issue.
The Backdrop community has been experimenting with an "advocacy" program, in which we ask community members to identify an issue they feel strongly about, and volunteer some time to help push that issue forward. Often times, the key to moving an issue forward is the involvement of a single individual that is willing to:
Audience: developers creating forms programmatically
For many years now, I've been using #states in many of my pull requests that were around improving the admin user interface. I've found that hiding/showing form elements depending on various conditions, in many situations may result in a much better user experience for content editors and site builders using Backdrop.
I do not consider myself a coder. My contributions in the issue queues both in drupal.org as well as in the GitHub repository of Backdrop CMS had very little to do with actual code.
