# Content needed

This checklist tracks confirmed gaps for the first build. Items marked “provided” are transcribed from the supplied brief and still need church review before publication.

## Identity and design
- [x] Approved name: Winnipeg Christian Assembly (WCA).
- [x] Logo image supplied in chat; copied to `assets/wca-logo.jpg`.
- [ ] Confirm whether the logo image is the final high-resolution/transparent asset.
- [ ] Confirm brand colors, typography, photo/video rights, and any approved reference-site details.
- [ ] Supply approved congregation, worship, ministry, and outreach photos/video for hero and gallery.
- [ ] Supply/approve three Home hero assets (photos or short video), optional video poster/fallback image, alt text, and media-use permission. Current slideshow cards are illustrative placeholders, not WCA photos.
- [ ] Supply several approved congregation photos for the continuously scrolling footer strip (for example, worship, fellowship, gatherings, and community), with permissions and appropriate alt text. Current tiles are gradient placeholders, not photos.

## Who We Are / Beliefs
- [ ] Supply WCA leadership-approved statement of faith, including approved headings, wording, and any preferred scripture references for the Who We Are page.

## Visit / New Here
- [x] Sunday service: 10:00 a.m.–1:00 p.m. (provided; confirm punctuation/time-zone wording).
- [x] Wednesday Bible study: 6:30–8:30 p.m. (provided; confirm punctuation/time-zone wording).
- [x] Address: 90 Ashland Avenue, Winnipeg, Manitoba, R3L 1K6.
- [ ] Confirm what to expect during a service.
- [ ] Confirm parking and transit information and approved map/directions link.
- [ ] Confirm children’s arrangements, youth information, and accessibility details/policies.
- [ ] Confirm whether “meet someone on arrival” should appear on the launch form.
- [ ] Confirm visitor form recipient, consent wording, retention period, access, and handling before enabling submissions.

## MVP teaching and resources
- [ ] YouTube sermon URLs and approved title, speaker, date, series/topic metadata.
- [ ] Confirm how sermons and other content will be exported from WordPress before admin access lapses.
- [ ] Devotional posts and verse-of-the-day content with source/attribution.
- [ ] Music playlist/audio embeds and rights/approved source.
- [ ] Bible-study outlines, books/resources, and message summaries with approved metadata.
- [ ] Sister/associated ministry names, descriptions, links, and approved images.
- [ ] Confirm whether calendar/news/events are available for launch.

## Giving and public contact
- [x] Giving methods selected for the page: Interac e-Transfer, QR code, and cash or envelope in person.
- [ ] Interac recipient address, transfer instructions, approved QR-code image/destination, and in-person giving location/process.
- [ ] Approved giving wording and contact destination for questions; no payment processing is configured.
- [ ] Confirmed church contact email, YouTube channel URL, and Instagram profile URL; the footer currently shows labeled placeholders without active links.
- [ ] Other public contact details and approved contact destination for general submissions.
- [ ] Community outreach opportunities, assistance request recipient, eligibility/process, and handling instructions.

## Congregation and families
- [ ] Bulletin and announcements content and publishing owner.
- [ ] Calendar events, registration requirements, cancellation/consent wording, and event contacts.
- [ ] Small groups and ministry-team names, details, leaders, and approved public visibility.
- [ ] Member sign-in method, member data, dashboard rules, roles, administrators, account lifecycle, and access review.
- [ ] Children’s/youth policies and event-registration details.
- [ ] Decision whether secure check-in is needed; if yes, process, authorized users, data, retention, safeguards, and incident handling.

## Pastoral care and volunteer workflows
- [ ] Pastoral-care/prayer request recipients, who may view/assign, follow-up process, retention, security, consent language, and approved request fields. The page form is a disabled preview only.
- [ ] Volunteer opportunities, availability fields, schedule owner, notification channels, reminder approval, access roles, and open-role process.
- [ ] Whether any workflow will use an external service and the church’s approval of its data handling.

## Worship, media, and future integrations
- [ ] Live-service platform/URL and publishing owner, if used.
- [ ] Sermon transcript, scripture/topic metadata, saved-message, and study-resource requirements.
- [ ] Approved teaching corpus and source/permission rules for search/assistant answers.
- [ ] Human review owner and approval stages for generated transcripts, summaries, clips, social slides, and recommendations.
- [ ] Captions/transcripts provider and accessibility review process.
- [ ] Service-companion content owner and which notes/scriptures may be published.
- [ ] Confirm archive migration and R2 audio are Phase 2 work; not started in this build.

## Church operations
- [ ] Receipt rules and giving record requirements (static giving only until confirmed).
- [ ] Room inventory, booking rules, approvers, calendar integration, and permissions.
- [ ] Document types, storage location, access roles, versioning, retention, and audit requirements.
- [ ] Administrative roles and approved audit-log retention/access policy.

## Editing, hosting, and handover
- [ ] Identify nontechnical content editors and decide whether a browser-based CMS is required.
- [ ] Confirm church-owned GitHub organization/repository and Cloudflare account/project.
- [ ] Confirm domain/DNS owner and access for later launch.
- [ ] Confirm deploy/review approvers and who maintains the site/SOP.
- [ ] Approve final public content and the operational setup before launch.