Publishing — ready as a draft, visible only when you decide
An event stays a draft until you publish it, independently of the service catalogue.
The problem
Preparing an event takes time: dates, prices, description. Showing it too soon, before it's ready, complicates things.
Without a draft status, a half-configured event risks becoming visible by mistake.
An event stays a draft until you decide to publish it.
Without Kagenda
The event becomes visible from creation, even incomplete.
With Kagenda
The event stays a draft; you decide the exact moment to publish.
How it works in Kagenda
You prepare the event as a draft, then publish it when it's ready.
- You create the event as a draftInvisible to the public while you prepare it.
- You fill in dates, prices and descriptionNo pressure, at your own pace.
- You publish when you're readyThe event becomes visible and bookable.
Event status
- Draft
- Published
- Unpublished if needed
In practice
- 1
An event in preparation
Invisible to the public as long as it stays a draft.
StatusDraft - 2
Publishing at the right moment
Visible as soon as you decide.
DraftPublished - 3
Independent of the service catalogue
Publishing an event doesn't touch your regular services.
CatalogueSeparate
Frequently asked questions
Is a draft event visible to the client?
No, only once published.
Can an already-live event be unpublished?
Yes, at any time.
Does publishing an event affect the service catalogue?
No, the two are independent.
Can several events be prepared as drafts at once?
Yes, with no limit.
