WP-C cheat sheet

Semantic HTML: use heading levels h1-h6 in strict order for outline structure; a page has one h1 describing the primary content, and skipping levels breaks screen-reader navigation.

Content hierarchy rule: primary message above the fold, supporting detail in the next section, and legal/footer boilerplate last; each section must be independently understandable when read out of order.

WCAG 2.2 minimum contrast is 4.5:1 for normal text and 3:1 for large text (18pt, or 14pt bold); non-text UI components and graphical objects require 3:1 against adjacent colors.

Every image needs an alt attribute: descriptive alt for informative images, alt="" for purely decorative images, and long descriptions via figure/figcaption for charts or infographics.

Link text must make sense out of context; "click here" and "read more" fail WCAG 2.4.4 because screen-reader link lists show only the link text.

Responsive design: set the viewport meta tag, use relative units (rem, %, vw) for type and layout, and reserve media queries for layout changes rather than font scaling alone.

Content inventory fields: URL, title, owner, last-modified date, page views, conversion role, and disposition (keep, update, merge, redirect, retire).

Redirect rule: a retired URL with a live equivalent gets a 301 to the closest topical match; a retired URL with no equivalent returns 410 or a 404 with helpful navigation.

Metadata: title elements should be unique and roughly 50-60 characters; meta descriptions around 150-160 characters and written as a value proposition, since search engines may rewrite them.

HTTP status classes: 2xx success, 3xx redirection, 4xx client error, 5xx server error; 301 is permanent, 302/307 temporary, 304 not modified, 410 gone.

Caching headers: Cache-Control max-age sets freshness lifetime in seconds; s-maxage overrides it for shared caches; stale-while-revalidate permits serving stale content while revalidating in the background.

ETag and Last-Modified enable conditional requests; the client sends If-None-Match or If-Modified-Since and a 304 response carries no body, saving bandwidth.

HTTPS deployment requires a valid certificate matching the hostname, a redirect from HTTP to HTTPS, and HSTS (Strict-Transport-Security) to prevent protocol downgrade.

DNS records: A maps a name to IPv4, AAAA to IPv6, CNAME aliases one name to another, MX routes mail, TXT carries verification and policy data such as SPF and DMARC.

Core Web Vitals thresholds: LCP good at 2.5 s or less, INP good at 200 ms or less, CLS good at 0.1 or less, measured at the 75th percentile of page loads.

Staging-to-production promotion: back up the database, deploy code, run schema migrations, smoke-test key templates, then verify redirects and analytics before announcing.

Log analysis triage: separate 5xx from 4xx, group by URL pattern rather than individual URL, and check whether errors correlate with a deploy timestamp or traffic spike.

Backup rule: keep at least one offsite copy, test restores on a schedule, and record recovery time objective and recovery point objective for each system.

ROI formula: (gain from investment minus cost of investment) divided by cost of investment; express as a percentage and state the time period used.

Total cost of ownership includes licensing, hosting, implementation labor, training, maintenance, and migration or exit costs, not just the purchase price.

RACI assigns each task exactly one Accountable role; Responsible does the work, Consulted gives input before, Informed is notified after.

SMART goals require Specific, Measurable, Achievable, Relevant, and Time-bound criteria; a goal lacking a measurement and a deadline is not actionable.

Budget variance = actual minus planned; a positive variance on a cost line is an overrun and should be reported as a percentage of the planned figure.

Payback period = initial investment divided by annual net cash inflow; shorter payback means faster recovery but ignores value created after breakeven.

Stakeholder map: plot influence against interest; high-influence, high-interest parties need active management, while low-influence, low-interest parties need only monitoring.

Scope change control: any new requirement is logged, impact-assessed for cost, time, and risk, approved or rejected by the sponsor, then baselined.

KPIs must be paired with a target, a data source, and a review cadence; a metric without an owner and threshold cannot drive a decision.