• Joining the translation team on Transifex: Translate language strings collaboratively with other volunteers.
• Becoming a language maintainer: Take responsibility for the translation and support of Composr in your native language.
• Reporting translation issues: If you encounter unclear, incorrect, or duplicated language strings, file bug reports.
• Providing feedback and suggestions: Share your thoughts on improving the translation process through feature suggestions.

• Centralized translation efforts: Multiple translators can work on the same project.
• Improved translation quality: The platform facilitates consistency and accuracy.
• Simplified language pack creation: You can generate downloadable language pack addons directly from Transifex.

• Copy the EN folder: Create a new folder with the ISO code of your target language (e.g., FR for French).
• Replace the images: Replace the English images with translated versions.
• Ensure correct image paths: Update any references to these images in your templates or content to point to the translated versions.

• Editing the content directly: Go to the specific content item (page, news post, etc.) and edit it in the new language.
• Using the language editor: Access the language editor from Admin Zone > Style > Translate/rephrase Composr to modify language strings used on specific pages.

• Download the language pack: You can download language packs from the Composr website.
• Install the language pack: Upload the downloaded language pack addon through Admin Zone > Structure > Addons > Import non-bundled addon(s).
• Change the default language: Go to http://yourbaseurl/config_editor.php and set the desired language.
• Update your profile: If you had a previous language set in your profile, update it to the new language.

Coded the chatroom, blogging support, the analytics system, and OcCLE (now Commandr)

Masters Degree in Computer Science degree from The University Of Cambridge

Other work has included helping out with Firefox, and ongoing work on GNOME

Original designer for ocPortal

Also conceived and coded the Theme Wizard and Point Store

Son of one of the early inventors of Internet protocols (Usenet, aka Internet newsgroups)

Token non-brit

Ran some of the early websites where ocPortal came from

Technically the original developer of ocPortal, in that he wrote the first few lines of code

Heavily involved in the feature design process

Hosted some of our early meet-ups

Original developer of ocPortal, former lead developer of Composr CMS

Masters degree in Computer Science from The University Of Sheffield

Undertaken work for over 15 FTSE-100 companies, as well as many small and mid-sized organisations. Includes a number of banks and major brands.

gameRevolt (@[email protected]) - LinuxRocks.Online

That depends on several factors. Here are some pros and cons of each:

It is not recommended you do this because you may run into issues. For example, some changes were made in crypto_master.php and data/upgrader2.php prior to the first v11 alpha. These changes will result in a broken upgrade unless you already pulled these changes from git. Similar situations could happen in the future as well.

It is recommended you either discard the git install and use a fresh install from the Downloads, or to maintain a git install and a bleeding-edge release install separately. Do not combine the two.