This year's DrupalCon North America may have been one of my favorites so far. Baltimore was a wonderful city, the sessions I attended were incredibly inspiring, and the convention itself was extremely well-organized. And, for the first time, I started to feel comfortable that Drupal 8 was finding its footing instead of being stuck in "wait-and-see mode."
Here you'll find posts about both the software and the Backdrop community.
One of the strengths of a good content management system is its ability to add on extra modules for additional functionality. In an open source environment, such as BackdropCMS, many developers share their contributions for the benefit of all, and some of these contributed modules become frequently used and a de facto solution to specific website needs.
Though Backdrop 1.6.0 may be considered a minor release, it is packed with new features that improve the powerful content management tools and lays the groundwork for comprehensive file and media management in future releases.
Sharpening your tools is an important part of any developers life cycle and can help you deliver solid, maintainable sites using best practices, efficiently and on budget. The tools I'll discuss in this post:
This was my first BADCamp. Though I have been to many other DrupalCons and Camps, I had heard that BADCamp still retained the sense of community and was scaled to allow for a great deal of interaction between presenters and attendees. To that end, BADCamp exceeded my expectations!
Backdrop 1.5 is a release packed with new features and an all-new out-of-box experience! A new default theme -- "Basis", drop-down menus, a homepage layout, demo content, and hero block provide a fresh take on the fundamentals of a modern day content management system.
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. That was until a few months ago Geoff (a.k.a. @serundeputy) showed me a way to create PRs though the GitHub UI that I find very easy (although not very coder-like).
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: