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
    Girls in traditional clothing smiling at a market

    Sponsor

    Put one chapter into a language for the first time

    Monthly sponsorship keeps teams paid between consultant visits, which is when projects most often stall.

    Monthly levels

    Choose what your gift does

    Every level is monthly, can be paused any time and is tied to one named or lettered language.

    Reading group

    Reading group

    $25/month

    Pays for tea, transport and printed drafts for a village reading group for a month.

    • One community check group
    • A photo of the drafts in use
    • Quarterly team update
    Give $25 monthly
    Sponsor a chapterMost chosen

    Sponsor a chapter

    $45/month

    About one month of a translation team's time, from draft through check.

    • One chapter, start to finish
    • Its back translation in English
    • A prayer card for the team
    • Monthly letter from the desk
    Sponsor a chapter
    Fund a consultant visit

    Fund a consultant visit

    $150/month

    Covers a share of travel and two weeks of checking with a team.

    • Your share of one visit
    • The consultant's trip report
    • A call with the team afterwards
    Fund a visit

    Gifts are tax-deductible. Sponsors get the English back translation of their chapter once it passes consultant check.

    Give

    Give once or every month

    Every dollar is assigned to a language unless you choose 'Where it's needed most', which we use to keep stalled projects moving.

    We publish what each project costs and send sponsors the same reports our board sees.

    $

    = 1 chapters drafted and checked

    Thank you. In the live site this opens secure checkout and emails a receipt.

    Secure checkout. Receipts by email each January.

    Where a dollar goes

    Every dollar, 2025–26

    From our audited accounts. We think you should see this before you give.

    Fiscal year 2025–26

    Audited by an independent firm in Dallas each September.

    Read the full report (PDF)
    1. Translator stipends154¢
    2. Consultant checking and travel17¢
    3. Training, software and laptops11¢
    4. Typesetting, printing and audio8¢
    5. Office and administration27¢
    6. Raising the next dollar3¢
    1. 1Paid monthly through local church trusts.
    2. 2Four staff in Duncanville, one shared building.

    Questions

    Before you sponsor

    Can my church sponsor a whole book?

    Yes. A Gospel is usually 16 to 28 chapters. Write to Ruth and we'll match you with a team at the right stage, and arrange a video call with them.

    What if the project stops?

    It happens, usually because of conflict or illness. We'll tell you straight away and move your gift to the nearest project in the same region unless you ask otherwise.

    Will I know the language's real name?

    For most projects, yes. For about a third, no: we use letters to keep teams safe. Sponsors of those projects receive updates without place names.

    Can't give right now? Pray instead.

    Adopt one language, get one card and one update a month.

    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.