French tA articles, beginning with those occurring in OBS.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Larry Sallee 090b8eaede remove DS Store 4 months ago
checking New content 2 years ago
intro Created 'intro/uw-intro/' using 'tc-create-app' 4 months ago
process New content 2 years ago
translate remove DS Store 4 months ago 1 year ago Added new content 2 years ago
manifest.yaml Valid Restore content 2 years ago
media.yaml New content 2 years ago

unfoldingWord translationAcademy


unfoldingWord translationAcademy is a modular handbook that provides a condensed explanation of Bible translation and checking principles that the global Church has implicitly affirmed define trustworthy translations. It enables translators to learn how to create trustworthy translations of the Bible in their own language.


If you want to download English translationAcademy to use, go here: tA is also included in tS and tC.

Improving tA

Please use the issue queue to provide feedback or suggestions for improvement.

If you want to make your suggested changes then you may use the online editor to do so. See the protected branch workflow document for step by step instructions.


The tA are written in a simple Markdown format and organized according to the Resource Container Manual type. See that link for more information but here is a quick summary.

Each manual has it’s own directory in this repository (for example, the Checking Manual is in the checking directory). Each module has its own directory inside of these manual directories. Inside each of these are three files:

  • - This is the main body of the module
  • - This file contians the question that the module is intended to answer.
  • - This contains the title of the module

There are also YAML formatted files in each manual’s directory. The toc.yaml file is for encoding the Table of Contents and the config.yaml file is for encoding dependencies between the modules.

GL Translators

tA Translation Philosophy

To learn the philosophy of how to translate the tA please see the Translate translationAcademy article in the Gateway Language Manual.

If you are translating online, please fork the Door43-Catalog/en_ta repository, following this workflow: Translate Content Online.

Technical Information for Translating tA

  • Do not rename any files or directories. Only translate what is inside the files.
  • The config.yaml and toc.yaml files do not need to be changed unless you add a new module. When you are finished translating, you may want to update the title fields in the toc.yaml file, but you shouldn’t make any other changes in those files.
  • Images that are included in tA should be no more than 600px wide. Leave the image links alone to use the original images.
  • Hyperlinks (links to other articles or to other pages on the internet) follow this pattern: [text to display]( You can translate the “text to display” inside the square brackets but not the web address that follows inside the parentheses.

You are free to add additional modules. In order for the new modules to be included when tA is published, all of the following conditions need to be satisfied:

  • You must create a directory in one of the manual directories (like the translate directory) that has the short name of the module you want to write. For example, to create a new module on “testing” in the Translation Manual, you will want to put the file in “translate/testing/”.
  • The file must be included in the table of contents, toc.yaml for the appropriate manual.
  • The value of the slug in the toc.yaml file and the directory (without the extension) must be the same as the directory name (testing in this example).
  • The slug must be unique, and not used in any of the other tA repositories. This is a requirement so that it is possible to create unambiguous links to articles in other tA manuals.


See the LICENSE file for licensing information.