Define scope of 'basic' event recipe that would be offered in the installer

Created on 25 July 2024, about 1 month ago
Updated 12 August 2024, 26 days ago

Problem/Motivation

Most likely, there will be a 'basic' event recipe that is the one offered to users in the installer. We want to provide users with a simple but functional way to create events on their sites.

It should ideally include event features that are common across other platforms, but should (probably) exclude advanced functionality such as registration or a calendar view. Those could potentially be offered as separate add-on recipes later in the journey.

Remaining tasks

  1. Discuss!
  2. Define the initial recipe
  3. Create a new issue for the development of the recipe
📌 Task
Status

Active

Component

Track: Event

Created by

🇦🇺Australia pameeela

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @pameeela
  • 🇦🇺Australia pameeela

    @mandclu had a play with the recipe at drupal/events. Some points for discussion:

    1. Should there be an optional image field?
    2. The upcoming and past event listings are views pages. I think this would be more intuitive as nodes, so they would appear in the content list and be editable.
    3. I think it would be good to get some user feedback on the multi-date functionality
    4. What should the 'default' date format be? Ideally we could ask users their preference, or if not we could consider how to guide the user to change it.

    I am sure others have thoughts!

Production build 0.71.5 2024