Revivalife Church — Visual Brand Design System

Revivalife Church

Visual Brand Design System

A visual-first brand guide for a warm, sacred, cinematic, bilingual church experience. The system uses the correct palette, the agreed display/body fonts, and the Style Script font shown in your reference.

Style Script Cinzel Inter No random red
Welcome Home
A House Where Faith Comes Alive

Sunday worship, community, prayer, and the Word with clarity for English and Bahasa Indonesia visitors.

Plan Your VisitWatch Sermons
01

Brand Foundation

Brand Essence

Revivalife is a spiritual home: warm, reverent, modern, and deeply human. The design should feel like light entering a sacred room, not like a generic church template.

Warm

Human faces, generous spacing, welcoming language, natural rhythm.

Sacred

Deep navy, editorial serif, restrained yellow light, quiet authority.

Clear

Practical paths: service time, language, location, visit CTA.

02

Personality Matrix

The tone is cinematic but not theatrical, premium but not cold, spiritual but not old-fashioned.

Reverent

Large Cinzel titles, calm layouts, deep blue structure.

Inviting

Style Script appears as a human, handwritten welcome.

Useful

Inter keeps navigation, forms, language selector, and CTAs readable.

03

Visual Positioning

The brand should sit between a contemporary church, a refined editorial magazine, a cinematic worship platform, and a warm community house.

Church

Worship, prayer, community.

Editorial

Scale, spacing, typographic discipline.

Cinematic

Light, depth, atmosphere, motion.

Community

People-first content and simple next steps.

04

Art Direction Concept

Light Within the House. Every page should feel like a sacred interior warmed by light: ivory surfaces, deep blue structure, yellow accents, real photography, and gentle motion.

Light Within

The creative rule

Design everything as if light is moving through a living spiritual community.

05

Moodboard Logic

References should come from worship photography, parchment tones, editorial magazine pacing, architectural light, soft film grain, evening blue, and gold illumination.

Evening BlueCinematic depth
Ivory PaperQuiet warmth
Yellow LightSpiritual accent
SandHuman softness
06

Logo System

Use the full logo in the header, footer, hero, giving, and downloadable materials. Use the mark for favicon, mobile header, social avatar, and loader.

REVIVALIFE Church

Primary logo preview zone

R

Mark / icon preview zone

Logo image URLs

Paste the actual URLs from your original code into these CSS variables or directly into the img tags. I cannot see those original links in the current message thread.

--logo-primary:url("PASTE_PRIMARY_LOGO_URL_HERE");
--logo-light:url("PASTE_LIGHT_LOGO_URL_HERE");
--logo-dark:url("PASTE_DARK_LOGO_URL_HERE");
--logo-mark:url("PASTE_MARK_URL_HERE");
07

Logo Clear Space

Minimum clear space equals the height of the mark or the capital height of the wordmark. The logo should never touch navigation, buttons, page edges, or image noise.

Desktop

Minimum 32px breathing room around the full logo.

Mobile

Minimum 18px breathing room; use the mark when space is tight.

08

Incorrect Logo Usage

Do not stretch, recolor randomly, add heavy shadows, rotate, outline, or place the logo over busy images without a dark overlay.

Do

Use on ivory, navy, or clean image overlays.
Keep proportions intact.

Don’t

No random color changes.
No cheap drop shadows or distortion.
09

Color

Color System Overview

The correct system is ivory, cloud, warm white, Revival Blue, Deep Navy, Revival Yellow, and warm earth neutrals. Red is not a brand color. It is only for error, urgent, or live states.

Foundation

Ivory / Cloud / Warm White

Structure

Revival Blue / Deep Navy

Light

Revival Yellow used sparingly.

10

Primary Palette

These are the core colors. Keep this disciplined.

Revival Blue#123C69
Deep Navy#071B33
Revival Yellow#F2C94C
Ivory#F8F3E8
Cloud#F5F7FA
Warm White#FFFDF8
11

Secondary Atmosphere Palette

These support photography, page rhythm, hover states, and quiet transitions.

Sand#E7D8C4
Stone#C9C2B8
Warm Gray#8B8378
Soft Blue#DCE8F3
Mist Blue#EEF5FA
Charcoal#1F252B
12

Color Usage Ratio

Use the palette like an editorial system, not decoration.

60% neutrals · 25% blues · 10% photo atmosphere · 5% yellow · less than 1% red for alerts only.

13

Background Rules

Use ivory and warm white as the page base. Use deep navy for worship, livestream, sermons, footer, and emotional emphasis.

Light editorial sections

For welcome, service times, ministries, and forms.

Dark cinematic sections

