Online Platform • 2026Read time: 14 min
Case Study 01Product Design • Information Architecture • UX/UI

Selah — Designing a Digital Space for Spiritual Reflection

Selah is a personal faith and reflection platform designed for prayer, scripture, dreams, personal reflections and experiences users may want to revisit over time. The central design question wasn't simply how to store this information. It was how to give deeply personal spiritual content enough structure to remain meaningful and retrievable without making faith feel like another productivity system.

Production Build Live on Web
rocket_launchView Live Product
RoleProduct / UI/UX Designer
Scope Product Architecture · UX/UI Design · Interaction Design · Design System
PlatformResponsive Web Application
Timeline5 months

Designing Without Productivity Pressure

Many digital products use streaks, reminders, and progress metrics to encourage people to return. For Selah, those patterns could make personal reflection feel like something to keep up with or complete.

I designed Selah as a quieter place to record what matters and return to it when ready. Its structure helps people find and revisit their entries without measuring how often they reflect.

check_circleNo streaks
check_circleNo performance metrics
check_circleNo pressure to complete
Architectural Premise
“Structure should help people return to meaningful moments — not turn those moments into tasks.”
M
Product/ UI/UX Designer
selahh.app/home / selah latest version
Selah: Light mode activebedtime
Selah homepage

The Living Archive of Personal Grace

Non-linear, temporally deep, and reverently quiet. Notice the absence of notification counters, red badges, or urgency prompts.

02 • The Central Challenge

When Reflection Doesn't Behave Like a Task

Selah holds very different kinds of spiritual experiences — from a thought captured in the moment to scripture, dreams, prophecies and reflections that may gain meaning over time. The challenge was giving those experiences enough structure to remain organized, connected and retrievable without treating personal faith like a system of tasks to complete.

auto_stories
Tension 01

Reverence vs. Structure

Prayer, scripture, dreams and personal reflections need enough structure to be found and understood later. But treating every entry like conventional data risks making deeply personal content feel administrative.

arrow_forwardDESIGN RESPONSE → No streaks or completion-based progress
schedule
Tension 02

Spontaneous Capture vs. Deeper Reflection

A thought, dream or spiritual experience may need to be recorded while it is still fresh, while scripture study and deeper reflection benefit from more context and organization.

arrow_forwardDESIGN RESPONSE → Capture first, organize when needed
hub
Tension 03

Privacy vs. Connection

Individual entries can be deeply personal, yet their meaning may become clearer when revisited alongside scripture, previous reflections or experiences recorded over time.

arrow_forwardDESIGN RESPONSE → User-controlled relationships between entries
03. UNDERSTANDING THE EXPERIENCE

THE 3 REALITIES OF SPIRITUAL RECORD-KEEPING

Selah isn't designed around one fixed way of recording faith. A thought may need to be captured in seconds, scripture may become a lasting reference point, while a struggle, prayer or spiritual experience may unfold over months or years.

spaThe Meaning of “Selah” — Pause & Reflect

Selah appears throughout the Psalms and is commonly associated with a pause or moment of reflection. That idea became a guiding principle for the experience: create space to record, return and reflect without demanding constant activity.

The 3 Realities of Sacred Record-Keeping
1

Immediate Moments

A thought, dream, impression or reflection may need to be captured while it is still fresh

2

Anchoring Moments

Scripture, notes and meaningful reflections can become reference points that the user returns to repeatedly.

3

Longer Seasons

Struggles, recurring themes, prayers and other experiences may develop meaning over weeks, months or even years.

Deliberate System Rejections

DELIBERATE DESIGN CHOICES

cancelGamified Streaks

Streaks can turn consistency into an obligation and make returning after time away feel like a failure, instead Selah welcomes users back without penalizing absence

cancelKanban Workflows

Spiritual experiences don't always move predictably from “open” to “complete.” Some remain unresolved or continue developing over time.

cancelURGENCY BADGES

Notification counts and persistent warning states create pressure to respond. Instead Selah keeps the interface quiet and lets users choose when to return

cancelPRODUCTIVITY METRICS

Word counts, completion percentages and activity scores would measure participation rather than meaning. Instead progress is represented through what users record and revisit, not how much they produce

04. CONTENT ARCHITECTUREThe Living Archive

Different Content, Connected Meaning

Selah contains different kinds of spiritual records, each with its own purpose and context. Rather than treating everything as a generic note, I designed distinct content types that preserve what makes each entry meaningful. At the same time, those entries can relate to one another — allowing something recorded today to gain new context when revisited later.

