Gospel Translations:Technology/Multi-wiki project
From Gospel Translations
(Difference between revisions)
| Line 2: | Line 2: | ||
===Description=== | ===Description=== | ||
| - | '''Goal:''' to have a separate wiki for every language we support | + | '''Goal:''' to have a separate wiki for every language we support, with fully automated content loading and updating |
'''Requirements:''' | '''Requirements:''' | ||
Revision as of 18:56, 26 August 2008
Read on to learn more. Use the discussion tab to make comments, post solutions, etc.
Description
Goal: to have a separate wiki for every language we support, with fully automated content loading and updating
Requirements:
- Code base written in PHP
- For each language X, copy over every X article from this English wiki to a target wiki, http://X.gospeltranslations.org
Technical process
This is the basic process that could be used to accomplish the multi-wiki setup and updates. There are some underlying techniques not spelled out here, so feel free to ask questions if something isn't connecting for you.
- [working] Cronjob imports up-to-date info DabbleDB database and stores it in local PHP array (see structure)
- [unassigned] Automating bot (how to make one)
- reads local PHP array to find all entries for language X
- for each entry, gets translated title off of the English wiki (i.e., for Gospel_Implications/es, it finds the title Consecuencias del evangelio)
- for each entry, creates a page on the target wiki, i.e., http://fr.gospeltranslations.org/wiki/ENTRY_TRANSLATED_TITLE
- on each page created, writes in transclusion code:
{{:gt_en:ENTRY_ENGLISH_NAME}}
- [working] Non-English wiki uses transclusion code to pull article text from English wiki. For example, the code
{{:gt_en:Gospel_Implications/es}}will grab the entire article text from Gospel_Implications/es
Obviously, what is missing from the functionality right now is a working automation bot.
