A few weeks ago I gave a talk about testing business critical features with Behat at Midwest PHP. That talk came after working with Behat for over a year and consulting with our agency partners about automated testing.
Any website that wants to provide a speedy experience to logged-in users (e.g. content editors, forum participants) or even logged-out users who need a unique page (online shoppers, viewers seeing personalized content, etc) needs an application object cache. These caches store built-up data objects (e.g. a user, a post, a node) between requests so that there’s less work for the CMS to do to serve a page that needs one of those objects in the future. They’re crucial.
I always feel a sense of rebirth at the beginning of each Gregorian year (sorry @c4rl), and it's fatefully appropriate for the beginning of 2015 to see the launch of Backdrop CMS 1.0. For those unfamilar, Backdrop CMS is a "full featured CMS with a focus on small-medium businesses, education, and non-profits" that is "a fork of the Drupal project".
Pantheon announces the release of Pantheon Autopilot to keep sites up-to-date by automatically detecting, performing, testing, and deploying updates for WordPress and Drupal CMS solutions.
Autopilot from Pantheon allows your team to focus on innovation, instead of CMS updates.
Choosing the right developer portal for your business is crucial. The developer portal often serves as the foundation of a successful API Program—it's a place for your developer community to thrive and grow, and houses your API products. When you use Apigee to manage APIs that you build, it often comes down to a simple choice: the integrated developer portal that comes with the license, or a Drupal developer portal.
As a Developer Advocate, I work with web development teams on improving their workflows. That often means discussing how to adopt Continuous Integration (CI). I usually center my answers on a suite of Pantheon tools meant to combine an external git host (like Github or Bitbucket) with a Composer-based repo structure, and a CI platform (like CircleCI) push a build artifact to Pantheon. Any number of tests can then run after the push.
On June 30, 2023, Pantheon will discontinue support for its built-in LocalDev feature. We are making this change because in the years since we introduced LocalDev, a number of more fully-featured options have become available to developers, allowing offline development and code editing. Have no fear: we’re here to help you with the transition.
Remote working can exacerbate the worst failings of waterfall web development—the practice of developing websites in discrete linear steps, which means work must happen sequentially, not concurrently, and projects take longer to complete.
Like with preventative maintenance on your car, you can’t expect your CMS to deliver peak performance and optimal reliability if you skip your service appointments and don’t maintain it. We can all agree that’s sage advice.
Today marks the release of Drupal 9.1, the first new feature release for the web’s favorite enterprise-grade, open-source CMS. It also marks the next step in Pantheon’s evolution for supporting modern PHP development practices, with the availability of Drupal 9.1 with new Integrated Composer workflow.