Awana About structure
Philosophy lead, 3B discipleship model, age pathways, club-night breakdown, proof, implementation CTA, scale, membership support, and resources.
Source Evidence
What shaped the system
The corrected reference informs structure and seriousness; Bible Blast assets and copy inform color, voice, audience, pathway naming, and CTAs.
Bible Blast brand colors
Red, gold, blue, purple, and navy are taken from local brand context and logo-derived palette.
Local copy context
Homepage rewrite, Bible Biz pages, FAQ copy, and wireframes define families, churches, homeschoolers, Scripture memory, rhythm, and free sample CTAs.
Voice Rules
Sober ministry clarity with family warmth
Speak to the adult leader first. The design can carry warmth, but the copy should make discipleship, Scripture memory, and implementation feel clear and sustainable.
Use: Help kids know God's Word and carry it for life.
Use: Simple enough for one child. Structured enough for a church program.
Use: Help families and churches build a repeatable Scripture rhythm.
Avoid: Hype-heavy claims, childish jokes, mascot language, or unsupported statistics.
Colors
Bible Blast color roles
Keep most sections white. Use color to make decisions clear, not to fill every surface.
Action Red#d02338
Memory Gold#f6cd27
Trust Blue#30488a
Secondary Purple#7c3b8c
Ink Navy#182044
| Name | Token | Value | Use |
|---|---|---|---|
| Red action | --at-color-red | #d02338 | Primary conversion and urgent CTA moments |
| Gold highlight | --at-color-gold | #f6cd27 | Progress, memory work, small emphasis |
| Blue trust | --at-color-blue | #30488a | Navigation, secondary CTA, ministry trust, and success states |
| Purple accent | --at-color-purple | #7c3b8c | Secondary visual accent and hero atmosphere |
| Ink | --at-color-ink | #182044 | Primary text |
Gradients
Restrained, not decorative
Gradient tokens exist for complete downstream coverage, but flat white surfaces are the default. The hero uses two dark purple shades. CTA bands use dark blue and navy.
Hero
Two dark purple shades for the first viewport only.
CTA band
High-priority final action.
Card warmth
Small support panel accent.
Typography
Credible, readable, warm
The default stack is system-based for portability. It avoids comic display styles and keeps dense ministry content readable.
Help kids know God's Word.
Build a weekly rhythm families can keep.
Body copy uses generous line height, navy text, and muted support copy to keep long-form curriculum pages easy to scan.
Sample kicker
Spacing
Broad section rhythm
Use generous vertical spacing like a ministry landing page, then tighter card interiors for scan-friendly content.
Section
80px default desktop rhythm.
Card
24px interior padding.
Cluster
12px gaps between actions.
Radii
Soft but not toy-like
Small 4px
Card 8px
Pill badges only
Shadows
Low elevation
Default card
Lead form panel
Modal or overlay only
Motion
Small state motion
Use motion for hover, press, disclosure, and focus feedback. Respect reduced motion and avoid animated decorative backgrounds.
Token timing: fast 140ms, base 220ms, slow 360ms.
Imagery
Real ministry context when available
Prefer authentic home, homeschool, and church learning imagery. Until approved photography exists, use the logo and simple original support graphics.
Iconography
Simple line support
Scripture
Open book, verse, memory icons.
Rhythm
Calendar, repeat, check, progress icons.
Audience
Home, church, group, student icons.
Components
Reusable website building blocks
Components include primitive controls, navigation, feature cards, steps, status panels, forms, and website sections.
Relational ministry
Adapt the reference's relationship-first philosophy into Bible Blast language for families, homeschoolers, and church volunteers.
Scripture-rooted learning
Cards and copy should keep Bible reading, questions, memory work, and truth from God's Word at the center.
Weekly practice
Use repeatable steps and activity breakdowns to show how kids carry Scripture into life.
1
Choose a pathway
Bible Blast, Bible Biz, home, church, or homeschool.
2
Run the weekly rhythm
Read, discuss, remember, quiz, sing, encourage, and reward.
3
Use support resources
Samples, guides, partner care, and local help should be easy to find.
Applied UI
An About-page-modeled ministry slice
This composition shows the target section rhythm: philosophy, age/stage pathways, weekly activity breakdown, proof, implementation CTA, support resources, and lead form.
Bible Blast
Bible story reading, questions, Scripture memory, songs, rewards, and a repeatable weekly rhythm for families and churches.
Bible Biz
Student-driven Scripture study and weekly quizzing for older students who are ready to search God's Word for themselves.
Large group time
- Bible lesson and interactive teaching
- Worship, announcements, awards, and encouragement
Small group time
- Leader huddles, questions, and Bible discussion
- Handbook work, prayer, and personal check-ins
Group activity time
- Games, crafts, and review activities
- Adapted for the church, home, or homeschool space
86%
Reference proof pattern: the Awana About page uses an alumni statistic to build credibility. For Bible Blast, use only validated Bible Blast proof, testimonials, age ranges, group-size claims, or curriculum-duration claims.
Awana source noted in reference: Excellence in Giving Awana Alumni Study, 2020. Do not republish as a Bible Blast claim.
Implementation CTA
Wondering how Bible Blast could work in your church, homeschool, or family rhythm?
Use this dark-blue CTA band for sample requests, church implementation questions, and resource-support entry points.
Flexible scale
Use copy and components that support small homes, homeschool groups, rural churches, urban churches, and larger ministries.
Partner resources
Show getting-started guides, sample lessons, training, partner care, and local support as part of the system.
Long-term foundation
Position Bible Blast as a partner that helps draw families, foster relationships, and build Scripture memory over time.
Accessibility
Baseline requirements
Focus: visible gold and blue ring.
Forms: labels, help text, and non-color error text.
Motion: reduced-motion media query included.
Implementation Notes
Downstream usage
Use BEM or plain semantic component classes and map all values back to `--at-*` tokens. For Bricks work, recreate components with native fields where possible and reserve custom CSS for token mapping and behavior that Bricks cannot express natively.
Known Gaps
Items to validate before production
- The corrected Awana About page is used for structure only; no Awana assets, colors, logos, or photography are included.
- Available local copy included the homepage StoryBrand rewrite, Bible Biz 2, Bible Biz at Church, Bible Biz at Home, and FAQ copy.
- Typography is inferred and system-font based.
- Support artwork is original placeholder material, not final photography.
- Claims and statistics must be validated before publication.