01 / Collection

Content Types

Distinct spaces for capturing and revisiting different kinds of spiritual experiences.

verified01 / ITEM

Prophecies

Long-term divine commitments requiring patience and testing. Built with a “Testimonies" tab to view fulfilled prophecies

DESIGNED FOR: Long-term revisiting & fulfillment
nights_stay02 / ITEM

Dreams

Capture dreams while details are fresh, with space to add context later.

DESIGNED FOR: Capture now, interpret later
visibility03 / ITEM

Visions

Visual epiphanies, atmospheric senses, mental pictures, and acute promptings experienced during waking contemplation.

DESIGNED FOR: Recording context & significance
favorite04 / ITEM

Worship

Words of praise, song lyrics, gratitude expressions, and joy.

DESIGNED FOR: Expression & Praise
psychology05 / ITEM

Virtues

Spiritual disciplines: Reflect on qualities, lessons and areas of personal spiritual growth with tree visual.

DESIGNED FOR: Reflection on personal growth
heart_broken06 / ITEM

Struggles

Record difficult or unresolved experiences without requiring a “completed” state. Explicitly protected from forced cheerful status resolutions.

DESIGNED FOR: Processing unresolved experiences
grain07 / ITEM

Reflections

Longer-form space for thoughts that don't belong to a more specific content type.

DESIGNED FOR: Longer-form personal reflection
Notes08 / ITEM

Notes

Save Bible-study notes, sermon notes and other supporting reflections.

DESIGNED FOR: Easy access to notes database
02 / Collection

Tools & Aids

Supporting resources that help users study, connect context, and explore scripture.

menu_book01 / ITEM

Scripture

Save passages, notes and reflections that can become reference points across other entries.

DESIGNED FOR: Capturing what speaks the most to you
Map02 / ITEM

Bible Map

Explore connections between passages, themes and references across Scripture.

DESIGNED FOR: Exploration & Learning
Architectural Matrix

Why Separate vs. Why Connected

The defining architectural breakthrough of Selah is the dialectic between strict categorization and organic relational weaving.

call_splitWhy We Keep Them Strictly Separate

A dream, scripture passage, struggle and reflection aren't interchangeable pieces of content. Each has different context, meaning and ways a user may want to return to it, Giving them distinct structures preserves those differences instead of forcing every spiritual experience into one generic note format

Example: A 2022 Lament regarding bereavement is held in its sacred unresolved state—not marked “Completed” by an eager task engine.
alt_routeWHY ALLOW CONNECTIONS

Spiritual experiences don't always make sense in isolation. A reflection may relate to an earlier dream, a struggle may connect to scripture, or something recorded months ago may gain new meaning later. Connections allow users to build those relationships intentionally rather than having the system decide what their experiences mean

A dream recorded as “The Almond Tree in Winter” includes a references to Jeremiah 1:11. The dream keeps its own details and context, while the Scripture reference gives the person a passage to explore alongside it.
Living Thread Visual Schema
nights_stay
DreamRecorded Oct 14, 2021
heart_broken
StruggleEntered Jan 09, 2022
menu_book
Scripture: Isaiah 43:19Anchored Jun 22, 2023
verified
Fulfilled PromiseAnswered Nov 03, 2024
05 • CORE USER JOURNEY

Capture Now, Understand Later

Spiritual experiences don't always arrive neatly categorized. Selah separates capturing a moment from organizing it, allowing users to record something while it is fresh and add meaning or connections when they are ready.

Phase Imic

Capture the Moment

A dream, reflection, impression or thought can be recorded without first deciding exactly where it belongs or how it connects to everything else.

Low-Friction capture • Structure can wait
Phase IIfilter_vintage

Add Context

Later, the user can add context, connect scripture, choose a relevant content type or relate the entry to something recorded previously.

Organization is available, not required upfront
Phase IIIspa

Return & Reflect

Entries are presented in a quieter reading experience where the content takes priority over controls, metadata and navigation.

Content first • Reduced interface noise
Phase IVhistory

Revisit Over Time

Something recorded months or years earlier can be revisited alongside related scripture, reflections or experiences, allowing its meaning to develop over time.

Designed for continuity, not completion
06 • DESIGN EXPLORATION

Escaping the Productivity Pattern

Early exploration looked at different ways Selah could organize and encourage interaction with personal spiritual content. Two familiar product patterns offered useful ideas, but introduced behaviors that conflicted with the experience I wanted to create. This led to a third direction: a reflective archive built around capture, optional organization and revisiting over time.

