Volunteer:Development
From Gospel Translations
(New page: Gospel Translations relies on a few basic pieces of software to run smoothly. '''[http://www.mediawiki.org MediaWiki]''' is our wiki engine, and is the same software used by Wikipedia. It...) |
|||
| Line 9: | Line 9: | ||
'''[http://www.dabbledb.com DabbleDB]''' is our online database provider, helping us keep information about all of our publishers, articles, volunteers, and translations organized in one central place. Better still, it has good API support, so we've been able to tie the data their directly into wiki articles--when you visit a page and see the blue box listing Author, Translator, and so forth, you are seeing MediaWiki and DabbleDB work together. | '''[http://www.dabbledb.com DabbleDB]''' is our online database provider, helping us keep information about all of our publishers, articles, volunteers, and translations organized in one central place. Better still, it has good API support, so we've been able to tie the data their directly into wiki articles--when you visit a page and see the blue box listing Author, Translator, and so forth, you are seeing MediaWiki and DabbleDB work together. | ||
* [[Project:Technology/DabbleDB integration|How DabbleDB integrates with the GospelTranslations wiki]] | * [[Project:Technology/DabbleDB integration|How DabbleDB integrates with the GospelTranslations wiki]] | ||
| - | |||
==Multi-wiki project== | ==Multi-wiki project== | ||
| - | + | '''Goal:''' to have a separate wiki for every language we support | |
| + | |||
| + | '''Requirements:''' | ||
| + | * Written in PHP | ||
| + | |||
| + | '''Components:''' | ||
| + | * [COMPLETE] Our flat file '''[[Project:Technology/DabbleDB integration|content database]]''', which provides information about all the translations for any given language | ||
| + | * [unassigned] '''[http://wikisum.com/w/User:Adam/Creating_MediaWiki_bots_in_PHP Automating bot]''' which will | ||
| + | ** Search the database for all articles in the specified language | ||
| + | ** Create a new page on the target wiki for each translation | ||
| + | ** Write to the page ''transclusion code'' (see below) and a fully localized "About this Resource" box (see Glossary below) | ||
| + | * [COMPLETE] '''Transclusion code''' in this form--<code><nowiki>{{:gt_en:Name_of_corresponding_article_on_English_wiki}}</nowiki></code>--will make a live copy of the translation text and display it on the page where this code appears | ||
| + | |||
| + | |||
| + | [[Category:Tech admin]] | ||
Revision as of 19:59, 22 August 2008
Gospel Translations relies on a few basic pieces of software to run smoothly.
MediaWiki is our wiki engine, and is the same software used by Wikipedia. It was chosen for it's proven scalability, excellent support for multiple languages, and it's easy extensibility. The fact that it has such excellent community support was also a big factor when we chose it. MediaWiki runs on PHP and MySQL.
DabbleDB is our online database provider, helping us keep information about all of our publishers, articles, volunteers, and translations organized in one central place. Better still, it has good API support, so we've been able to tie the data their directly into wiki articles--when you visit a page and see the blue box listing Author, Translator, and so forth, you are seeing MediaWiki and DabbleDB work together.
Multi-wiki project
Goal: to have a separate wiki for every language we support
Requirements:
- Written in PHP
Components:
- [COMPLETE] Our flat file content database, which provides information about all the translations for any given language
- [unassigned] Automating bot which will
- Search the database for all articles in the specified language
- Create a new page on the target wiki for each translation
- Write to the page transclusion code (see below) and a fully localized "About this Resource" box (see Glossary below)
- [COMPLETE] Transclusion code in this form--
{{:gt_en:Name_of_corresponding_article_on_English_wiki}}--will make a live copy of the translation text and display it on the page where this code appears
