Skip to content
EntryWick documentation

For somebody who signed up five seconds ago, and has never seen EntryWick before.

Get started — the first-run wizard

Who opens it: somebody who signed up five seconds ago, and has never seen EntryWick before.

What they came to do: have an event that people can register for.

True when they leave: an event is published, its registration form is open, and its link is theirs to send. Or they put the wizard aside on purpose, knowing nothing was half-made.

The gate this screen exists for (docs/BUILD_PLAN.md week 22): a new organization reaches a published event in under ten minutes, without reading docs.

The six steps

Step What it asks Optional
1 Pick a starting point One of six kinds of event, each with its vertical, days and kinds of attendee on the card no
2 Fill in the blanks The event's name, date, venue and whatever else its event template declares no
3 Your groups Match the event template's example tree to groups you have, create it, or ignore it no
4 Make it yours Two files and a name; the colours are read from the icon yes
5 Your own address A name under your own domain, with two DNS records to copy yes
6 Publish One button no

Steps 2 and 3 are the same fields the import wizard asks (event-template-import.md); step 4 is the branding wizard's two files (brand-assets.md); step 5 is a custom domain (custom-domain.md). This screen puts them in one order and nothing more — every rule still lives in the service that owns it, so doing it here and doing it one screen at a time produce the same organization.

Decisions already made

  • A brand-new Owner lands here, not on the dashboard. An empty dashboard is not the way to a published event. Every other sign-in, and every other role, still lands on its role's own home.
  • It is skip-able, and skipping breaks nothing. "I will do this later" closes it for good and hands over to the dashboard's short checklist, which keeps the way back. Nothing is half-created: each step's own service has either finished or has not run.
  • It is resumable, by anybody. The progress lives on the organization (tenants.settings.onboarding), not in an HTTP session — so the tab can close, the phone can take over, and a colleague can finish what somebody started. The page says how far along it is.
  • The brand and the address are applied before the event. Neither can block an event: a brand that will not save is said out loud and the wizard carries on, and an address only claims a name and shows two records.
  • Publishing is the last thing. If publishing is refused — a plan limit, a self-hosted licence — the event and everything in it is still there as a draft, and the wizard says where. The wizard is only "done" when an event is actually published, because that is what the gate says.
  • It stops offering itself once an event is published, or once somebody has put it aside. A wizard that never goes away is a wizard people learn to ignore.
  • Nothing an event template brings is locked. Days, types, forms, templates, schedules and rules are all editable the moment the event exists. The wizard's last screen says so.

Completion analytics

Each step records the moment it was finished, and finishing a step twice keeps the first time — the number that matters is when somebody got there, not how often they went back. That makes the funnel a read over tenants, with no second analytics store to keep in step:

php artisan ew:onboarding

It prints how many organizations opened the wizard, how many published, how many put it aside, how many finished each step, the median time to publish, and how many of the finished ones came in under ten minutes. --json gives one line for a dashboard.

Every step also writes an audit_logs row (tenant.onboarding_started, tenant.onboarding_step, tenant.onboarding_completed, tenant.onboarding_skipped, tenant.onboarding_reopened), so a support question about one organization has an answer without reading JSON out of settings.

Open questions

  • Nothing here helps somebody who wants two events on day one. The second is the import wizard's job, which is the right answer but is not said anywhere on screen.
  • The event template picker is a radio list with a line of shape under each name. Real cards — a colour, an icon, a sentence of voice — would help somebody choose between "Volunteer Day" and "Community Celebration".
  • The ten-minute gate has not been timed with two non-engineers yet; that is week 22 step 5, and it needs people.