Plan Your Visit
Get the approved worship schedule, location, accessibility, parking, and what to expect.
This demonstrator presents a visitor-centered home page: clear first steps, a warm PCC welcome, and the things a new visitor is most likely to need without creating a crowded front door.
The first release should not ask people to hunt. It should make a small number of useful choices obvious and calm.
Get the approved worship schedule, location, accessibility, parking, and what to expect.
Find the live-worship route when available, recent services, and message-focused content.
Discover public events, ministry connections, approved community information, and practical help.
A long home page can guide the visitor naturally instead of making them decode a dense menu or a wall of content.
The first release can provide a stable, honest launch placeholder while PCC confirms its recurring live-worship and recording workflow.
Show only current, approved public events. The actual calendar source and update owner remain a Meeting 4 confirmation.
Use PCC-approved details when they are ready.
The public directory should lead with clear, current information, not a long collection of stale names and pages.
The public site should use one consistent /give destination with context, secure Pushpay access, and clear mail-giving information.
Warm enough to invite people in. Clear enough to help them act. Sustainable enough for PCC to care for over time.
About should help a visitor understand PCC's story, ministry identity, leadership, and the community relationships PCC wants to present publicly. This is a direction page, not final copy.
Connect brings together first-time visitor information, public events, ministry and auxiliary information that meet PCC's public-inclusion criteria, and approved community-care content.
Visible details for a first-time attendee. PCC needs to confirm the approved schedule, address, parking, accessibility, and what visitors should expect.
Display only events with a clear owner, an active ministry or event lead, approved public wording, and an accurate date.
Use a consistent summary and contact template. Avoid unofficial, outdated, or unapproved ministry pages.
Publicly useful content belongs here when PCC confirms current days, eligibility, contact method, and change owner.
Use approved public channels. The launch should not publish unmonitored forms, inboxes, or personal contact information.
This is a future need. It should not be implied as ready or promised within the Phase II public-site scope.
Worship supports live worship, recent services, and message-focused content without prematurely locking PCC into a media model it has not yet defined.
Launch with the simplest sustainable public experience. The actual source, timing, privacy rules, and archival pattern remain a Media Team confirmation.
Use approved language and a clear call to return for live worship or recent recordings. Do not create a fragile live-media process just to look complete on launch day.
A richer sermon archive, playlists, groups, and membership-related media can be defined later when sources, tagging, and ownership are sustained.
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 safe visual placeholder. Phase II should use PCC's authorized embedded giving configuration when it is confirmed by the responsible administrators.
Use this while screen-sharing to keep the conversation focused on confirming the direction rather than designing individual pixels.
This is an interaction demonstration, not an approved operational page. The finished site should use PCC-confirmed, maintained details.
Before a public event is published, PCC should identify a current owner, a current date, an approved summary, and a way to correct it if it changes.
Each ministry / auxiliary entry should follow a lightweight template: name, short purpose, current public contact route, simple image or visual, and an assigned content owner.
The Media Team should confirm the source of truth, live workflow, recording location, retention practice, who updates links, and the fallback message when a live stream is unavailable.
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.