For worship, sermon feature, video, footer, and prayer.

14

Typography

Typography System

The script font is now explicitly the Google Font shown in your reference: Style Script. The full system is Style Script, Cinzel, and Inter.

Style Script

Used for emotional welcome lines and sacred warmth.

Cinzel gives the brand sacred editorial authority
Inter is the usability anchor for body copy, navigation, bilingual content, forms, cards, labels, buttons, and information panels.
15

Typography Hierarchy

Use dramatic contrast in scale, but keep line-height and spacing controlled.

Welcome Home
Experience Revival in Christ

A church family where worship, the Word, and community come alive.

16

Style Script Rules

Style Script is a warm accent, not the main voice. It should feel like a personal invitation.

Use it for

Welcome Home

You Belong Here

Never use it for

Navigation, paragraphs, forms, schedules, legal text, buttons, or long bilingual content.

17

Cinzel Rules

Cinzel gives structure, dignity, and sacred visual authority. Use uppercase carefully and add tracking when needed.

A House of Worship and Community
18

Inter Rules

Inter carries the practical experience. It should be clean, calm, and never over-designed.

Navigation

Medium to bold. Compact. Clear labels.

Body

16–18px with generous line-height.

Forms

Labels, helper text, placeholders, validation.

19

Type Pairing Logic

Style Script = spirit and warmth. Cinzel = sacred authority. Inter = clarity and function.

Grace in Motion

THE WORD, WORSHIP, AND COMMUNITY

One section should never need more than these three voices.

20

Layout

Grid System

Use a 12-column desktop grid, 6-column tablet grid, and 4-column mobile grid.

Desktop: 1200–1320px max width with 24–32px gutters.

21

Spacing System

Use an 8px rhythm with generous section padding. The page should breathe.

32px

Component interior

64px

Small section gap

96px

Major rhythm

160px

Hero / chapter space

22

Layout Rhythm

Avoid stacked generic Elementor blocks. Use quiet intro, cinematic expansion, community warmth, practical information, and final invitation.

Quiet

Editorial welcome and mission.

Cinematic

Worship/video/sermon moments.

Practical

Times, location, language, contact.

23

Photography Direction

Use real worship, families, prayer, youth, community, pastors, and auditorium atmosphere. No fake stock imagery.

24

Image Treatment

Use soft contrast, warm highlights, deep navy overlays, subtle grain, and controlled radius.

Overlay recipe

linear-gradient(
rgba(7,27,51,.58),
rgba(7,27,51,.38)
)
25

Video Direction

Video should be cinematic, slow, compressed, muted by default, and supported by a fallback image.

Use for hero, worship atmosphere, sermon preview, livestream, and ministry highlights.

26

Motion

Motion Direction

Motion should feel like breath, light, and presence: slow fades, soft parallax, image reveals, and staggered text.

Fade Up

Subtle, 16–32px movement.

Image Reveal

Clip-path or mask reveal.

Parallax

5–12% movement only.

27

GSAP Animation Rules

Use GSAP for premium storytelling, not gimmicks. Animate hierarchy, not everything.

duration: 0.8–1.4s;
ease: "power3.out" / "expo.out";
stagger: 0.06–0.14s;
movement: 16–48px max;
28

WebGL Atmosphere Rules

WebGL should create subtle light fields, dust, glow, or blue/yellow atmosphere. It must never fight readability.

Subtle Light
Not a gimmick
29

Web + UI

Header System

The header must be premium, calm, and useful: logo, nav, language selector, and primary CTA.

AboutSundaysSermonsEvents
ENID
Plan Visit
30

Navigation System

Use clear labels. No overloaded menu. No clever wording.

HomeAboutSundaysMinistriesSermonsEventsGiveContact
31

Language Selector

The language selector is a real UI component, not an afterthought. It must remain visible on desktop and mobile.

Desktop

ENID
Menu
ENID
Visit Us Sunday
32

Button System

Buttons should be confident but not loud. Primary on light = blue. Primary on dark = yellow.

Plan Your Visit Learn More
Join Sunday Watch Sermons
33

CTA Hierarchy

One primary path per page. Do not make every CTA the same weight.

Primary

Plan Your Visit

Secondary

Watch Sermons

Tertiary

Contact / Prayer

34

Card System

Cards should feel editorial, image-led, and calm. Use them for ministries, sermons, events, service times, and leaders.

Youth

A space for young people to grow in faith.

Prayer

Care, support, and spiritual covering.

Worship

Gathering around presence and praise.

35

Icon System

Use minimal line icons with 1.5–2px stroke. No mixed icon packs.

Prayer

Home

Community

Next Step

36

Homepage Section System

