- How do I install goldnead/statamic-booking in a Laravel Statamic application?
- Install it with Composer using composer require goldnead/statamic-booking, then follow the addon's Statamic setup instructions for registering and configuring it. It is built as a Statamic addon on a Laravel/PHP stack, so normal Composer and Statamic addon conventions apply. The v1.7.0 navigation change does not add migrations or a new config key.
- What Laravel and Statamic versions does this booking addon support?
- The package is a Statamic addon within a Laravel/PHP stack and follows standard Statamic addon conventions. Exact Laravel and Statamic version constraints should be checked in the package's composer.json and README before adoption. For the new control panel settings layout, statamic-brand-context 1.16 or newer is required, while older versions safely keep the previous layout.
- How do I define bookable resources and availability rules?
- The addon provides configurable bookable resources and availability rules so you can model appointments, rentals, or services without building a custom booking system. You define the resources and their availability according to the addon's configuration and Statamic-native templates. The overview does not indicate database migrations or new config keys for the v1.7.0 navigation update.
- Can I use frontend booking forms with validation?
- Yes, the addon includes frontend booking forms with validation and Statamic-native templates for integration into your site. Developers can expose booking workflows to visitors while keeping booking records manageable in the control panel. The exact form markup and validation rules should be taken from the package documentation.
- How are booking email notifications and statuses handled?
- The addon supports email notifications and booking status tracking as part of its booking management workflow. Bookings can be reviewed and managed through the Statamic control panel, alongside availability and scheduling. Notification recipients and status behavior should be configured per the package documentation because the provided overview does not list every option.
- Do I need to run migrations or change configuration when upgrading to v1.7.0?
- No, the v1.7.0 change is additive and does not include database migrations, new config keys, or required configuration changes. Existing installations upgrade normally via Composer. To see the new settings navigation layout, upgrade statamic-brand-context to 1.16 or newer; otherwise the addon continues with the previous layout.
- What is statamic-brand-context and why does this addon reference version 1.16+?
- statamic-brand-context is the addon that provides shared settings-page context and navigation for Statamic control panel addons. goldnead/statamic-booking v1.7.0 adds settingsNavParent() to declare its control panel navigation parent, and statamic-brand-context 1.16+ is needed to activate the new settings sub-item layout. Older versions safely ignore the method and retain the previous layout.
- What happens if statamic-brand-context is missing or older than 1.16?
- The settingsNavParent() method is ignored when statamic-brand-context is absent or below 1.16, so the addon keeps its previous settings layout. The assessment expects no fatal errors and describes the change as low risk and backward compatible. Users may be confused only if they expect the new navigation layout without upgrading the dependency.
- Are there Control Panel permission implications for the new booking settings entry?
- The v1.7.0 change is a presentation-layer navigation declaration and the technical evaluation does not describe any new permission requirements. Existing Statamic control panel permissions for the addon's settings and booking management should continue to apply. If your roles rely on specific settings navigation visibility, verify the entry after upgrading in a staging environment.
- Is goldnead/statamic-booking suitable for production, and how should I test the upgrade?
- The package is designed for production Statamic sites that need reservation workflows, and the v1.7.0 navigation update is assessed as low risk with no data model, caching, or scaling impact. Test the Composer upgrade in staging with both your current statamic-brand-context version and 1.16+ to confirm the settings layout behaves as expected. Also confirm that frontend booking forms, notifications, and control panel booking management still work for your configured resources.