Comparison to Bookable Entities Everywhere

Was the intent to have something that gets up & running faster?

Hi, at one point I did have BEE listed as a similar module, I'm not opposed to adding that back in with some key differences.

This module was created when I had a couple clients at the same time needing some similar booking related features on their website. I originally tried going down the BEE/BAT route to see if those modules would fit my needs and they just seemed overly big and complicated for what I needed. The BEE module does require at least some parts from BAT to work, and BAT is aimed at Hotel booking type of flow. With the need to handle all the complexity that comes with that type of booking, I do understand why there is such a vast amount of settings to get up and running.

The intent of Bookable Calendar is to be a more simple repeating date booking system, I personally compare it more to the module Entity Registration → but if you have a repeating rule for your event that people register for. The examples I normally give are: Conference Rooms, Voice Lessons, Park Entry, Queue Reservation, or any place that is a repeating value like "every 15 minutes allow 5 people in".

Are there features over that this module has no plans to support (e.g. accepting payments)?

I'm sure there are some features that I don't think belong in this module, currently payments is not in my roadmap, but I'm not opposed to getting it to work with Commerce → and if people are wanting that I'm willing to push that up in the roadmap and do that before I do other features. The main hesitation I'd have about features would be adding features that add-in extra steps for the end user, as I want this to be easy enough for a non Drupal dev to be able to use.

How does the architecture differ?

As said before, BEE has a lot more settings, you can manage lots of different things that I seriously have no idea what they do. BEE attaches to existing Nodes (much like Entity Registration) where you edit a content type and turn on BEE for that node.

Bookable Calendar is a set of separate Content Entities, and you edit settings and everything for the calendars on those Entities instead of attaching them to Nodes. I personally think thanks to Smart Date → my repeat rule widget is way easier to use to make very complicated open/close rules.

Are there any other differences that users should know about?

Bookable Calendar is built to be a lightweight repeating date registration/booking module that pulls in as little amount of dependencies as it can and just use what Drupal already has to make things work in a simple enough way.

This is certainly helpful; thanks.

Major differences I'm seeing:

1. No payment integration here, and
2. it's not possible to reserve variable-length time slots here.

Please add a "Similar Modules" section to the project page, with a link to the new Comparison of booking/availability/reservation modules → in the Drupal documentation. Thanks!

Thanks, Colan, that is added!

Automatically closed - issue fixed for 2 weeks with no activity.