Meeting 4 visual demonstrator v0.3 — a review tool, not the production site. Final content, identity, ownership, and integrations remain PCC-controlled.
P People's Community ChurchWelcome Home
Welcome Home

A place to worship, grow, and connect.

This visual demonstrator presents a visitor-centered PCC home page: a clear welcome, useful first steps, and several ways to experience the same important information.

What is intentionally not shown as a fact: final schedules, address text, ministry leaders, event details, media links, and final brand assets. Those require PCC-approved source content or Phase II confirmation.
Welcome begins before the door.A visitor should feel oriented, invited, and able to take a useful next step.
Start here

Make the next step easy to find.

The first release should not make people hunt. It should give visitors and members a few useful choices without making the front door crowded.

Plan Your Visit

Find PCC-approved worship, location, parking, accessibility, and welcome information.

See the visit pathway

Experience Worship

Choose a message, the full worship service, or a future media-library path.

Explore worship

Connect

Discover public events, PCC auxiliaries, youth, community care, and practical ways to reach the church.

Find ways to connect

Visitor experience

From curiosity to connection.

This is an optional visual way to experience PCC—not a mandatory four-step process. Visitors can still use the menu or scroll naturally.

Direction only: the arrows are an expressive review device, not final PCC branding. They suggest forward movement and give visual learners another way into the site.
More ways to engage

Worship, events, and care—without crowding the front door.

These are supporting paths on the home page. They matter, but they should not compete with the three first-step cards above.

Worship & Media

Worship should be easy to enter.

Choose a message, a fuller worship-service experience, or a future PCC media-library path after Media Team decisions are made.

Explore Worship & Media

Events

Make opportunities easy to find.

Temporary featured opportunities, event details, and memorable PCC-owned URLs can help people respond without digging through a calendar.

See the event direction

Community Care

Keep the Food Pantry visible.

The Food Pantry has its own public role and should be easy to find—separate from About-page affiliations.

Explore Community Care

Giving

A PCC-owned path to give.

The public site should use one consistent /give destination with context, authorized Pushpay access, and a clear mail-giving alternative.

Giving changes require PCC Finance / leadership approval.
Why this matters

One simple route is better stewardship.

Consistency
Use the same PCC route across the site, email, social, slides, print, and QR codes.
Trust
Explain that the giving action remains secure and managed through PCC's authorized provider.
Accountability
Keep a clear owner for link, fund list, embed, and QR-code confirmation.
The guiding direction

A digital front door that feels like home.

Warm enough to invite people in. Clear enough to help them act. Expressive enough to help them experience PCC. Sustainable enough for PCC to care for over time.

About PCC

A clear picture of who PCC is.

About should help a visitor understand PCC's story, ministry identity, leadership, and public relationships. This is a direction page, not final PCC copy.

About PCC

Introduce the story, then let people go deeper.

Each card uses a concise intro sentence. “More…” opens a simple detail-view example rather than leaving visitors in a wall of text.

Core content

Mission & Beliefs

Use approved leadership language to explain what PCC believes and why the church exists.

More…

Core content

History & Identity

Give visitors enough context to understand PCC without turning the page into a long archive.

More…

Core content

Leadership

Introduce approved public leadership roles, current names, and photographs of the Pastor and deacons.

More…

Affiliation

ICCC

Describe PCC’s relationship concisely and link to a PCC-approved destination for more information.

More…

Affiliation

North End Foundation

Introduce the relationship in PCC’s own words, then offer a clear way to learn more.

More…

Agency partner

Greater Cleveland Food Bank

Explain the partnership concisely; the PCC Food Pantry itself remains under Community Care.

More…

About PCC

Mission & Beliefs

This page demonstrates the right pattern: a concise overview here, with final, approved PCC language supplied before launch.

What this page should do

Offer a warm, readable explanation of PCC’s mission and beliefs for someone who is still getting to know the church.

content needed

Use approved source language.

Phase II should not invent a theological statement. PCC leadership should provide or approve the wording that belongs here.

About PCC

History & Identity

A readable church story can be meaningful without becoming a document archive.

Show the story in layers.

Start with a short identity statement, key moments, and a few carefully selected images or milestones. Let visitors choose whether to keep reading.

content shaping

Keep the long history available, not dominant.

Longer source material can be shaped into a deeper page or downloadable archive after PCC approves the public story.

About PCC

Leadership

Visitors should be able to recognize the people entrusted with PCC’s public leadership.

Recommended presentation

Use current approved photographs and short role descriptions for the Pastor and deacons. Keep the page personal, current, and easy to scan.

content needed

Confirm the public roster.

Names, roles, photographs, and update responsibilities need PCC confirmation before the page becomes live.

About PCC

ICCC

This is a detail-view example for a PCC affiliation or relationship page.

