Longer requests
Screens, contents, rules. Split a long request into those three and it holds together.
Why split it at all
Longer is not automatically better. In one dense paragraph it stops being clear where the screens end and the rules begin.
Three groups is enough: which screens you need, what goes in them, and who is allowed to see what.
Name the screens first
Just list them. Home, product list, product page, order lookup, an admin screen.
Names alone are fine. A line each on what belongs there is better.
Then say what goes in them
List the fields the way you would say them out loud. A product has a name, a price, a photo, a description. A booking has a date, a time and a headcount.
You will forget some. That is fine — add them later, one at a time.
Rules are about who sees what
This is the part people skip, and it is the part that matters. One customer must never be able to read another customer's phone number.
Write it plainly: the product list is public, enquiries are for me only, the admin screen needs a sign-in. Safe defaults are applied either way, but saying it removes the doubt.
A long request is a large job
A request that spans several screens is the largest class of work. It costs 6 credits and asks you to confirm first.
Nothing happens until you press confirm, and stopping there costs nothing. If it feels like a lot, start with two or three screens and add the rest afterwards.
Bigger takes longer
Of the seven we measured, the site with the most pages took 616 seconds and the smallest took 221.