QR Album
Blog

Step by step, for the host

Step by step, written for the person hosting rather than the person coding.

Guides somebody followed before they were published here. No screenshots of menus that have since moved, and no step that quietly assumes you already know where to click.

Each one opens with how long it takes and what to have ready. Where a step can go wrong, it says how you would notice and what to do about it.

Anyone planning a wedding has no time to learn a tool. What is here is the shortest route to the result, not a tour of everything the product can do.

When a guide goes out of date it is rewritten rather than annotated. A correction pinned under a wrong step helps nobody who started at the top.

Every guide also says when not to follow it. A wedding of thirty does not need half the steps, and that belongs at the top rather than in the last paragraph. Where a step costs money, the amount is named, not merely the fact that a paid plan exists.

The guides also assume the venue will say no. No adhesive on the walls, nothing freestanding in the fire route, no signage before six, and the room turned around while you are eating. Every instruction here is written to work inside those constraints rather than around them, because finding out on the day that the sign has nowhere to go is the failure that actually happens.