Concise PCC explanation.

The production page should explain PCC’s relationship in PCC-approved language, then offer a clear destination for anyone who wants to learn more.

approval needed

Confirm wording and destination.

Before launch, PCC should approve the relationship description and any external destination link.

About PCC

North End Foundation

This is a detail-view example for a PCC affiliation or relationship page.

Keep the relationship clear.

Visitors should understand why PCC mentions the organization without being forced through a long explanation on the main About page.

approval needed

Confirm wording and destination.

Before launch, PCC should approve the relationship description and any external destination link.

About PCC

Greater Cleveland Food Bank

Show the partnership clearly while keeping PCC’s Food Pantry easy to find under Community Care.

Partnership and practical help.

The About page can explain the agency relationship. The Community Care path should take people to the practical PCC Food Pantry information they need.

approval needed

Confirm partnership wording.

PCC should confirm how this relationship is described and whether a “Learn More” destination is shown.

Connect

Practical ways to connect with PCC.

Connect is where public opportunities, PCC auxiliaries, youth, community care, contact, and the public-calendar direction come together. It should be active and owned—not a catalog of old church groups.

PCC Auxiliaries

Public-facing groups, not every committee.

Working language is “Auxiliaries.” Active groups with a public purpose may be included using a common, concise template.

See inclusion and template direction

Community care

Food Pantry

The Food Pantry should be called out as a distinct PCC outreach area. Days, eligibility, contact details, images, and owner are still PCC-confirmed content needs.

See pantry direction

Contact PCC

A form-first contact path.

Visitors can choose a reason for reaching out. In production, messages would route to PCC administration for review, response, or escalation.

Open the contact example

Events and registration

Make opportunities visible without making promises the site cannot keep.

The demonstrator shows the capability for a prominent public or member-oriented event callout, readable event URLs, and a registration path. The actual platform, capacity rules, payments, and owner remain Phase II decisions.

Example URL

peoplescommunity.org/community-day

A memorable PCC-owned URL makes event promotion easier in announcements, handouts, QR codes, and conversation.

static demonstration only

Youth

A place for young voices—with guardrails.

Youth can help shape appropriate recurring content, such as reflections, youth news, or service stories. It should not use real names, photos, or content until PCC sets adult review, consent, privacy, and ownership practices.

Member AccessPhase II feasibility

Useful enough to drive adoption; bounded enough to do safely.

The first-release concept now includes a member-access capability, but the authentication method, membership data source, administrator process, and access rules have not been selected.

Worship

More than a sermon link.

Meeting 4 clarified that PCC should consider the visitor who wants the message and the member who wants to experience the full service. The production answer depends on leadership and Media Team decisions.

Conceptual route

Watch the message

Message-focused content can help a visitor begin quickly. The current source, link pattern, and publishing cadence still require Media Team confirmation.

See media dependency

Conceptual route

Experience the worship service

Full services may serve members, homebound people, and those who want the full worship experience. PCC still needs a storage, retention, and access decision.

See media dependency

Future direction

Explore the media library

A future PCC-controlled library could support organized recordings, messages, studies, and selected clips when the operating model is sustainable.

See media dependency

Launch rule

Show only what PCC can sustain.

Do not create a fragile live-media process just to look complete on launch day. A clean, honest worship route is better than stale links or unowned video.

What remains open

Media is an operating model, not just a page.

Source of truth, workflow, publishing responsibility, storage, retention, member/public access, permissions, and fallback wording still need confirmation.

Give

One clear route for generosity.

The PCC /give route should give context, direct visitors to the authorized secure giving experience, and preserve a simple mail-giving alternative.

What the page should do

Explain, reassure, and connect.

1Give context
A short PCC-approved explanation of giving and stewardship.
2Open the secure giving experience
Use the authorized Pushpay link or embed once the current configuration is confirmed.
3Offer mail giving information
Publish only the PCC-approved mailing address and instructions.
Secure giving demonstrator

Pushpay access belongs here.

This is a visual placeholder for a future approved Pushpay iframe or embedded widget. It is intentionally not a live embedded payment form.

Default fund, embed configuration, and mail address require PCC confirmation.

v0.3 review lens

This refinement applies the July 2 visual-direction changes while keeping operational dependencies clearly labeled.

refinedThe header now keeps only the five public navigation items and Plan Your Visit.
refinedFeatured Opportunity is shown as a temporary, closable active-state example—not a permanent homepage section.
refinedHome now uses three primary entry cards; Worship & Media, Events, and Community Care appear as supporting cards later on the page.
plannedSearch and Member Access are still represented, but live in contextual areas: Connect and the footer.
pendingCalendar source, content owners, Media Team model, final brand system, authentication, real forms, and real registrations still require decisions.