The project
Email Studio
Buhonea’s email studio: create, preview and send campaigns with list control, history and templates — built to operate for real, not a three-screen demo.
The project
Buhonea already had website, search, panels and Super Admin. What was missing was serious email: campaigns to beta testers, internal lists, reusing a sent mail without rebuilding it. Email Studio is a private piece of the ecosystem so the team can create and send branded mail with signatures, preheader and modular content — and keep track of sends, unsubscribes and editable templates.
What they wanted
Give Buhonea an internal email studio: HTML campaigns by blocks, recipients from real lists (Beta, manual adds, miniBlog marketing), preview, send, and manage history and unsubscribes — without locking into a generic SaaS that doesn’t know their product.
The challenge
Stop improvising mails in random clients. Clear senders, signatures and alignment, inbox preheader, recipients by hand or from Beta participants, content with header/title/subtitle/description/CTA/extras, preview before send, then history, unsubscribe, editable templates, CSV export and purge of old data.
Our solution
We built Email Studio as a PHP app with login. Three big tabs: Create Mail (flow 1–5), History (sends, unsubscribes, saved mails) and Beta + Subscribers (Beta participants, manual emails, miniBlog marketing; newsletter coming). Content is block-based; images from a resent mail are reused on the server; each send is logged so you can edit and send again.
How it’s built
Three zones of the same studio: where the mail is created, where sends are controlled, and where recipient lists live.
Create Mail — the composer
Guided flow: 1) sender, 2) footer signature and alignment, 3) preheader, recipients and subject — with add-from-Beta —, 4) block content (Header, Title, Subtitle, Description, CTA, Extras), 5) preview and send. Re-editing a sent mail reuses server images and counts as a new send. The operational heart of the studio.
History — sends, unsubscribes and templates
Nothing gets lost. Sends from the studio, unsubscribed emails, and saved templates to edit, resend or delete. Maintenance: delete selected, clear, purge older than 90 days, export CSV. Real ops control — not “sent and forgotten”.
Beta + Subscribers — living lists
Three audience sources: Beta participants, emails added by hand, and miniBlog users who accepted marketing. Refresh, select and prep the next send without copy-pasting sheets. Newsletter subscribers are the next layer. Buhonea’s recipient pantry.
Colour palette
Near-black ink for the studio frame, electric violet for actions, supporting lilac, light mist background and white paper cards. Product-tool feel: clean, focused, no generic marketing noise.
-
Studio ink
#0e1016 -
Action violet
#6d5efc -
Lilac
#8b7cff -
Mist
#eef0f7 -
Paper
#ffffff
Typography
Dosis: readable on desktop for long operating sessions — clear titles, numbered steps, no fluff that slows a send.
- Aa Dosis UI copy, titles and reading
Tech stack
PHP on the server (login, send, history), HTML/CSS/JS in the block composer, HTML email templates, CSV export and unsubscribe logic. Fits the Buhonea stack: owned piece, not an alien plugin.
- PHP
- HTML5
- CSS3
- JavaScript
- SMTP / correo
- CSV
- Plantillas HTML
Result
Buhonea can email with product discipline: create, preview, send, save templates and govern lists and history from one studio. Another proof SevenApps ships large pieces inside the same ecosystem — not only the public face.