Skip to main content
Visual Arts & DesignWeb Polish29 lines

Editorial Web Design

Design accessible long-form articles with readable typography, a responsive editorial grid, intentional media treatment and usable article navigation.

Quick Summary9 lines
Start with representative article content: a long title, byline and date, section headings, links, a figure and caption, a quotation, and the longest table or code block the template supports. Identify the reading order before choosing columns. Use semantic headings and landmarks, and preserve the article's logical sequence when optional visual material shifts location.

## Key Points

- [W3C WCAG reflow guidance](https://www.w3.org/WAI/WCAG21/Understanding/reflow)
- [W3C text spacing guidance](https://www.w3.org/WAI/WCAG22/Understanding/text-spacing.html)
- [HTML figures and captions](https://html.spec.whatwg.org/multipage/grouping-content.html#the-figure-element)
skilldb get web-polish-skills/editorial-web-designFull skill: 29 lines
Paste into your CLAUDE.md or agent config

Editorial Web Design

Start with representative article content: a long title, byline and date, section headings, links, a figure and caption, a quotation, and the longest table or code block the template supports. Identify the reading order before choosing columns. Use semantic headings and landmarks, and preserve the article's logical sequence when optional visual material shifts location.

Build the reading surface

Choose a type scale and line measure that work with the actual font, language and content. Test a deliberately long title and unbroken string. Keep prose as one readable primary flow on narrow screens. Let columns serve distinct purposes such as a contents list or supplementary notes at larger sizes. Keep the primary article order in the DOM and avoid CSS reordering that makes reading and focus order diverge. Make table and code overflow local, with a usable keyboard path where needed.

Use figures and visible captions when media needs explanatory text, and provide an appropriate text alternative when it conveys information. Give video captions or a transcript as required for the content. Use responsive image sources and known dimensions to limit shifting as assets load. Check that optional illustrations and decorative separators do not interfere with headings or announce redundant descriptions.

Verify reading and navigation under stress

Give the article a clear heading hierarchy and useful anchor links for long sections. Ensure sticky headers do not obscure the destination, focus or footnote target. Footnotes should support returning to the reference. At a narrow viewport, enlarged text and user-adjusted text spacing, look for clipped elements, collapsed labels and horizontal scrolling in the prose. Test keyboard traversal, the contents list and a long article with delayed images or fonts. If print or PDF is in scope, verify it separately using a real article.

Record the chosen width, breakpoints, tested content and screenshot comparisons alongside behavior. Treat the reference image as visual intent and record responsive decisions where the reference only shows one size. Keep any required correction traceable to the article region and observable reading problem.

References and rights

Original SkillDB instructions under LicenseRef-SkillDB-Content. References were checked 2026-11-13 and used for technical verification.

Install this skill directly: skilldb add web-polish-skills

Get CLI access →

Related Skills

Form Elements

Unify all form elements — inputs, selects, textareas, checkboxes, toggles, radio buttons, file uploads, date pickers, and form layouts — into a consistent, accessible system. Trigger when forms look different across pages, upload buttons don't match, or form validation styling is inconsistent.

Web Polish•408L

Modal Dialog System

Unify all modals, dialogs, drawers, sheets, and overlay patterns across a website into a single consistent system. Trigger when modals look different across pages, close buttons don't match, overlays have different opacity, or dialog behavior is inconsistent.

Web Polish•317L

Navigation Patterns

Fix inconsistent navigation patterns — mismatched headers, footers, sidebars, breadcrumbs, tab bars, and mobile menus. Establish unified navigation components that work across all pages. Trigger when nav "looks different on different pages," active states don't match, or mobile menu is broken/missing.

Web Polish•318L

Progressive Web App and Offline Behavior

Add or repair a web app manifest, install experience and service worker offline behavior. Verify cache policy, updates, multiple tabs and signed-out data handling.

Web Polish•29L

Reference-Based UI Implementation Verification

Translate a supplied screenshot or design into a responsive implementation and verify matching layout, typography, spacing, assets and interaction at representative viewports.

Web Polish•29L

Responsive Repair

Fix broken responsive layouts in a vibecoded website — content overflowing on mobile, misaligned grids, missing breakpoint handling, touch targets that are too small, and navigation that doesn't adapt. Trigger when things "break on mobile," "look bad on tablet," or "don't resize properly."

Web Polish•301L