• 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.

Absolutely! Frequent changes may be made to both bundled and non-bundled addons. Bundled addons will be updated via the upgrader. For non-bundled addons, you will have to update them through the addons management screen (Admin Zone > Structure > Addons). You will be informed which ones need updated.

Once version 11 reaches release candidate, we do not expect frequent updates to non-bundled addons anymore. But it is still good practice to check after every update.

Yes, for basic non-custom v10 sites. However, expect some issues to arise in the process. And please report those issues to the tracker.

For v10 sites with non-bundled addons or customisations, upgrading to v11 will likely break the site until you update the non-bundled addons or temporarily remove the customisations.

We aim to have the upgrader fully functional for a large majority of types of sites and for sites using non-bundled addons by the time version 11 reaches release candidate stage.

We do not recommend upgrading production v10 sites at this time until v11 reaches stable.

Yes (probably). Always remember especially during alpha and beta phases that things can break. Please make backups first. And let us know on the issue tracker if an issue occurs.
 

Note: You cannot upgrade from 11 alpha to 11 beta without first upgrading to 11.alpha4 (if you are not already on 11.alpha4).

As of July 22, 2024, we entered beta status where our focus is now smashing bugs and stabilising the software. All planned features have been implemented for 11.0 (and most others deferred to 11.1 or later), though we may still merge in a few minor features or tweaks. The upgrader has been tested on a typical non-custom v10 site.

We will be releasing several beta versions in the beta phase.

We do not know when we will be able to release the first Release Candidate or stable versions at this time.

These plans are all subject to change without notice.