Turn editorial content into clear pages, accessible layouts, and reliable release files.
Give every page a reading hierarchy
Readers need to recognize the title, introduction, main sections, examples, captions, and next step without decoding decorative choices. Use a small type system and consistent spacing. Distinguish article content from navigation and commercial material. A visually exciting cover or home page cannot compensate for hard-to-read body text.
Create reusable components
Design one article template, one index or section page, and one special format such as an interview or comparison. Record heading levels, callout use, image proportions, caption style, and links. Reusable rules help a growing publication feel coherent and shorten production time.
Clear headline → short introduction stating the reader benefit → sections with useful headings → evidence and examples where needed → related next step → author/date and correction route. Use a different order only when the story requires it.
Test beyond the design file
Review the real page or exported edition at normal and enlarged text sizes. Use a keyboard to follow controls. Inspect images with text alternatives and ensure charts or tables retain meaning when colors are not available. For long tables, a mobile reader may need a different presentation rather than tiny type.
Proof the finished artifact
A source document is not the release. Check the final website page, delivered email, ebook file, or printed proof. Layout changes can introduce broken links, clipped text, incorrect page breaks, or missing labels. Keep a version number and a release owner so the team knows which file was approved.
Make this now: production proof sheet
Final URL/file • version • text and image rights • keyboard and mobile review • headings and alternatives • links • captions • disclosures • final proof approver • release time.
Next guide: Make an archive that works for readers ↗