Decidim::EnhancedTextwork

The EnhancedTextwork module allows users to contribute to participatory textwork. They can support text-paragraphs, amend them, comment on them and discuss among each other.

This module is based on decidim-proposals and was developed to improve the existing participatory_texts functionality to better suit specific needs for participatory textwork, that we found in Austria. Demo-version can be found here: https://textwork.decidim-austria.org/

EnhancedTextwork is available as a Component for a Participatory Process.

We also extended some javascript code using webpacker.

This module needs at least Decidim v0.26.0 to work.

Add this line to your application's Gemfile:

gem 'decidim-enhanced_textwork'

And then execute:

bundle
bin/rails decidim_enhanced_textwork:install:migrations
bin/rails db:migrate

Within the scope of our project we improved some parts of the feature called “participatory_text”, which is part of the core module “decidim-proposals”. Unfortunately after finishing our work the decidim core team in Barcelona did not have resources available to integrate our results into the decidim core. For this reason we created a new module based on “decidim-proposals” including our participatory_text enhancements.

We named the base model for participatory texts Paragraph (instead of Proposal).

Our improvements span 3 areas described in the following sections:

• Participatory Text Frontend
• Participatory Text Result Export
• Participatory Text Import

To make working with a participatory text easier and more user friendly we rebuilt the design for the overview page and created a sidebar.

We called the page including the sidebar “overview” and added it to the routes of the proposals module:

lib/decidim/enhanced_textwork/engine.rb

To change the style of the comments to better fit the sidebar and to improve user experience we created a new class Decidim::EnhancedTextwork::CommentsCell that derives from the global Decidim::Comments::CommentsCell. That allowed us to overwrite the global comments cell view while still using most of the other views of the global CommentsCell.

• comments_cell.rb
• show.erb

We added a setting to allow hiding proposal titles, because numbered titles did not make sense for long texts. In our new module we enable this setting by default.

In Decidim every component (module) allows you to define settings that get then displayed automatically in the components edit view using the localized texts configured for example under en.decidim.components.enhanced_textwork.settings.global.hide_participatory_text_titles_enabled

settings.attribute :hide_participatory_text_titles_enabled, type: :boolean, default: true

see component.rb

Because enhanced_textwork is based on proposals, the Paragraph model is based on the Proposal model. For this reason all the features existing for proposals can also be used on enhanced_textwork. One of those features is the export of results. Until now exporting results was optimized for proposals and it didn’t make a lot of sense to export the results of collaborative work on a big text document consisting of many sections.

Existing export formats for proposals were defined in decidim-core:

• CSV
• Excel
• JSON

In a text-based participatory process the export of a text-document can help to continue working with the results. Hence we decided to add a new Word/docx export exclusively in the enhanced_textwork module:

lib/decidim/exporters/word.rb

To enable it, the export formats need to be defined in the component configuration:

lib/decidim/proposals/component.rb

To export in docx format we decided to use a more recent fork of the caracal gem by commonlit.

To add a new page for importing text directly from a rich text editor we had to add some routes in the admin_engine

Decidim already uses the quill richt text editor in many places, so we decided to also use it.

We created a new HtmlToMarkdown class that uses the kramdown gem to convert the html output of the quill editor to markdown, which is already the supported format for importing documents.

The new class had to be autoloaded from the proposals component

After importing text it was not possible to delete single proposals/paragraphs of the draft. You could only delete all proposals together. Therefore we added a delete button to each draft and added a new command and a destroy_draft controller action that we also added to the routes in the admin_engine:

pg_trgm is a PostgreSQL extension providing simple fuzzy string matching used in the Paragraph wizard to find similar published paragraphs (title and the body).

Create config variables in your app's /config/initializers/decidim-enhanced_textwork.rb:

Decidim::EnhancedTextwork.configure do |config|
  config.similarity_threshold = 0.25 # default value
  config.similarity_limit = 10 # default value
end

similarity_threshold(real): Sets the current similarity threshold that is used by the % operator. The threshold must be between 0 and 1 (default is 0.3).

similarity_limit: number of maximum results.

This module includes the following models to Decidim's Global Search:

• Paragraphs

Participatory texts persist each section of the document in a Paragraph.

When importing participatory texts all formats are first transformed into Markdown and is the markdown that is parsed and processed to generate the corresponding Paragraphs.

When processing participatory text documents three kinds of sections are taken into account.

• Section: each "Title 1" in the document becomes a section.
• Subsection: the rest of the titles become subsections.
• Article: paragraphs become articles.

Feel free to use the issues and pull requests to contribute to this module.

Software: AGPL-3.0 README: CC-BY-3.0 AT