A church website has to tell the truth about Sunday, the pastor, and the gospel.

The problems this build addressed

• A ChurchSpring, Wix, Sharefaith, or Squarespace site that leaks admin chrome, leaves sermons empty, or buries the gospel three clicks down
• Service times, pastor names, and giving instructions that go stale because the office cannot edit them without a vendor
• The Sunday bulletin, the website, and the weekly email as three separate jobs
• Doctrine, pastor, or leftover copy from another church (Trinity, Charleston, River Mountain) published by mistake
• Member, prayer, and directory data sitting in a tool the church does not own

What the vertical build includes

• A public church site: home, about, beliefs, how to be saved, schedule, sermons, events, prayer, give, contact, and a print-ready bulletin
• An office login the secretary can run: schedule, events, prayer, pages, photos, mailing list
• A claims audit that will not invent attendance, founding years, or pastor bios, and that flags leftover template copy
• A per-URL PRESERVE or 301 map from the old ChurchSpring, Wix, WordPress, or Squarespace paths
• A fact-sheet correction loop for every [CONFIRM] row before the real domain points here

Bring me the current site and the pages a first-time guest cannot afford to miss.

I will map what needs to be preserved, what needs confirmation, and what a skeptical reviewer should test.