hortus:publish:events
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| hortus:publish:events [2026/04/07 11:55] – savino.frisardi | hortus:publish:events [2026/04/07 12:04] (current) – savino.frisardi | ||
|---|---|---|---|
| Line 29: | Line 29: | ||
| | **Save the schedule** |Click Add in the Add Schedule modal. The new schedule block is then displayed in the event editor as a dated card on the schedule timeline.|Saving the schedule turns draft logistics into a visible agenda structure that can be refined further.| | | **Save the schedule** |Click Add in the Add Schedule modal. The new schedule block is then displayed in the event editor as a dated card on the schedule timeline.|Saving the schedule turns draft logistics into a visible agenda structure that can be refined further.| | ||
| | **Add more schedules** |Repeat Add Schedule to create additional sessions on the same day or on different days. The screenshots show multiple schedule cards under the same event.|This supports multi-session and multi-day events without forcing everything into one generic block.| | | **Add more schedules** |Repeat Add Schedule to create additional sessions on the same day or on different days. The screenshots show multiple schedule cards under the same event.|This supports multi-session and multi-day events without forcing everything into one generic block.| | ||
| + | |||
| + | **Define program(s) with a schedule** | ||
| + | ^ Event Creation action ^ What id does ^ What it matters ^ | ||
| + | | **Add a program inside a schedule** |Inside a saved schedule card, click Add Program. This opens a second modal used to create smaller agenda items nested inside that schedule.|This allows the organiser to move from a simple session plan to a detailed agenda with lectures, exercises, or sub-activities| | ||
| + | | **Name and describe the program item** |In the Add Program modal, fill Title program* and the Description field. The description area uses the same rich-text pattern as the other editors.|A program title and short explanation make each sub-activity understandable and easier to scan during the event.| | ||
| + | | **Set program time and participant cap** |Fill Time* with the specific time range for the sub-session. Optionally use Participants to define a maximum number of participants.|This adds operational precision, especially when activities have different durations or limited capacity.| | ||
| + | | **Add program location details** |Use Street, Housenumber, | ||
| + | | **Assign program conductors** |Fill Program Conductors* with the person or people responsible for that specific sub-session.|This clarifies who leads each activity and helps participants identify the right contact or speaker.| | ||
| + | | **Save the program item** |Click Add in the program modal. The item then appears nested inside the schedule card, with its own title, time, short description, | ||
| + | | **Review the generated agenda** |After schedules and program items are added, review the right-hand timeline. The screenshots show the structure clearly: date heading, start times, schedule cards, and nested program blocks.|This lets the organiser check that the event reads well from a participant perspective before publication or final save.| | ||
| + | |||
| + | {{: | ||
| - | * define title and description | ||
| - | * set date and schedule | ||
| - | * specify participation details | ||
| - | * add related content (project, resources) | ||
| - | * configure registration | ||
| - | * submit (if moderation applies) | ||
| ---- | ---- | ||
hortus/publish/events.1775555730.txt.gz · Last modified: by savino.frisardi
