- How do I install goldnead/statamic-events in a Laravel Statamic project?
- Install the addon with Composer using composer require goldnead/statamic-events. Statamic addons are normally auto-discovered, but if the package ships publishable configuration or migrations, run the vendor:publish and migrate commands documented in the README. Clear Statamic's caches after installation so the addon's tags and settings are registered.
- Which Statamic and Laravel versions does goldnead/statamic-events support?
- The README and composer.json are the authoritative source for supported Statamic and Laravel versions. Check those constraints before installing or upgrading, because Statamic addons often track specific major versions of Statamic and Laravel. If you are on an older Laravel release, verify compatibility or pin the addon version that supports it.
- How do I create multi-date events with this Statamic events addon?
- Create event entries and attach multiple dates or occurrences to each event. Each occurrence can carry its own scheduling details, while the parent event holds shared content such as title, description and location. If you run multiple brands, use the addon's brand scoping to keep event catalogs separated within the same Statamic installation.
- How do I display upcoming and past events in Antlers templates?
- Render events in Antlers using the listings and tags provided by the addon, then filter for upcoming or past events based on occurrence dates. The exact tag names and parameters are documented in the README. Use customizable listing views to control markup for cards, detail pages and event archives.
- Does goldnead/statamic-events support ICS downloads and calendar feeds?
- Yes. The addon supports ICS downloads for events and calendar feeds for subscribing to event schedules. This lets visitors add occurrences to Google Calendar, Apple Calendar or Outlook without manual entry. Check the README for the feed routes and any configuration needed when using multiple brands.
- How are per-event timezones handled?
- Each event can define its own timezone so occurrences display correctly for the event's local context. Store dates consistently and let the addon handle conversion for template output and ICS feeds. Test around daylight-saving transitions if your events span timezone changes.
- Can events use a physical venue or an online location?
- Events can use either a venue or an online location, so you can publish in-person and virtual events from the same event model. Location details are available to Antlers templates for display and can be included in calendar exports. This avoids maintaining separate event types for physical and online gatherings.
- How should I test events in a Laravel application?
- Test events like other Statamic content by creating entries in tests, freezing or faking time with Laravel's date helpers, and asserting that upcoming and past filters return the expected occurrences. Use the addon's own test suite as a reference if it is published. Run tests against the same Statamic and Laravel versions you deploy.
- What are production concerns for event listings and calendar feeds?
- Cache calendar feed responses where possible and avoid querying all events on every request by filtering on occurrence dates and limiting the fields you need. Statamic's static caching can help public listings and archives. Warm caches after publishing events so upcoming lists and feeds update predictably.
- What are the alternatives to goldnead/statamic-events, and is it actively maintained?
- Alternatives include modeling events manually with Statamic collections and date fields, or using other calendar and event addons. goldnead/statamic-events is aimed at teams needing multi-date occurrences, per-event timezones, venues or online locations, ICS downloads and calendar feeds. Check the GitHub repository for recent releases and issue activity before adopting it, and review composer.json constraints for Statamic and Laravel support.