UX Foundations · Step 4 · 7 min read
Content first
Design with the real words and data, not with placeholder text. How to take a content inventory and audit, why lorem ipsum hides problems, and how to write labels, links and microcopy that people can find, scan and trust.
People come for the content, not for the layout. They want the price, the opening hours, the delivery date, the answer. If you design boxes first and pour words in later, the words never quite fit: labels get cut, headings get vague, and the most important sentence ends up below the fold. Starting with real content (what you have, what people need, what it's called) gives your structure and your screens something solid to stand on.
What you'll be able to do after reading:
- Explain why designing with real content beats placeholder text
- Run a simple content inventory and audit
- Write labels and links that people can find and trust
- Use microcopy to help people understand where they are and what happens next
1. Why content comes first
Jeffrey Zeldman wrote it in 2008: "Content precedes design. Design in the absence of content is not design, it's decoration" (Zeldman, Content precedes design, 2008).
Placeholder text ("lorem ipsum") looks tidy because it's the same length everywhere. Real content isn't. Real product names are long, real addresses wrap onto three lines, real error messages need two sentences, and real lists are sometimes empty. Designing with real content shows those problems while they are still cheap to fix.
If you don't have the final text, use realistic text: the longest product name you have, a real customer question, an actual price with currency. And design the hard cases too: no results, one result, a very long name.
2. Know what you have: inventory and audit
- 1Inventory
List every piece of content you have.
Name, place, owner - 2Audit
Judge each one: keep, fix, merge or remove.
Is it right and still needed? - 3Group and label
Organise what is left, in people's words.
Card sort if unsure - 4Design with it
Lay out screens with the real text and data.
No lorem ipsum
NN/g's definitions (NN/g, Kaley, Content Inventory and Auditing 101, 2020):
- A content inventory is "a list of every piece of digital content you currently have".
- A content audit "examines, assesses, and evaluates the quality of the content listed in the inventory".
Both fit in one spreadsheet. A small example for the fictional plant shop:
| Content | Where it lives | Owner | Last updated | Decision |
|---|---|---|---|---|
| Delivery costs | Help > Shipping | Customer service | 2024 | Update: prices changed |
| Plant care guides (40 pages) | Blog | Marketing | Various | Merge into one "Plant care" section |
| Returns policy | Footer PDF | Legal | 2022 | Rewrite as a web page |
| "Our story" video | Home page | Marketing | 2021 | Remove from home; keep in About |
NN/g's tips: start small, with the content people use most or that supports top tasks; give the work a time box; and remember it's never really finished.
The inventory is also your list of cards for a card sort (see Card sorting and tree testing).
3. Labels people can find
People don't read menus; they scan them for a word that matches what's in their head. NN/g calls this information scent: people pick the link that seems most likely to lead to what they want, based on "the link label, the content that accompanies the link, the context in which the link appears" and what they already know (NN/g, Budiu, Information Scent, 2020).
Says what is on the other side.
"Delivery costs", not "Learn more"Keeps its promise.
No surprise page after the clickMakes sense on its own.
People read links, not paragraphsShort, key word first.
The first two words carry itNN/g's "4 Ss" for links: they should be specific, sincere, substantial and succinct (NN/g, Moran, Better Link Labels, 2019). Moran names the generic "Learn more" as "one of the most common link failures". And put the key word first: in lists, users "typically see about 2 words for most list items" (NN/g, Nielsen, First 2 Words, 2009).
| Weak label | Why it's weak | Better |
|---|---|---|
| Solutions | Could mean anything | Plant care services |
| Learn more | Not specific | Delivery costs and times |
| Click here to see our returns policy | Key word last | Returns: how to send a plant back |
| SKU catalogue | Team jargon | All plants |
| Green Club | Branded name, no meaning | Loyalty points |
Jargon is the quiet enemy of findability. NN/g suggests two questions before using a technical term: how many readers will know it, and how important is it in your context (NN/g, Moran, Dealing with Technical or Professional Jargon, 2023).
4. Microcopy: the small words that guide
Microcopy is the short text around the interface: page titles, button labels, hints, empty states, error messages. It does a lot of the navigation work. A clear page title answers "where am I?"; a button that says "Pay €24.90" answers "what happens next?" much better than "Continue".
Keep it short, because people read very little. Nielsen estimated that on an average web page, "users have time to read at most 28% of the words during an average visit; 20% is more likely" (NN/g, Nielsen, How Little Do Users Read?, 2008). The GOV.UK guidance sums up the goal: "Good content design helps people quickly find out what they need to know or do" (GOV.UK, Understand content design, first published 2016).
AI tools can draft label options, shorten text or suggest microcopy for many states quickly. Treat their output as a first draft: check it against your terms and voice, and test labels with people. See AI for content design.
5. Common mistakes
- Designing every screen with lorem ipsum and finding out late that the text doesn't fit.
- Moving all old content into the new design without an audit.
- Labels in the team's language ("SKU", "Module B") instead of the users'.
- "Learn more", "Click here" and "Other" as link text.
- Two names for the same thing in different places.
- Forgetting empty, long and error cases.
6. Vocabulary
| Term | Meaning |
|---|---|
| Content first | Starting design from the real content and what people need from it |
| Lorem ipsum | Fake Latin-like placeholder text |
| Content inventory | A list of all the content you have |
| Content audit | Judging each piece: keep, update, merge or remove |
| Information scent | How strongly a label suggests it leads to what someone wants |
| Microcopy | Short interface text: titles, buttons, hints, errors |
| Jargon | Specialist words that outsiders don't understand |
7. Try it (no tools needed)
- Pick a screen you designed, or a screen of an app you use.
- Replace every placeholder with real or realistic content: the longest name, a real price, an empty list. Sketch it on paper. What breaks?
- Rewrite three labels or links with the 4 Ss. Put the key word first.
- Ask one person to tell you, from the labels alone, where they'd tap to do a common task.
Reflection questions: Which label did you write in your team's words rather than the users'? What would the screen look like with no results at all?
8. If you already practise
- Ask for real content (or at least real examples) before the first wireframe, and treat its absence as a project risk.
- Keep a shared glossary of product terms with one approved name per concept, and use it in designs, code and help pages.
- Pair with a content designer or writer early; label decisions are structure decisions.
Checklist
Learn more
- Jeffrey Zeldman, Content precedes design (2008)
- NN/g: Content Inventory and Auditing 101 (2020) · Information Scent: How Users Decide Where to Go Next (2020) · Better Link Labels: 4Ss for Encouraging Clicks (2019) · First 2 Words: A Signal for the Scanning Eye (2009) · How Little Do Users Read? (2008) · UX Writing: Study Guide (2024)
- GOV.UK: Understand content design (2016, updated 2026)
Books, courses and videos to go deeper
- Content DesignSarah RichardsBook · Content Design London, 2017 (Amazon)
- Content Strategy for the WebKristina HalvorsonBook · New Riders, 2009 (Amazon)
Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.
Related
Information architecture · Card sorting and tree testing · AI for content design · Forms · Interface states: empty, loading, error, success · Affordances, signifiers and feedback