One congregation, two languages, one platform
A bilingual church is not two churches that share a building. The software should not turn it into two mailing lists, two portals and two sets of announcements.
How the two languages work
Per person, not per site
Each member chooses their language and the whole platform answers in it. There is no Spanish version to maintain separately.
The whole application, not the menus
Including error messages and validation, which is the part that is usually left in English and is exactly where a member gets stuck.
Consistency that is tested
A build fails on a key that exists in one language only, on mismatched placeholders, and on a sentence left untranslated — so drift is caught before release rather than by a member.
One membership, one set of groups
Your English and Spanish congregations are in the same directory, the same events and the same giving records.
The public pages are bilingual too
Not only the signed-in application. This site’s Spanish marketing pages have permanent Spanish addresses of their own rather than a language button, because a search engine reads the HTML it is served and a page that only becomes Spanish after loading is, to Google, an English page. If your church is going to be found by a Spanish-speaking pastor, that is the difference.
Frequently asked questions
- Is Spanish an extra cost?
- No. Both languages are in every plan.
- Is the Spanish machine-translated?
- No. It is written and reviewed, including a consistency pass over the terminology, because a congregation can tell the difference immediately.
Set your church up on Church By Faith
Create your church, invite your leaders and turn on only the tools you use. Nothing you do not need appears in anyone’s navigation.
Start your church