Event template import wizard — admin

Who opens it: an organizer setting up, often for the first time, who has an event in mind and no idea what a "registration form" is.

What they came to do: get from nothing to an event they can publish, without making twenty decisions they are not yet qualified to make.

True when they leave: a draft event exists with days, types, forms, reminders and check-in points, and they know what their plan could not give them.

Decisions already made

• Four steps: choose → fill in the blanks → match your groups → review. Placeholders are the only thing they are asked to type, and every one of them is declared in the document with a label and usually a default.
• The group step offers three honest answers: match the event template's example groups to mine, create them, or ignore them.
• Anything their plan cannot run is imported switched off with a reason, not skipped and not refused — ninety working objects and one clear warning beats nothing at all (§4.6).
• The review step says what will be created, in their own vocabulary (term()), and what is still missing.
• Import is one transaction: a document that fails halfway leaves nothing behind.

Added in week 16 step 8

• Anything the plan had no room for is kept on the event (skipped_template_items), with the document's own definition, the entitlement key that stopped it and the limit at the time. The import notification still names the first one, but the list now outlives the notification.
• "Add skipped event template items" on the event's page offers them once the plan allows at least one, item by item, each through the service that owns its rule. A type that required a skipped companion gets that requirement back when the companion is added. An item the plan still refuses stays recorded; one the organizer made by hand under the same code quietly leaves the list.
• §1.5 no longer says "upgrading and re-importing creates them": re-importing makes a second event, which is how the Chaperone, Regional Member and Respected Leader types used to be lost.

Open questions

• The warnings list can run to a dozen lines on Free. Is that a summary with a "show all", or does it belong on the event afterwards where it can be acted on?
• Nothing yet shows an event template preview — an organizer picks by name and description alone.
• Re-importing gives the second event's form a new code (-2). Correct, but it will look odd in a form list.