Church4Christ

Many churches do not need another isolated tool; they need a digital home they can keep and run for the long term. Subscription bills, plugin upkeep, migrations, and platform lock-in often force a small congregation to choose between affordability and control.

Church4Christ starts from a different premise: a small but complete open-source project can provide a professional bilingual site and practical administration. The church owns its code, content, and member data—without waiting for a vendor's price change, shutdown, or another disconnected account.

The public site gives home, sermons, bulletins, events, ministries, staff, articles, and a prayer form a clear bilingual front door; three built-in themes help each church make it its own. Content teams enter the CMS through passwordless sign-in, reverse edits in one click, and schedule bulletins to publish themselves.

The system continues into everyday ministry: a private prayer wall, volunteer scheduling with email confirmations, people and household records, children's check-in, online giving, paid or free event registration, a member portal, and automated sign-in links, reminders, and weekly digests. Each capability is modular: turn it off when it is not needed, delete nothing, and restore it later.

Astro and TypeScript build the site, which deploys as one Cloudflare Worker; Cloudflare D1 stores default data, R2 holds uploaded media, and Email sends transactional messages. A typical church site can run on Cloudflare's free tier; online giving, registration, and the member portal need Stripe and Supabase in addition.

Clear feature documentation and extensive automated tests make it practical for a technical volunteer or an AI assistant to collaborate on routine changes. GPL-3.0 protects the freedom to use, study, modify, and share the work, while requiring distributed modifications to give back under the same open-source spirit.