Logo Lanfrica

KwasiEzor/ekklesia-cms

Domaine:

digital infrastructure

Type de record:

software
Créateur:
Kwa
Hôte:
The open-source CMS built for African churches and religious organizations # Ekklesia CMS An open-source, headless, multilingual content management system purpose-built for churches and religious organizations in Francophone Africa and the diaspora. ## The Problem Churches in Togo, DRC, Cote d'Ivoire, Benin, Cameroon, and the francophone diaspora in Belgium and France manage their online presence with tools that were never designed for them — WordPress is bloated and English-first, Western church software is priced in USD/GBP with no mobile money support, and everything else runs on WhatsApp groups and spreadsheets. Ekklesia is the tool that was missing. ## Features - **French-first admin panel** powered by Filament v5 - **Sermon management** — audio, video, transcripts, series, scripture references - **Event coordination** — calendar, registration, capacity management - **Member directory** — cell groups, baptism records, pastoral notes - **Giving records** — including mobile money (MTN, Orange, Wave) - **Multilingual content** — French, English, and local language support - **AI assistant** — drafts announcements, summarizes sermons, and answers how-to questions in French - **Headless REST API** — build your frontend in Next.js, Nuxt, React Native, or plain Blade - **Multi-tenant by design** — one installation, many churches, fully isolated data ## Tech Stack - Laravel 12 - Filament v5 - VitePress (documentation) ## Project Status Ekklesia is currently in **pre-beta active development**. Phases 1 through 5 (Core Content Types, API Layer, Deployment Prep, and AI Layer) are complete. The recent Production Readiness Sprint and the Page Builder "Pro" Update are also finished. We are currently implementing Phase 6 (Premium Modules). > **Warning:** Do not use in production yet. The API, database schema, and plugin contracts are subject to change without notice until v1.0 stable. ## Documentation **Read the full documentation** The documentation covers architecture decisions, content type system, multi-tenancy strategy, deployment …

Licenses