Self-Hosted, Headless, and Hyper-Automated: The Backyard DevOps Stack for Backdrop Applications (Part 2)

In Part 1, we talked about using Backdrop CMS to run your entire business, from job tracking to stadium screens. Now, let’s get our hands dirty and talk infrastructure. If your business apps are critical, you need speed, reliability, and full control over your data.

We're trading expensive cloud bills and vendor lock-in for a lean, powerful, self-hosted infrastructure stack that keeps you in the driver's seat.

This is a deep dive into what DevOps need to develop, deploy, and automate your mission-critical Backdrop applications:

Backdrop For Beginners

An opportunity to ask beginner questions about Backdrop CMS. We'll have a demo site ready to show how to do things and answer your questions LIVE. A perfect place to ask beginner questions about things like:

* Content Types and Fields
* Getting Started with Views
* The Backdrop CMS Layout System

A dragon's eye view of finding content in Backdrop

Out of the box, Backdrop CMS has Views that can have exposed filters and Search.

However, there are modules that can extend the capability of Views and Search including integration with third party solutions including AI.  The purpose of this session is to give a high level overview of the options with very brief demos.  The idea being if there is demand to dig deeper, these sessions can be added later in the unconference.

Payment options in Backdrop CMS

Even those who don't run a full-fledged online shop sometimes need the option for website visitors to make payments, such as donations, costs for informational materials, or event registration fees.

What are good payment options in Backdrop? Which payment methods are recommended, can they easily be implemented in Backdrop, and how? For example: How can Paypal or Stripe be integrated with various modules like Webform, Registration, Ubercart, or Basic Cart?

Using Composer

I have a composer file in OpenAI and S3 File System.  I started using the Composer Manager module for managing dependencies although both of these modules ship with a vendor directory so users don't need to use composer.  I hope the discussion gives direction to what we should and shouldn't do with managing dependencies in Backdrop.

Pages