Internal · not a public page
Build questions
Decisions and open questions surfaced while building the demo — a checklist to walk through together.
Design & Brand
3- Needs their input
Which homepage direction do we build out?
Three live variations to compare — Warm (/), Editorial (/editorial), Bold (/bold). Same brand and content, different feel. Pick one to develop; ideas from the others can be grafted in.
- Our recommendation — confirm
Keep the current logo and navy / steel / gold palette?
The demo carries the existing brand over and drops the stock SnapPages greys. Confirm they're happy with it, or whether a refresh is on the table.
- Needs their input
Photography — new shoot, or reuse what exists?
The demo uses real photos pulled from the current site. Staff headshots are theirs; several event/serve-card images are thematic stand-ins. Worth deciding if a fresh photo set is wanted.
Events & Planning Center
5- Needs their input
How should staff choose which events appear on the homepage?
Right now every event published to Church Center shows — including the weekly Sunday service (it appears twice, 9:00 & 10:30). Options: a dedicated 'Website'/'Promote' tag, or Planning Center's built-in 'Featured' flag, to curate the homepage. Your calendar is already heavily tagged, so a tag would slot in cleanly.
- Our recommendation — confirm
Manage event artwork in Planning Center?
PCO exposes an event image directly (image_url), and the demo already pulls it. This likely removes the need for a separate CMS step for event images.
- Needs their input
Own event detail pages, or link to Church Center?
Every event already has a working detail page on Church Center, with registration wired up and always current — Planning Center hands us that link directly. We could link straight out to it, or build matching detail pages on the new site. Our own pages look consistent and help Google find events; linking out is zero maintenance and never goes stale.
- Our recommendation — confirm
How fresh do events need to be?
Plan is scheduled rebuilds (e.g. every few hours) plus an on-demand rebuild — not per-second live. Confirm that cadence is acceptable, or if near-instant updates matter for any case.
- Heads-up / already handled
Private / internal calendar entries stay internal.
Verified: the site only pulls events staff mark visible in Church Center. Internal entries (room bookings, staff time-off, staff/elder meetings) are filtered out and never reach the build or the browser. Read-only, build-time only.
Content & CMS
4- Heads-up / already handled
Page copy is managed in Sanity — live to demo.
Decided and built: a Sanity project is set up with the site's real content, and we can log in and edit it together. Weekly event work stays in Planning Center exactly as today — nothing about that changes. Sanity is only for occasional page copy, staff and service times. Free tier covers 20 editors, well beyond what's needed.
- Heads-up / already handled
Nothing private goes in the CMS.
Worth knowing: Sanity's free tier stores content in a public dataset, meaning published copy is readable through their API by anyone — fine, since it's all bound for a public website anyway. The rule it sets: no personal phone numbers or home addresses, no member data, no prayer requests. Those stay in Planning Center, which has real permissions.
- Our recommendation — confirm
Staff can add whole new pages — confirm that's wanted.
Creating a page in Sanity and setting its URL publishes it to the site, no developer needed. Worth confirming that's desirable rather than alarming — some churches would rather new pages went through one person, which we can do instead.
- Needs their input
Who are the ongoing content editors?
Helps decide how simple the editing surface needs to be and how much training/handoff to plan for.
Site Structure & Navigation
3- Needs their input
Which pages do we keep, merge, or retire?
~58 pages today, target ~20–25. Candidates to cut/merge include stale '-archive' duplicates and a public 'calendar-test' page. Want their sign-off on the consolidation.
- Our recommendation — confirm
Confirm the proposed navigation.
Demo groups things as New Here / About / Ministries / Get Involved / Care / Media. Confirm the groupings match how they think about the ministries.
- Needs their input
Confirm staff shown on the homepage and leadership page.
Homepage features five; the leadership page also lists office/support staff (Marty Kissell, Anna Merrill, Janet Waldmiller, Karen Koster). Confirm who should appear where and their titles.
Media & Giving
5- Heads-up / already handled
Subsplash is being retired.
The migration moves off Subsplash entirely — sermons, media, and the giving embed included. That's decided; the items below are only about where each piece lands, not whether Subsplash stays. Where possible we consolidate onto Planning Center / Church Center.
- Needs their input
Where will online giving live? Nothing is set up yet.
The biggest open item, and bigger than it first looked. Online giving runs through Subsplash today, which is being retired — and Planning Center Giving is NOT currently enabled on their account (Church Center's giving page returns 'missing organization'). So this isn't a switch to flip: whichever platform they choose has to be set up, funds configured, and bank details verified, which takes lead time. Until it's decided, the Give page shows the other four ways to give and marks online giving as coming soon rather than linking anywhere.
- Our recommendation — confirm
Giving is the last thing to migrate, not the first.
Recommendation on sequencing: the site can launch with everything else moved over while giving still points at whatever is live at the time. Cutting over giving during the site launch stacks the highest-risk change on top of the busiest week — and a broken giving flow costs the church real money, unlike a page that looks slightly off.
- Heads-up / already handled
Livestream is YouTube-first.
Answered: Sunday services stream to YouTube, so /livestream embeds the YouTube player directly — no third-party video platform, no extra cost, and it works on every device without an app.
- Needs their input
Is the sermon archive just the past livestreams?
YouTube is settled as the live source. Still to confirm: does /sermons list the past stream recordings as-is, or are sermons edited into separate shorter videos? Also whether audio-only / podcast matters to anyone.
Deployment
2- Heads-up / already handled
The existing custom domain carries over.
Answered: no new domain — the site keeps the custom domain already in use. Visitors, printed material and existing links all keep working, and the search history built up on that domain is preserved.
- Needs their input
Confirm exactly which domain and where its DNS lives today.
The audit has gbcpeople.com serving the SnapPages site, with Subsplash hosting the app, sermons and giving — so we want to be precise about whether Subsplash also holds a custom domain or subdomain (e.g. for the app or media) that needs to come along. We need the registrar login and the current DNS records before scheduling the cutover to Cloudflare Pages, keeping email (MX) and any verification records untouched.
Edit src/pages/questions.astro — append to thequestions array to add items. Delete this page (and the “Questions” link in DemoSwitcher.astro) before launch.