DIRECTION A — EXPLOREDclose

Structured Knowledge System

The structure became too demanding during capture. Users would need to think about organization at the same moment they were trying to preserve an experience.

Trade-off

Relationships between entries, without requiring heavy categorization upfront.

What I kept

The separation of information infrastructure

DIRECTION B — EXPLOREDclose

Habit & Routine System

A routine-based model could encourage regular reflection through streaks, reminders and visible progress.

Trade-off

It made consistency itself feel like the goal, introducing performance and completion patterns that didn't fit Selah's approach to spiritual reflection.

What I kept

Gentle ways to return, without streaks or penalties for absence.

DIRECTION C — CHOSENcheck

Reflective Archive

A quieter model centered around capturing meaningful experiences, adding context when useful and returning to them over time.

Why it fit

It combines low-friction capture with meaningful organization while allowing entries to remain unfinished, unresolved or relevant for years.

Design direction

Capture · Connect · Revisit · Reflect ·

07 · KEY DESIGN DECISIONS

Four Decisions That Defined Selah

Four decisions shaped how Selah handles personal spiritual content — prioritizing low-friction capture, meaningful structure and long-term reflection over conventional engagement patterns.

DECISION 01motion_photos_on

Capture Before Categorization

Consideration: Requiring categories, tags and relationships upfront adds friction at the exact moment someone is trying to preserve a thought, dream or experience.

Decision: Let users capture the content first and add context or connections when they are ready.

DESIGN PRINCIPLECapture first · Structure can wait
DECISION 02fullscreen

No Gamified Faith

Consideration: Streaks, completion percentages and guilt-based reminders can turn consistency into a measure of spiritual performance.

Decision: Selah avoids rewarding frequency or penalizing absence. Returning after time away should feel just as natural as returning tomorrow.

DESIGN PRINCIPLEEncourage return without measuring devotion
DECISION 03graphic_eq

Different Content Deserves Different Treatment

Consideration: A dream, scripture passage, struggle and reflection may all be “entries,” but they carry different context and are revisited for different reasons.

Decision: Give each content type its own structure while maintaining a shared interaction language across Selah.

DESIGN PRINCIPLE:Shared system · Context-specific content
DECISION 04health_and_safety

Design for Revisiting, Not Completing

Consideration: Traditional software often treats information as something to process, resolve or archive. Spiritual experiences don't always have a clear completion state.

Decision: Entries can remain unresolved and still be meaningful. Selah emphasizes returning, connecting and reflecting rather than clearing an inbox.

DESIGN PRINCIPLE:Continuity over completion
08 • Iteration & Refinement

Refining the Experience

As Selah developed, the interface was refined to make navigation clearer, reduce visual noise and give different types of spiritual content more appropriate ways to be captured and revisited.

01

Navigation & Visual Hierarchy iteration

A calmer space that feels more personal
A quieter layout with clearer hierarchy and consistent iconography.
02

Interactive Tree iteration

From functional prototype to cohesive experience
Polished tree that fits into the visual style of the rest of the page
03

Scripture Reference Map

A helpful tool for Bible study
A clearer study experience with stronger hierarchy, simplified navigation and more focused space for exploring Scripture.
“Designing Selah was an iterative process of removing what didn’t serve the experience, so there would be more space for what did".
MM

09 • Selah Design System

Visual Design Tokens for Devotional Stillness

The color hierarchy deliberately shifts away from clinical high-contrast cold blacks and stark whites, settling into warm ivory, navys, and soft earthy neutrals. Inspired by biblical imagery of light, darkness, and the desert, the palette creates a sense of stillness, warmth, and reflection. These familiar, natural tones help Selah feel grounded and contemplative at first glance, while subtle contrast between light and shadow reinforces the idea of moving from quiet reflection toward clarity and spiritual growth.

01 / Typographic Foundation

3 Typefaces
AaTypeface 01

Geist

Regular 400 · Medium 500 · SemiBold 600

The primary interface typeface. Used for body copy, navigation, buttons, and descriptions to keep everyday interactions clear and easy to read.

In context

A quiet place to record what’s on your heart.

AaTypeface 02

Playfair Display

Regular 400 · SemiBold 600

The expressive typeface. Used for headings, the Selah wordmark, Scripture quotations, and reflective passages to create a contemplative tone.

In context

“In quietness and confidence shall be your strength.”

AaTypeface 03

Geist Mono

Regular 400

Used sparingly for small labels and supporting details. Its precise rhythm adds structure to the interface without drawing attention away from the content.

