Decidim::TermCustomizer

The gem is a fork by the original Term Customizer created by Mainio Tech maintained by Pokecode.

WHY THIS FORK The original Term Customizer is maintained at the pace that suits the original company according to the needs of their clients.

This means that many contributions, including translations, upgrades and fixes, can be on hold for many months before being merged. This is very uncomfortable for the majority of the Decidim ecosystem using this plugin. Including ourselves which have a much quicker response policy in general when it comes with updates and fixes.

See the CHANGELOG for changes related to this fork.

Future policy We will be monitoring the original code and we will port those PR that seem interesting or solve problems.

However, we encourage everyone to contribute here, we will commit on being responsive and community committed.

Instructions on how to install are updated for using this fork accordingly.

A Decidim module to customize the localized terms in the system. The module allows administrators to add "translation sets" through the admin panel which contain customized terms for any module in the system. These sets can be applied against different scopes within the system, e.g. the whole system, participatory space scope (e.g. all participatory processes or a specific participatory process) or a specific component within a participatory space.

The term customizations will be only applied to the scope which the admin user has defined for the set. Multiple scopes can be defined against a single translation set.

Example use cases for this module:

• Admin wants to change the term "Proposal" to "Idea" in all participatory processes within the system.
• Admin wants to change the terms "accepted" and "rejected" in the proposals component to "possible" and "not possible" for a specific participatory process.
• Admin wants to change the term "debate" to "discussion" for all assemblies within the system.

You can add the term customizations using either of the following methods:

• Search the terms from all the system translations matching the term itself or the translation keys. This method is available in the "Add multiple" view.
• Add the term customizations for specific translation keys in case you have the technical knowledge to find out the translation keys.

Installation

Add this line to your application's Gemfile:

gem "decidim-term_customizer", github: "openpoke/decidim-module-term_customizer"

Install dependencies:

bundle
bin/rails decidim:upgrade
bin/rails db:migrate

EXPERTS ONLY

Under the hood, when running bundle exec rails decidim:upgrade the decidim-term_customizer gem will run the following two tasks (that can also be run manually if you consider):

bin/rails decidim_term_customizer:install:migrations

Usage

• Install the gem.
• Login to the system as an administrator.
• Go to the admin panel > Term customizer.
• Add a new translation set and give it a name (e.g. "All processes"). The name of the set is only relevant for the admin to identify what that set is used for. It is suggested to give the sets a name that identifies the scope where it is used.
• Apply the set to the scope or scopes where you want these customizations to be active.
• Save the set.
• Add the translations to the set which you want to customize within the defined scope. You can either add specific translation keys manually or search the translations from all the system's translations using the translation terms or keys.
  • Using the "add multiple" view is definitely easier for beginners since it allows searching for the terms and then automatically adding all the keys where that translation exists.
  • In case you are directly adding the translations, please note that the translation key refers to the technical key that Rails uses to refer to the translatable terms. For example, decidim.menu.processes.

The UI is currently a bit rough, it could definitely use some improvement. Contributions regarding this are very welcome!

Contributing

For instructions how to setup your development environment for Decidim, see Decidim. Also follow Decidim's general instructions for development for this project as well.

Developing

To start contributing to this project, first:

• Install the basic dependencies (such as Ruby and PostgreSQL)
• Clone this repository

Decidim's main repository also provides a Docker configuration file if you prefer to use Docker instead of installing the dependencies locally on your machine.

You can create the development app by running the following commands after cloning this project:

$ bundle
$ DATABASE_USERNAME=<username> DATABASE_PASSWORD=<password> bundle exec rake development_app
$ npm i

Note that the database user has to have rights to create and drop a database in order to create the dummy test app database.

Then to test how the module works in Decidim, start the development server:

$ cd development_app
$ DATABASE_USERNAME=<username> DATABASE_PASSWORD=<password> bundle exec rails s

In case you are using rbenv and have the rbenv-vars plugin installed for it, you can add the environment variables to the root directory of the project in a file named .rbenv-vars. If these are defined for the environment, you can omit defining these in the commands shown above.

Code Styling

Please follow the code styling defined by the different linters that ensure we are all talking with the same language collaborating on the same project. This project is set to follow the same rules that Decidim itself follows.

The following linters are used:

• Ruby, Rubocop
• JS/ES, eslint

You can run the code styling checks by running the following commands from the console:

$ bundle exec rubocop
$ npm run lint

To ease up following the style guide, you should install the plugins to your favorite editor, such as:

• Atom
  • linter-rubocop
  • linter-eslint
• Sublime Text
  • Sublime RuboCop
  • SublimeLinter-eslint
• Visual Studio Code
  • Rubocop for Visual Studio Code
  • VS Code ESLint extension

Testing

To run the tests run the following in the gem development path:

$ bundle
$ DATABASE_USERNAME=<username> DATABASE_PASSWORD=<password> bundle exec rake test_app
$ DATABASE_USERNAME=<username> DATABASE_PASSWORD=<password> bundle exec rspec

Note that the database user has to have rights to create and drop a database in order to create the dummy test app database.

In case you are using rbenv and have the rbenv-vars plugin installed for it, you can add these environment variables to the root directory of the project in a file named .rbenv-vars. In this case, you can omit defining these in the commands shown above.

Test code coverage

If you want to generate the code coverage report for the tests, you can use the SIMPLECOV=1 environment variable in the rspec command as follows:

$ SIMPLECOV=1 bundle exec rspec

This will generate a folder named coverage in the project root which contains the code coverage report.

Localization

If you would like to see this module in your own language, you can help with its translation at Crowdin:

https://crowdin.com/project/decidim-term-customizer

License

See LICENSE-AGPLv3.txt.