The page should be built from a designed system: hero, welcome, service times, about, worship, ministries, sermons, events, leadership, next steps, giving, location, prayer, footer.

HeroWelcomeService TimesAboutWorshipMinistriesSermonsEventsFooter
37

Hero Section Rules

The hero should be cinematic and immediate: video/image, navy overlay, Style Script line, Cinzel headline, Inter copy, two CTAs, language-aware text.

Welcome Home
Experience Revival in Christ

A church family where worship, the Word, and community come alive.

Plan Your VisitWatch Sermons
38

Service Times

This must be highly usable: when, where, language, children/youth, parking/access, and visit CTA.

SUN
10

Sunday Worship

10:00 AM · English / Bahasa support · Kids available

Location

Address, map, parking details, first-time visitor instructions.

39

Ministry Cards

Ministries should feel alive, not like admin categories.

Kids

Safe, joyful, faith-building environment.

Youth

Belonging, discipleship, and leadership.

Community Groups

Life together beyond Sunday.

40

Sermon System

Sermons should feel like a media library, not a random YouTube embed dump.

Featured Sermon

Speaker · Date · Category · Watch / Listen CTA.

41

Events System

Events need date, title, time, location, short description, and CTA.

24
JUN

Prayer Night

7:00 PM · Main Auditorium

30
JUN

Youth Gathering

6:30 PM · Youth Room

42

Giving Section

Giving should feel trustworthy and spiritual, not transactional.

Generosity

Give with peace and purpose

Use a calm explanation, secure CTA, and optional scripture-led support.

Give Securely
43

Footer System

The footer should be deep, calm, complete, and useful.

44

Forms System

Forms should be spacious, trustworthy, and accessible.

Your name
How can we pray for you?
45

Bilingual Content Rules

Support English and Bahasa Indonesia cleanly. Do not randomly mix languages in the same hierarchy unless intentional.

English

Plan your visit this Sunday.

Bahasa Indonesia

Rencanakan kunjungan Anda hari Minggu ini.

46

Accessibility Rules

Strong contrast, readable text, keyboard navigation, alt text, video fallback images, and reduced-motion support are mandatory.

Contrast

No yellow body text on white.

Motion

Respect prefers-reduced-motion.

Language

Selector must have labels.

47

Responsive Rules

Desktop can be immersive. Tablet should simplify. Mobile must prioritize logo, menu, language, service time, CTA, location, contact.

Desktop / Tablet
Mobile

Stacked, clear, fast.

48

Elementor Build Rules

Set global colors, global fonts, buttons, section padding, container widths, card styles, forms, header, and footer before building pages.

Global FontsGlobal ColorsReusable CardsHeader TemplateFooter Template
49

Component Naming

Keep components reusable and easy to maintain.

Header / Main

Hero / Cinematic

Card / Ministry

Card / Sermon

CTA / Primary

Language Selector

50

Motion Components

Use a limited motion kit so the page feels designed, not chaotic.

Fade Up

Opacity 0→1, Y 24px, .9s.

Image Reveal

Clip-path, 1.2s, expo.out.

Stagger

0.08s between items.

51

Texture & Atmosphere

Texture should be felt, not seen loudly: film grain, paper tone, blue haze, yellow light leak at 3–8% opacity.

Light Leak

Paper Ivory

Blue Haze

52

Border & Shadow

Use soft borders and atmospheric shadows. Avoid heavy black shadows.

Border

1px solid rgba(18,60,105,.10)

Glow

Only in dark worship sections.

53

Design Tokens

Use these tokens inside Elementor custom CSS or the theme stylesheet.

:root {
  --revival-blue:#123C69;
  --deep-navy:#071B33;
  --revival-yellow:#F2C94C;
  --ivory:#F8F3E8;
  --cloud:#F5F7FA;
  --warm-white:#FFFDF8;
  --sand:#E7D8C4;
  --stone:#C9C2B8;
  --warm-gray:#8B8378;
  --soft-blue:#DCE8F3;
  --mist-blue:#EEF5FA;
  --charcoal:#1F252B;
  --danger-red:#C83A32;
  --font-script:"Style Script", cursive;
  --font-display:"Cinzel", serif;
  --font-body:"Inter", sans-serif;
}
54

Do / Don’t Summary

The system must stay disciplined. Warm, sacred, cinematic, useful.

Do

Use Style Script only as an accent.
Use Cinzel for sacred hierarchy.
Use Inter for usability.
Keep language selector visible.
Use real worship photography.

Don’t

Do not introduce random red.
Do not use generic gradient blobs.
Do not over-animate.
Do not hide practical information.
Do not build messy one-off Elementor styling.