Interactive case study
Active — 2026 build window

Pressdeck

WordPress Operations & Delivery Dashboard

A WordPress development cockpit: live client-site checks, real Lighthouse Core Web Vitals runs, SEO and accessibility auditors, an ACF Flexible Content theme generator, an SFTP deploy runner, and migration checklists.

Headline outcome
Built the tool a WordPress developer reaches for between the design file and the production push.
Business Outcome: Compressed the WordPress delivery loop — audits, performance runs, theme scaffolds, and SFTP deploys — into one tool with one-click checks.
25
Audit Checks Per Site
9
ACF Block Layouts Generated
18/18
E2E Suite Green
Node.js 22LighthousePHPACFSFTPPWA
Verified Project Visual
Pressdeck overview with site checks, audit scores, and Core Web Vitals rings
Click to expand high-res screenshot

Project snapshot

Production
Duration
Active — 2026
Why it matters
Every module operates on real targets: audits fetch and parse live pages, vitals run real Chrome, and the deploy runner speaks actual SFTP with dry-run safety.
Role focus
  • System architecture design
  • Lead fullstack engineering
  • AI automation workflow routing
  • Containerized security isolation
  • High-availability infrastructure tuning
Overview

Why this system had to exist

Professional WordPress work is a loop: convert a design into a theme, wire ACF Flexible Content, audit SEO and accessibility, chase Core Web Vitals, deploy over SFTP to managed hosting, and migrate or troubleshoot when things move. Each step usually means a different tool — browser extensions, online checkers, an FTP client, a notes app for the migration checklist. Pressdeck collapses that loop into one dashboard where the checks are real and the outputs are usable artifacts.

Moment 01

A WordPress development cockpit: live client-site checks, real Lighthouse Core Web Vitals runs, SEO and accessibility auditors, an ACF Flexible Content theme generator, an SFTP deploy runner, and migration checklists.

Moment 02

Every module operates on real targets: audits fetch and parse live pages, vitals run real Chrome, and the deploy runner speaks actual SFTP with dry-run safety.

Moment 03

Compressed the WordPress delivery loop — audits, performance runs, theme scaffolds, and SFTP deploys — into one tool with one-click checks.

Stage 1 of 5
Continue
Problem

What was breaking down

The hard part was making every promise operational rather than cosmetic. Public performance APIs rate-limit aggressively, so vitals had to run locally. SEO and accessibility checks had to parse real rendered HTML, not guess. The theme generator had to emit PHP that activates cleanly — templates, enqueue logic, and ACF field groups registered in code so fields ship with the theme instead of drifting in a database export. And the deploy runner had to be safe by default: validated targets, key-only auth, and a dry-run manifest before anything touches a server.

Moment 01

Performance Testing

Rate-limited online checkers

Moment 02

Theme Start

Hand-copied boilerplate per client

Moment 03

Deploys

Manual FTP client sessions

Stage 2 of 5
Constraint map
Solution

The breakthrough and implementation path

I built a Node 22 backend with a site registry and live checkers, a local Lighthouse pipeline with per-URL history, SEO and accessibility auditors producing scored findings, and a theme generator that writes a complete starter theme — nine Flexible Content block layouts, an FAQ block that emits FAQPage structured data, performance and accessibility defaults — zipped for upload. Deploys go over SFTP with per-site config, a connection test, and a dry-run mode; migrations run as persisted checklists built from field-tested runbooks. The interface shares its design system with my Opsdeck command center and installs as a PWA.

Moment 01

Local-first beats API-first for developer tooling. Running Lighthouse in headless Chrome on my own machine removed quotas, kept results private, and made history trivial to store. The same principle shaped the auditors — fetching and parsing pages directly means the findings list reflects exactly what a crawler sees, including JSON-LD schema types, canonical tags, heading structure, and alt-text coverage.

Moment 02

Site Registry + Live Checkers

Moment 03

Local Headless-Chrome Lighthouse

Stage 3 of 5
Build system
Results

Before vs after, without the clutter

Outcome metrics stay visible while comparison details are compressed into large readable cards instead of long stacked panels.

Before

Performance Testing

Rate-limited online checkers

After

Optimized resolution

Unlimited local Lighthouse with history

Stage 4 of 5
Measured impact
Architecture

Layered architecture with one consistent layout

Explore the operating layers and the shipped feature set in the same wider content frame used across the full case study.

Active layer

Site Registry + Live Checkers

Live site registry that detects WordPress, active theme, version exposure, SSL expiry, and latency
Ship 01

Live site registry that detects WordPress, active theme, version exposure, SSL expiry, and latency

Ship 02

Real Core Web Vitals runs via headless-Chrome Lighthouse on my own hardware — no API quotas

Ship 03

25 scored audit checks per site across SEO, JSON-LD schema, Open Graph, and static WCAG rules

Ship 04

Theme generator that outputs an installable ACF Flexible Content starter as a ready-to-upload zip

Stage 5 of 5
Architecture live