Volunteer:Development
From Gospel Translations
| Line 1: | Line 1: | ||
The scoop on what we use. If you're interested, here are current projects we need help tackling: | The scoop on what we use. If you're interested, here are current projects we need help tackling: | ||
| - | * [[Project:Technology/Multi-wiki_project|Multi-wiki automation]] | + | * [[Project:Technology/Multi-wiki_project|Multi-wiki automation]] - Using automated processes to launch and maintain separate wikis for each language that Gospel Translation works in |
== Software == | == Software == | ||
Revision as of 21:34, 25 August 2008
The scoop on what we use. If you're interested, here are current projects we need help tackling:
- Multi-wiki automation - Using automated processes to launch and maintain separate wikis for each language that Gospel Translation works in
Software
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 (see example), you are seeing MediaWiki and DabbleDB work together.
