Our first paying customer sat down with the invitation editor and got stuck four times. They wrote each one down and sent it to us. Every point was fair, and two of them turned out to be our bug rather than their confusion. Here is what they told us, and what we changed.
The form did not say what it wanted
The editor divides its sections into two groups. They used to be headed Ready to share and Make it yours, which sound pleasant and explain nothing: neither tells you that the first group is what a page cannot be published without, and the second is what you can add whenever you feel like it. The first section was called You two, which is warm but does not answer the only question a couple has in front of a blank form — what am I supposed to type here?
So the groups now say Required and Optional, each with a line underneath saying what that means, and the first section is called The couple. Every section also states where its words come out on the finished invitation. Milestones become dated entries in your story section; the wedding party becomes a card each; skip a section and it does not appear at all. That last part matters — an optional section you leave empty should vanish, not leave a heading standing over nothing.
Empty boxes are a bad question
Three fields asked for a word and gave no hint which word. Label, under each partner’s name. Role and Group, for each member of the wedding party. Our customer’s note was blunt and correct: narrow it down, give me something to pick.
They are dropdowns now — Bride, Groom, Partner for the label; Maid of Honour, Best Man, Bridesmaid, Groomsman, Officiant and the rest for the role. Every one of them ends with Other…, which opens a text box, because a list written in an office in Bandung cannot predict the words your wedding uses. A suggestion is not a rule, and a couple who has already typed something we never thought of keeps exactly what they typed.
Short bios and the welcome message had the opposite problem: not too many options, but a blank page. Those now open with an example sentence you can edit or delete. Clear it and it stays cleared. Whatever is sitting there when you publish is what your guests will read, and the field says so.
Three fields that quietly did nothing
Chasing the complaint about Label turned up something worse. That field, along with each partner’s short bio and portrait, was being saved and then shown to nobody. The invitation’s opening screen only ever printed the two names. Everything else a couple wrote about themselves went into the database and stopped there.
That was our mistake, and it explains the feeling behind the feedback perfectly: the fields felt pointless because they were. Every theme now has a section that introduces the two of you — portrait, name, label, and a few sentences each — in that theme’s own style. If you have already filled those fields in, they are on your invitation now.
Preview at the size your guests will actually use
The theme demos have always let you flip between desktop, tablet, and mobile. Previewing your own invitation did not, which is backwards: almost every guest opens the link on a phone, so the person who most needs to check the narrow view is the couple, on the page showing their real content.
The preview page now has that switch, plus a link straight back to the editor. It is the same control the demos use, so the two pages behave identically — the only difference is whose wedding is on the screen.
Why we rewrote words instead of adding features
None of this is a new capability. The form asked for the same things before and asks for the same things now; the preview shows the same page. What changed is that the product explains itself — which group of sections you actually need, what a good answer looks like, and where your words land once you are done.
A wedding invitation is one of the few forms a person fills in exactly once, with no chance to learn it. That makes clarity the feature.
What we learned
One person taking the trouble to write down where they got stuck did more for this product than a month of our own planning would have. We had built the editor, tested it, and used it ourselves, which is exactly why every box on it looked obvious to us. Our customer had none of that context, and that is what made their notes worth so much: they were the first person to read the form the way every couple after them will read it.
Three things went wrong on our side, and not one of them was a broken feature. We collected a partner’s label, bio, and portrait and displayed none of them, which means nobody had ever followed a single field the whole way from the form to the finished invitation. Two of our six themes left a heading standing over a section a couple had skipped, because we had asked six stylesheets to agree with each other by hand instead of writing the rule down once. And we named the parts of the form from the inside — Ready to share and You two are how we talk about the product among ourselves, not how somebody filling it in for the first time reads it.
Our tests were green through all of it. They proved each piece did what we had told it to do; they could not tell us the pieces failed to add up to something a stranger could finish. So we changed how we check our own work. A field is not finished when the form saves it — it is finished when a guest can see it. And the rule about empty sections is now enforced for every theme automatically, rather than trusted to each one to remember.
Keep the feedback coming. If something in Goldypaper makes you hesitate, that hesitation is the bug report — send it to us, and it will end up in a post like this one.