Concept
Citywire email, run as production.
A sponsored campaign from the HTML arriving to the report going out. One shell for four titles, one event across four sends, every email compiled from one library and render-checked.
Three streams of Citywire email production: the commercial send, the editorial shell every title runs on, and one event across its calendar.
①Campaign workflow
The Solus
A sponsored campaign, received as HTML, rebuilt, proofed, sent and reported.
Open the journey →
②One shell, four titles
The Daily
One editorial shell, four titles, one accent. The colour never changes between them.
Open the journey →
③One event, four emails
The Retreat
One event on a fixed calendar. Invitation, confirmation, the day before, thank you.
Open the journey →
Compare versions
The previous proof beside the current one, with the numbered change list the sponsor saw.
Compare on The Solus →Render matrix
Five clients, light and dark, from real emulated renders. Outlook captioned as a structure check.
See the matrix →View source
The table HTML of every email, with its weight, images, links and checks.
Read the source →These emails are compiled, checked and proofed on a platform I built.