Plan Your Visit
Find PCC-approved worship, location, parking, accessibility, and welcome information.
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.
The first release should not make people hunt. It should give visitors and members a few useful choices without making the front door crowded.
Find PCC-approved worship, location, parking, accessibility, and welcome information.
Choose a message, the full worship service, or a future media-library path.
Discover public events, PCC auxiliaries, youth, community care, and practical ways to reach the church.
This is an optional visual way to experience PCC—not a mandatory four-step process. Visitors can still use the menu or scroll naturally.
These are supporting paths on the home page. They matter, but they should not compete with the three first-step cards above.
Choose a message, a fuller worship-service experience, or a future PCC media-library path after Media Team decisions are made.
Temporary featured opportunities, event details, and memorable PCC-owned URLs can help people respond without digging through a calendar.
The Food Pantry has its own public role and should be easy to find—separate from About-page affiliations.
The public site should use one consistent /give destination with context, authorized Pushpay access, and a clear mail-giving alternative.
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 should help a visitor understand PCC's story, ministry identity, leadership, and public relationships. This is a direction page, not final PCC copy.
Each card uses a concise intro sentence. “More…” opens a simple detail-view example rather than leaving visitors in a wall of text.
Use approved leadership language to explain what PCC believes and why the church exists.
Give visitors enough context to understand PCC without turning the page into a long archive.
Introduce approved public leadership roles, current names, and photographs of the Pastor and deacons.
Describe PCC’s relationship concisely and link to a PCC-approved destination for more information.
Introduce the relationship in PCC’s own words, then offer a clear way to learn more.
Explain the partnership concisely; the PCC Food Pantry itself remains under Community Care.
This page demonstrates the right pattern: a concise overview here, with final, approved PCC language supplied before launch.
Offer a warm, readable explanation of PCC’s mission and beliefs for someone who is still getting to know the church.
Phase II should not invent a theological statement. PCC leadership should provide or approve the wording that belongs here.
A readable church story can be meaningful without becoming a document archive.
Start with a short identity statement, key moments, and a few carefully selected images or milestones. Let visitors choose whether to keep reading.
Longer source material can be shaped into a deeper page or downloadable archive after PCC approves the public story.
Visitors should be able to recognize the people entrusted with PCC’s public leadership.
Use current approved photographs and short role descriptions for the Pastor and deacons. Keep the page personal, current, and easy to scan.
Names, roles, photographs, and update responsibilities need PCC confirmation before the page becomes live.
This is a detail-view example for a PCC affiliation or relationship page.
The production page should explain PCC’s relationship in PCC-approved language, then offer a clear destination for anyone who wants to learn more.
Before launch, PCC should approve the relationship description and any external destination link.
This is a detail-view example for a PCC affiliation or relationship page.
Visitors should understand why PCC mentions the organization without being forced through a long explanation on the main About page.
Before launch, PCC should approve the relationship description and any external destination link.
Show the partnership clearly while keeping PCC’s Food Pantry easy to find under Community Care.
The About page can explain the agency relationship. The Community Care path should take people to the practical PCC Food Pantry information they need.
PCC should confirm how this relationship is described and whether a “Learn More” destination is shown.
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.
Working language is “Auxiliaries.” Active groups with a public purpose may be included using a common, concise template.
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.
Visitors can choose a reason for reaching out. In production, messages would route to PCC administration for review, response, or escalation.
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.
A memorable PCC-owned URL makes event promotion easier in announcements, handouts, QR codes, and conversation.
static demonstration only
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.
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.
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.
Message-focused content can help a visitor begin quickly. The current source, link pattern, and publishing cadence still require Media Team confirmation.
Full services may serve members, homebound people, and those who want the full worship experience. PCC still needs a storage, retention, and access decision.
A future PCC-controlled library could support organized recordings, messages, studies, and selected clips when the operating model is sustainable.
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.
Source of truth, workflow, publishing responsibility, storage, retention, member/public access, permissions, and fallback wording still need confirmation.
The PCC /give route should give context, direct visitors to the authorized secure giving experience, and preserve a simple mail-giving alternative.
This is a visual placeholder for a future approved Pushpay iframe or embedded widget. It is intentionally not a live embedded payment form.
This refinement applies the July 2 visual-direction changes while keeping operational dependencies clearly labeled.
This is an interaction demonstration, not an approved operational page. The finished site should use PCC-confirmed, maintained details.
This search only finds content represented inside this static demonstrator. A production PCC site-wide search remains a Phase II platform and content decision.
PCC expects member access to encourage early adoption. This demonstrator shows the intent, not a functioning member portal.
Meeting 4 did not settle the public-calendar source of truth or the relationship to PCC's internal master calendar.
Each public entry should follow a lightweight template: name, short purpose, public contact route, optional meeting information, and a named content owner.
The Food Pantry should be distinct from PCC's affiliations. It needs concise, practical information that people can use.
The Media Team should confirm the source of truth, live workflow, recording location, retention practice, who updates links, public/member access rules, and the fallback message when no live stream is available.
This does not submit or collect data. In Phase II, approved messages could route to PCC's administrative assistant for review, response, or escalation.
Production requirements still include secure configuration, spam protection, inbox/assignment rules, and a timely PCC response process.
This demonstrates how a public or member-oriented event could be called out. It is not a functioning registration system.
The team wants youth represented. The safest starting pattern is a youth-owned content area that has adult review and does not publish real youth details by default.
ICCC, North End Foundation, and Greater Cleveland Food Bank can be represented with short PCC-approved descriptions and clear external destinations.
For the demonstrator, this stays a visual placeholder. The production page should use PCC's approved Pushpay configuration and preserve PCC control of the URL, embed settings, funds, and QR code.