Backdrop, Drupal and CMS

Drupal:

Difficult to learn as the org grew, and difficult to migrate to new versions
Expensive to migrate to new versions
Based on Symphony framework - routing, change in code was difficult, had to be rewritten
Harder to learn what’s going on with Drupal 7 and move to Drupal 8
Not agile
Difficult to add media content - not flexible
Configuration management- yemo parsing
Difficult to find things
Headless CMS - database backend, choose your frontend
Developer experience - more important than the end user

Backdrop:

Agile workflow
Easy to learn, use, host
Faster to run
Solve problems that Drupal has
Just one file entity - makes process easy to
Shared hosting
Configuration management- json parsing - faster
Code on the server, get the URL and then you get a user interface
Dy-done : tool for lamp stack
Built in editor
Community is on Github - backdrop-contrib
Feeds - get feed from old system and move to Backdrop
database backend (build API, or somehow migrate data) , choose your frontend
PHP template for frontend, static HTML file which you can edit
Doesn't have a template for map/blocks like Squarespace - can code in javascript though
Only supports MySQL - API for accessing database (dbquery)
Put a feature and automate the updates (maybe every week)
Need to have modules for third party integrations
End user first - how easy is it for them
Good photo management, media browser - add everything in the database and have it on the editor
No built in library for Videos - users use links from YouTube/Vimeo
Online chat for resources - backdropcms.org/resources - Zulip (community meetings)
Runs on new versions of PHP - php 5,6,8

WordPress:

Navigation menu