Editorial brand experience
A recognizable Daily Promise masthead, large editorial imagery, restrained typography, family context, and a consistent invitation to receive free encouragement.
Own brand / editorial website / custom CMS
A family-led devotional website connecting personal writing, author profiles, email subscriptions, reader tools, voluntary giving, and a custom publishing system.
Public homepage: the Daily Promise identity, a free devotional invitation, and the family-led brand.
THE BRIEF
Daily Promise needed to feel like a place to read and return to, not just a signup form. Mandi and I share encouragement through writing, worship, and prayer. The website needed to introduce us personally, give devotional content a clear reading structure, make the free email invitation easy to find, and keep optional support separate from access to the writing.
MY APPROACH
I combined a quiet, photo-led editorial design with a React and TypeScript front end and a Firebase publishing foundation. The public experience covers discovery, reading, authors, subscriptions, and support. Behind it, the source includes protected content tools for articles, media, page editing, and editorial settings, so routine publishing does not depend on changing website code.
PROJECT SCOPE
A recognizable Daily Promise masthead, large editorial imagery, restrained typography, family context, and a consistent invitation to receive free encouragement.
Archive search, theme navigation, sorting, individual article routes, readable article templates, adjustable reading size, and audio presentation where an audio file is available.
Distinct author profiles, article-author presentation, guest-author slots, and editorial assignment settings. Planning tools are separate from email scheduling and delivery.
Subscription forms in the homepage, reading, and site-wide experience, with signup-source context stored alongside the subscriber record.
Firebase-backed article records, rich-content editing, image metadata, draft and published states, page revisions, and protected editorial administration.
A separate giving experience with one-time or monthly choices, selectable and custom amounts, clear disclosures, and continuation to an external contribution-review page.
THE EXPERIENCE
Meet the brand and the people behind the encouragement.
Explore the devotional archive and the article reading experience.
Choose the free email subscription for an ongoing connection.
Optionally contribute without making giving a condition of access.
01 / PROJECT DETAIL
Daily Promise is something Mandi and I share, so the site introduces real people rather than an anonymous stream of content. Author profiles, family photography, and the about page give the writing a human context. Thomas and Mandi remain distinct voices within the same brand.
The reading implementation includes category and keyword discovery, chronological sorting, individual article pages, reading-size controls, and audio when a recording is attached. These are capabilities of the publishing experience, not a claim that every article currently includes audio or that the entire historical writing archive is published on this website.
02 / PROJECT DETAIL
The implementation separates draft and published article content, stores article metadata and image descriptions, and sanitizes rich article HTML before public presentation. The source also includes media management, page editing, revision records, author settings, and protected administrative routes.
Editorial planning and newsletter acquisition are kept distinct. The website can record a subscriber and where the signup originated, while the editorial calendar helps organize contributors. Neither is presented here as proof of an automatic email-send schedule or an end-to-end delivery result.
03 / PROJECT DETAIL
The public website says plainly that the devotionals remain free whether or not someone gives. The support page gives one-time and monthly choices their own space, with selectable amounts, a custom amount field, practical disclosures, and a separate review step before payment details are entered.
That keeps the reading relationship and the financial choice understandable. The portfolio captures show the public interface only. No donation was submitted, no subscriber was added, and no private reader, supporter, or administrative records are shown as part of this case study.
SELECTED SCREENS
HAVE SOMETHING IN MIND?