In today's world, users are accustomed to having results personalized for them without having to do any work. If you login to your favorite store, e.g. Amazon, you'll get a list of recommended products. Google will provide you location-based searches. Your video streaming services, banking, big box stores, even your potential online dates all have incorporated location-based way-finding. Sometimes, you aren't even aware that you are being directed by location. 

Let's be honest, I don't really like the Quicktabs module. It's not that I don't think it's useful, it's just that users can do some pretty gnarly stuff with it that causes issues, like a ton of PHP notices being thrown into logging. 

Whenever I hear the word batch, I think of a nice, delicious batch of homemade cookies, and while the Drupal Batch API might not taste as good, understanding how to use it is an essential part of every Drupal developer's toolkit. 

In my last post in this series, I started going down the theming rabbit hole for Backdrop. A lot of that was very similar to my experience with Drupal 7 (D7), but separating the regions from the theme files was a really nice addition. 

Now, we are going to dive into more of a back-end-related discussion. To do so, we'll be converting the XML Sitemap module to be able to run on Backdrop. It was the most popular module I could see, other than CTools, that hadn't been ported to Backdrop. Since it has no dependencies, I thought it would be good for me to start on this one. 

In my last post in this series, I went over my motivations for exploring Backdrop and a few of the differences between it and Drupal 7 (D7). In this post, I'll actually go over setting up Backdrop and pushing code up to a server. 

In my last post in this series, I went over setting up Backdrop on Pantheon and in a local environment. After I setup a Drupal site, or now Backdrop site, I usually head straight into the theme section. I've never actually left a site in Bartik that I can remember so I always begin the process of creating a sub-theme. 

I think I first heard about Backdrop CMS from the Weekly Drop. As many Drupal developers do, I have a Wednesday ritual of pausing and surfing through the weekly headlines over a cup of coffee. Usually, I save a few articles for reading later, but on this particular Wednesday what do I see but...whoa, a fork?