WP-C: Web content development

Web content development

This domain tests how you turn editorial intent into structured, accessible, maintainable web content. WP-C candidates should know the difference between a content model and a page layout, and should choose markup and delivery patterns that survive redesigns, translation, and search.

Core rules

• Model content as fields (title, summary, body, image, taxonomy), not one rich-text blob; fields enable validation, reuse, and structured data.
• Use semantic HTML: one h1 per page, ordered headings, lists for lists, button for actions, a for navigation.
• Meet WCAG 2.2 AA basics: text alternatives, visible labels, 4.5:1 contrast for normal text, keyboard operability, visible focus.
• Serve responsive images with srcset/sizes and modern formats plus fallbacks; set width and height to limit layout shift.
• Keep URLs stable; use canonical tags, unique titles and meta descriptions, and structured data only where it matches visible content.
• Separate content from presentation so templates can change without re-authoring.

Worked example

A team wants a team-member card: photo, name, role, short bio, and a link to a profile page. The weak approach is one rich-text field where editors paste an image and type a heading. The better approach is a content type with image, name, role, bio, and profile-reference fields. The template controls heading level, image variants, and alt text derived from the name; editors add meaningful alt text only when the photo conveys information. Reasoning: structured fields enforce consistency, make the card reusable in listings, and let the profile page pull the same data.

Traps

• Using images of text or unlabeled icon buttons.
• Skipping heading levels because the design looks right.
• Hardcoding content in templates, which breaks translation and reuse.
• Keyword-stuffing meta descriptions or adding schema for invisible content.
• Shipping images without dimensions, causing layout shift.