Every Tongue · Bible Translation Ministry Website Template · sample contentOpen editorGet this website
Skip to content
Every Tongue
HomeHow it worksThe languagesTranslatorsSponsorPrayVisit us

On this page

    Sponsor a chapter
    Every Tongue
    HomeHow it worksThe languagesTranslatorsSponsorPrayVisit us

    2306 S Cedar Ridge Dr, Duncanville, TX 75116

    (555) 014-3380

    office@example.org

    Sponsor a chapter

    How it works

    Slow on purpose


    A New Testament takes eight to twelve years. Most of those years go into making sure a grandmother hears what the Greek actually says.

    Average timings from our last 14 completed New Testaments.

    Six stages

    What happens to every verse

    Most passages loop between stages two and four several times. That is the system working.

    1. 1

      Step 1 of 6

      A church chooses its translators

      Local churches nominate two or three people who speak the language from birth and are trusted to tell the truth. We train them for two years before the first verse.

      A church chooses its translators
    2. 2

      Step 2 of 6

      Drafting

      Working from the Greek and Hebrew with study notes in Paratext, a team drafts about a chapter a month. Most teams work from a shared office in a market town.

      Drafting
    3. 3

      Step 3 of 6

      Team and community check

      The team reads its draft aloud to groups in different villages and ages. Any word that makes people stop or laugh goes on a list.

      Team and community check
    4. 4

      Step 4 of 6

      Back translation

      A speaker who has not seen the source text writes a literal English version. It reads oddly on purpose, so nothing is smoothed over.

      Back translation
    5. 5

      Step 5 of 6

      Consultant check

      One of our consultants spends two to three weeks with the team, going verse by verse through the back translation. Only approved passages count toward our totals.

      Meet the consultants
      Consultant check
    6. 6

      Step 6 of 6

      Typeset, record, dedicate

      Bao and the Duncanville team typeset the text, a studio records it as audio, and the community holds a dedication service. Then the reading groups start all over again with the next book.

      Typeset, record, dedicate

    Typical timings

    What the numbers usually look like

    Averaged across the last fourteen New Testaments we helped finish.

    2009 to 2025

    9.41

    years from first draft to dedication

    ~85

    verses drafted per team per month

    40+2

    community readers per book

    11

    consultant visits per New Testament

    1. 1The fastest took six years; the slowest, fourteen, including a civil war.
    2. 2At least four villages, three age groups, men and women heard separately.

    Figures from our project database, updated each June.

    Questions

    What supporters ask us

    Why not use AI to translate faster?

    We use software constantly, including machine-assisted drafting tools where they exist for a language. They speed up the first draft. They do not replace community checking or a consultant, because the point is a text that real speakers trust.

    Why pay translators instead of using volunteers?

    Because it is a full-time job for a decade. Unpaid translators drift away to feed their families, and projects stall. Fair stipends are the single biggest predictor of a finished New Testament.

    Who owns the translation?

    The language community's churches. We never hold the copyright; it is registered to a local trust the churches appoint.

    What about oral communities?

    About a third of our teams produce audio first, often with women's storying groups. Print follows when there are readers for it.

    Bearded priest reading a red book beside a church window

    From a consultant

    My job is to ask the same question four hundred times: what does this word mean to you? The answers are where the real translation happens.
    Dr. Samuel HaddadTranslation consultant, 22 years

    Fund one month of one team's work

    A chapter is $45 a month for a year. You'll receive its back translation when it passes the check.

    Sponsor a chapter
    Every Tongue

    Funding, training and checking mother-tongue Bible translation since 1987. Field locations are kept general to protect our teams.

    Pages

    • Home
    • How it works
    • The languages
    • Translators
    • Sponsor
    • Pray
    • Visit us

    Duncanville office

    • 2306 S Cedar Ridge Dr, Duncanville, TX 75116
    • (555) 014-3380
    • office@example.org
    • Office Mon–Fri 8:30 AM – 4:30 PM
    • Scripture Wall open to visitors Tue & Thu
    © 2026 Every Tongue ProjectWebsite by Greater Purpose Web

    Design notes

    Why Every Tongue looks the way it does

    Every Tongue Project is a small Texas ministry that pays, trains and supports mother-tongue Bible translators in 38 languages. The site has to explain a slow, careful process to churches that give, while protecting translators who work in places where their faces and village names cannot appear online.

    Built for
    Church mission committees, individual sponsors and prayer partners across the US, plus translators and consultants who check the site for schedules and downloads.
    Navigation
    Contents column. A right-hand contents list tracks where you are on long pages, the way a well-made book or report does.
    Pages
    Home, How it works, The languages, Translators, Sponsor, Pray, Visit us
    Hero
    One impact number is the hero (for example meals served this year), with a line naming the unit, a sentence of context, a row of three supporting figures and one photograph. The number counts up once when it first comes into view. Variants: a = the number spans the full width above the photo and figures; b = photo on the left, number and a ledger of figures on the right; c = the number sits on a coloured panel that overlaps the bottom of a wide photograph

    Typography

    The whole site is set in the IBM Plex family: Serif for headings, Sans for reading and Mono for labels and verse references. Translation is engineering with words, and Plex was drawn for engineers, with very clear figures and broad support for diacritics. One superfamily also mirrors the discipline of the work: consistent, checked, nothing decorative for its own sake.

    Color

    The red is rubric, the iron-oxide red scribes used for headings and initials in manuscript Bibles; it is also close to the color of a consultant's correction pen. The teal is verdigris from old bindings, and the background is the gray-green of ledger paper rather than parchment cream. In dark mode the rubric lightens to coral so it keeps its contrast on a deep green-black.

    Layout and navigation

    Long pages with a contents column on the right, because visitors here read. A mission committee preparing a budget report wants to jump to the figures, a prayer partner to the language they adopted. The column shows where you are on the page without hiding the main navigation.

    The hero

    The opening number is verses approved this year. It is the honest unit of the work: a verse goes on the count only after a consultant signs it off. It sits full width, large enough to read from the back of a church foyer when it goes up on a mission Sunday slide.

    Calls to action

    'Sponsor a chapter' is the primary action because a chapter is a real, fundable unit: about one month of a team's time. 'Adopt a language in prayer' is the second door, deliberately given equal weight on the home page, because many supporters will never give large sums but will pray for one people group for years.

    Photography

    Field photographs never show translators' faces in sensitive regions, and language names are replaced with letters where needed, which is standard practice in this field. Portraits appear only for team members who have agreed to it. We favour desks, pages and gatherings around a reading over landscapes, because the story is people working with words.

    Accessibility

    Every color pair passes WCAG AA in both themes, including the red labels. The contents column is a real ordered list of links, so screen-reader users can navigate long pages by section. Audio samples come with text, and nothing important is carried by color alone.

    Type system

    • DisplayIBM Plex SerifIBM Plex Serif was drawn as an engineer's serif: sturdy slab-like joins, tabular-feeling figures and a calm italic. It suits translation work, which is careful, technical and checked line by line.
    • TextIBM Plex SansPlex Sans shares Plex Serif's skeleton, so headings and text feel like one voice. It is also built for diacritics and many scripts, which matters on a site full of language names.
    • AccentIBM Plex MonoPlex Mono sets labels, verse references and stage codes the way they appear in translation software: plain, aligned and exact.

    Colour and contrast

    Every text pairing is checked against WCAG 2.2 in both themes.

    Light theme

    PairingSampleRatioWCAG
    Body text on pageAa14.13:1AAA
    Body text on cardsAa15.6:1AAA
    Secondary textAa5.61:1AA
    LinksAa6.42:1AA
    Button textAa7.37:1AAA
    Accent label textAa5.87:1AA
    Text on dark bandsAa14.13:1AAA
    Muted text on dark bandsAa7.57:1AAA
    Text on brand bandsAa7.37:1AAA
    Muted text on brand bandsAa4.77:1AA

    Dark theme

    PairingSampleRatioWCAG
    Body text on pageAa14.49:1AAA
    Body text on cardsAa13.06:1AAA
    Secondary textAa6.54:1AA
    LinksAa6.59:1AA
    Button textAa7.0:1AAA
    Accent label textAa9.18:1AAA
    Text on dark bandsAa15.62:1AAA
    Muted text on dark bandsAa7.96:1AAA
    Text on brand bandsAa7.0:1AAA
    Muted text on brand bandsAa4.67:1AA

    Designed by Greater Purpose Web. Names, people and events are sample content.