In context

REFLECTION · 23 SEPTEMBER 2026

02 / Color System

2 Palettes

Dark mode

4 colors

Deep Navy

#0F1220 • Background

Light Gold

#D2A55E • Button Highlights

Navy Surface

#181D30 • Hover Button

Gold

#C79654 • Accent color

Light mode

3 colors

Shoji white

#e5ded2Background

Parchment paper

#d9cebfMenu

Rich caramel

#b47d2eHighlights/Buttons

03 / Iconographic Vocabulary

1.5px Organic Stroke
Prophecies
Dreams
Visions
Worship
Virtues
Struggles
Reflection
Notes
Bible Map
Profile

Rendered with gentle stroke weights and softened organic forms, the iconography maintains a quiet, sacred clarity without appearing harsh or gamified.

04 / Component Anatomy & Archetypes

Interactive Primitives

Action States

Primary · Rich caramel
Secondary · Deep Navy
Disabled · Restrained 40% Opacity

Anxiety

2 verses

⋮

Verses about anxiety

Psalm 34:4I sought the Lord, and he answered me.
Philippians 4:6Do not be anxious about anything.
14/08/2026•Interpreting

The Almond Tree in Winter

I stood in an orchard encased in deep snow. Every tree was dead gray, but in the center, a single almond branch was covered in white blossoms.

Jeremiah 1:11 linked
Selah · Visual Design SystemA visual language for quiet reflection
10 · Design Evaluation & LearningDesign self-review

What I Reviewed and What Changed

I reviewed Selah’s capture, organization, and revisiting flows against its goal: a calm space for spiritual reflection without pressure to keep up. These are design observations and decisions, not findings from formal user testing.

01Evaluation

What I Evaluated

  • How quickly someone can capture a thought without first choosing an entry type.
  • Whether prayer, scripture, dreams, and reflections have enough structure for their different purposes.
  • Whether people can find meaning across entries without navigating a complicated filing system.
02Findings

What I Learned

  • Choosing a category before writing can interrupt a spontaneous moment.
  • One generic entry form leaves out context that matters for different kinds of spiritual content.
  • Connections between entries should support reflection without making the experience feel like a productivity tool.
03Iterations

What Changed

  • Made the visual design feel more personal and inviting, with a calmer hierarchy and presentation that better fits spiritual reflection.
  • Added Quick Note / Inbox so someone can capture what is on their heart without choosing a category first.
  • Refined interface wording and translations so prompts feel clearer, more natural, and consistent across languages.
04Future Scope

What Remains

  • Test whether new users can capture a moment and understand what to do with it later.
  • Check whether connected entries remain easy to revisit as someone’s collection grows.
  • Learn how people understand Selah’s privacy choices and what would help them feel comfortable recording personal reflections.
11 • The Final Experience

A Personal Archive That Grows With You

The final experience brings Selah's principles together: low-friction capture, content-specific structure, intentional connections and an experience designed for returning rather than completing.

Capture a Moment — image 1 of 31 / 3
Flow 01: Home page

Capture a Moment

Capture → Add what matters → Save Different entry types provide relevant structure without turning the moment into a lengthy form. Users can preserve what matters first and add deeper context when useful.

Connect Meaning — image 1 of 21 / 2
Flow 02: Visual Spiritual growth

Connect Meaning

Record → Connect → Build context Entries can gain context over time through scripture, related experiences and later developments. The original record remains intact while its wider story can continue to grow.

Revisit Over Time — image 1 of 21 / 2
Flow 03: Space for personal growth

Revisit Over Time

Return → Rediscover → Reflect Selah is designed around content remaining meaningful after it is created. Previous entries can be rediscovered and revisited without requiring them to become tasks, achievements or completed items.

Explore & Understand Scripture — image 1 of 1
Flow 04: Connecting references

Explore & Understand Scripture

Search → Explore connections → Follow references → Capture what stands out Bible Map helps users explore how passages and themes connect across Scripture. As they follow references, they can capture notes and reflections in the moment, keeping personal insight connected to what they are studying.

12• Designing Without Default Patterns
Selah demonstrates how thoughtful information architecture can bring structure to deeply personal content without losing the human experience behind it.

I added Quick Note so someone can capture a thought without choosing a category first. I also refined the language and visual design to make Selah feel more personal, while keeping structure available when someone wants to add context or connect entries.

Selah taught me to let the moment guide the structure, rather than asking someone to understand the system before they begin. The next step is to test whether people can capture, find, and revisit their reflections as easily as intended.