Decidim Participatory Documents

This module allows to upload PDF (and possibilty other formats) and define areas on top of it that will become spaces for suggestions, improvements and other participative activities.

Installation

Add this line to your application's Gemfile:

gem 'decidim-participatory_documents

Or, if you want to stay up to date with the latest changes use this line instead:

gem 'decidim-participatory_documents', git: "https://github.com/openpoke/decidim-module-participatory-documents"

And then execute:

bundle
bundle exec rails decidim_participatory_documents:install:migrations
bundle exec rails decidim_participatory_documents:install_pdf_js
bundle exec rails db:migrate

Depending on your Decidim version, you can choose the corresponding version to ensure compatibi lity:

Version	Compatible Decidim versions
0.2.x	0.27.x

Usage

TODO...

Customization

Almost all the features of this module can be customized/disabled through an initializer.

For instance, you can create an initializer an change some of the available options as follows (This is optional, you don't need to do this, by default all options are enabled):

# config/initializers/participatory_documents.rb
Decidim::ParticipatoryDocuments.configure do |config|
  # Public: The maximum length of any text field (body, answers, etc) to export.
  # Defaults to 50. Set to 0 to export the full text.
  config.max_export_text_length = 50

  # Public: The minimum length of a suggestion to be considered valid.
  config.min_suggestion_length = 5

  # Public: The maximum length of a suggestion to be considered valid.
  config.max_suggestion_length = 500
end

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/openpoke/decidim-module-participatory-documents.

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

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.

Rubocop linter is used for the Ruby language.

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

$ bundle exec rubocop

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

Atom - linter-rubocop
Sublime Text - Sublime RuboCop
Visual Studio Code - Rubocop for Visual Studio Code

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-participatory-documents

License

See LICENSE-AGPLv3.txt.

antopalidi/decidim-module-participatory-documents