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:

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.

BIEN - Backdrop Import Export Nodes (Migrating Content)

This module has been around for a while and serves a interesting use case. If you want to move content from one website to another, you can use BIEN to export it and import it. 

For advanced use cases, something like the Feeds module is a more powerful and flexible solution. BUT, BIEN is much easier for simple use cases.

Let's look at what the modules does now, talk about what it should do, and discuss any better alternatives that might exist (if any)?

Pages