- Featured Columnists
Table of Contents
- Web Basics
- Publishing on the Web: Putting Files on the Server
- Web Design Process and Workflow
- Project Management
- Mark My WWWord: HTML and XHTML
- Standards Compliance
- Meta Tags and Search
- Enhancing Web Page Interaction
- Web Graphics
- Web Page Optimization
- RSS: What’s it for?
- Emphasize Hyper in Hypertext
- Give 'em Something to Talk About
- What's a product without a selling point?
- Site Matters
- Organize This!
- Inverted Pyramid – No Toppling
- Beauty Is in the Eye of the Beholder
- Whizzy Things and Other Distracting Objects
- Don't Make Me Read Twice
- What the Font Does It Say?
- No Flaunting Creative or Fancy Lexicon, Better Yet Cut to the Chase
- Cut the Fat
- Text Harmony and Understanding (and Consistency)
- Peace and Link Love
- Tale of Two Proofs
- Just the Facts, Ma'am
- Books and e-Books
- Online Resources
- Overview of Servers
- Server Programming Basics
- Careers in Web Design
- Intellectual Property for Web Designers
Cut the Fat
Last updated Oct 17, 2003.
Readers scanning and rarely reading word for word justify the need for shorter paragraphs. The general recommendation is to keep the paragraphs at two or three lines, three to five sentences, or one idea. Emails or content without paragraph breaks are difficult to read because it's easy to lose your place and not be able to find it. The spacing between paragraphs provides cues to where you are on the page. Long paragraphs may work better when broken into two paragraphs.
Just like it's harder to stay on track reading a long paragraph, it's tough to follow when the text goes from one side of the screen to the other. The number of characters per line varies based on font size. Lines with 40 to 60 characters are the norm on sites that have well-structured paragraphs.
Figure 7 has an example of a long text taking up the length of the screen. I talked with IBM developerWorks and they have debated the long vs. short issue and chose to stick with long.
Figure 6 Darwin Magazine uses narrow paragraphs for easier reading and tracking.
Figure 7 IBM developerWorks uses the most of the screen width, making it harder to read and track.
Tip #7: Use short paragraphs.