Keep your wireframes free of distracting Lorem Ipsum
github.com
github.com
This is just another tool in the toolbox.
The most basic wireframes will be just boxes everywhere and I label the boxes, say 'Pricing Plan Feature'.
Next iteration, would be wireframe still but all the copy need to be clear and thought out ie: the tag line would be 'Pricing Plan Feature' with a sentence below it like 'Our Plan fits any budget, from $5/month to $100/month' and be in that wireframe.
When people wireframe with lorem ipsum/line blocks, giving no indication of what would/is there, it can create assumptions and confusion - for your team mates/clients. If you say it's just for layout, then just use boxes with labels - anything else is just distraction.
When I get the copy after the wireframe, it can be frustation to get handed an essay and try to fit it in a space designed for a paragraph.
Always design around the content/copy, even at the wireframe stage. Knowing the exact (or close to it) copy/content the better - allowing you to gauge the layout and spacing more accurately.
Wouldn't it be better if you put that $5/month and let them know upfront copy/prices are not set - they are meant to communicate what that area is for and how much space is dedicated to it.
What if you had in your mind that the space is for $5/month, but used lorem ipsum and designed around that.
Then the client hands you copy that goes '$5/month, $50/ year, Save $10 if you subscribe annually / 20% off.' This will likely to have an impact on your layout and spacing, since you just used 'lorem ipsum' in the wireframe step.
There are also times (like in a small company) when the person reviewing the wireframes is also the person reviewing the final copy, so if you put real copy in there the meeting will always get sidetracked into a discussion of the final copy unless you use some type of filler.
Also the block font looks extremely heavy, would skew the hierarchy of the page and be pretty distracting.
And this is to have a place holder for your text, not your typography.
> This is going to make your mock-ups less relevant and is going to be harder to explain to your clients.
But it will make your wireframes less distracting and easier to explain to your clients.
The distinction is in the level of detail. If you're not at the stage where you're picking colors, why should you be picking fonts?
Different tasks; different tools.
I personally don't find Lorem Ipsum distracting, and like others have said, think it would be quicker and easier to troubleshoot design issues using real copy. (The no descenders thing especially gets to me.)
If Lorem Ipsum is genuinely distracting to other people, though, then to each his own! Glad there's options out there for everyone.
"BLOKK is a font for quick mock-ups and wireframing for clients who do not understand latin."
> Q: What's different about this compared to BLOKK?
> A: BLOKK has unusually large character widths, which adds much length to "standard" bits of dummy text, and also creates unecessarily ragged rags in my copy. Redacted solves this by using sane character widths; averaging character widths of narrow, regular, and wide characters of standard fonts. This gives a more realistic look to the text and helps it fit into narrow columns like real text would. Redacted Font also comes with script versions in two weights: bold and regular.
It's an appropriate tool for a part of the design process.
[1]: http://informationarchitects.net/blog/the-web-is-all-about-t...