Fix structural issues while they're still cheap
Why I fixed a few "small" issues in this Lab's rough wireframes instead of waiting for hi-fi.
Moving a wall on a blueprint takes an eraser.
While reviewing my own wireframes for this Lab, I found a few issues. They were rough, low-fidelity boxes, so it was tempting to leave the fixes for the hi-fi pass.
I fixed them anyway, because none of them were cosmetic:
- Text ran about 180 characters per line, so I set a 720px reading column. Column width drives type size, image sizes and the Webflow container classes.
- "Related Notes" was showing Logs. That decides which CMS filter gets built.
- There was no way to tell a Log from a Note. Adding a Format chip meant adding a CMS field, and adding it early means every entry is tagged from day one.
The cost of a structural change grows at every stage. In a wireframe, it takes minutes. In hi-fi, hours. Once it's built in Webflow, days. Once it's live with content, every entry has to be checked.
The test I use now: does this change affect how the page is built or how content is written? If yes, fix it now, even if the wireframe is rough. Colors and polish can wait.
Moving a wall on a blueprint takes an eraser. Moving it after the drywall is up takes a demolition crew. Wireframes are the blueprint.
What worked
What didn't
Moving a wall on a blueprint takes an eraser.
