decidim 0.28.3 → 0.29.0.rc1

data/docs/modules/develop/pages/c4_context.adoc

@@ -15,7 +15,6 @@ Person(administration_user, "Administration User", "A registered user with speci
 
 System(decidim_system, "Decidim", "Allows participants to make decisions collaboratively through participatory processes, assemblies, initiatives, etc.")
 
-System_Ext(decidim_bulletin_board_system, "Decidim Bulletin Board", "Allows participants to cast end-to-end verifiable secret votes.")
 System_Ext(mail_system, "SMTP system (e-mail)", "Sends mails to users, like confirmations, reminders, notifications, etc.")
 System_Ext(etherpad_system, "Etherpad-Lite system", "Optional. Allows real-time text edition in Meetings.")
 System_Ext(geocoding_system, "Geocoding system", "Optional. An Open Street Maps provider, allows geographical localization of Proposals and Meetings..")
@@ -26,7 +25,6 @@ Rel(participant_user, decidim_system, "Uses")
 Rel(administration_user, decidim_system, "Uses")
 Rel_Back(participant_user, mail_system, "Sends e-mails to")
 Rel_Back(administration_user, mail_system, "Sends e-mails to")
-Rel_Back_Neighbor(decidim_bulletin_board_system, decidim_system, "Uses")
 Rel_Neighbor(decidim_system, mail_system, "Sends e-mails", "SMTP")
 Rel(decidim_system, oauth_system, "Uses")
 Rel(decidim_system, geocoding_system, "Uses")

data/docs/modules/develop/pages/classes/commands.adoc

@@ -2,11 +2,188 @@
 
 A command is custom class that manages the logic between your input, usually a xref:develop:classes/forms.adoc[form] object, an object and an user.
 
-Usually, a command is used to create, update or delete a object.
+Usually, a command is used to handle the interaction between the controller and the model.
 
 Commands are located in the `app/commands/decidim/<my_module>` directory, and named: `<action>_<my_resource>.rb`.
 
-In the below example, you will be able to see how the command (`CreateMyResource`), events (`Decidim::MyModule::MyResourceEvent`) and jobs (`Decidim::MyModule::MyCustomJob`) can be used.
+Because most of the time, a command is used to create, update a resource, we are shipping 3 commands by default, which you can inherit in your own commands:
+
+- xref:_decidimcommandscreateresource[`Decidim::Commands::CreateResource`] - for creating resources
+- xref:_decidimcommandsupdateresource[`Decidim::Commands::UpdateResource`] - for updating resources
+- xref:_decidimcommandsdestroyresource[`Decidim::Commands::DestroyResource`] - for destroying resources
+
+== Decidim::Commands::CreateResource
+
+In order to create a resource, you need to provide the form with the values you want to create.
+
+This is a custom implementation for demonstration purposes:
+
+```ruby
+# frozen_string_literal: true
+
+# app/commands/decidim/my_module/create_my_resource.rb
+module Decidim
+  module MyModule
+    class CreateMyResource < Decidim::Commands::CreateResource
+      # Tell the parent class which fields are going to be
+      # copied from the form
+      fetch_form_attributes :title, :description, :component
+
+      # Tell the parent class which files are going to be
+      # extracted from the form and attached to the resource
+      fetch_file_attributes :logo, :banner
+
+      # This is the class initializer. It can be ignored if you do not need
+      # to do anything special.
+      def initialize(form)
+        @form = form
+      end
+
+      private
+      # Tell the parent what is the ActiveRecord class needed
+      def resource_class = Decidim::MyModule::MyResource
+
+      # This method allows you to customize the log visibility
+      def extra_params = { visibility: "all" }
+
+      # The command has a before hook that you can use:
+      def run_before_hooks
+        # do something
+      end
+
+      # The command has an after hook that you can use:
+      def run_after_hooks
+        # do something
+      end
+
+      # Additionally, you can override the `attributes` method
+      # to add more attributes to the resource
+      def attributes
+        super.merge({
+          my_custom_attribute: form.my_custom_attribute
+        })
+      end
+
+      # You can also provide a custom form validation
+      # by overriding the `invalid?` method
+      def invalid?
+        return true if form.my_custom_attribute.blank?
+        super
+      end
+    end
+  end
+end
+```
+
+== Decidim::Commands::UpdateResource
+
+In order to update a resource, you need to provide the resource you want to update, and the form with the new values.
+
+This is a custom implementation for demonstration purposes:
+
+```ruby
+# frozen_string_literal: true
+
+# app/commands/decidim/my_module/update_my_resource.rb
+module Decidim
+  module MyModule
+    class UpdateMyResource < Decidim::Commands::UpdateResource
+      # Tell the parent class which fields are going to be
+      # copied from the form
+      fetch_form_attributes :title, :description, :component
+
+      # Tell the parent class which files are going to be
+      # extracted from the form and attached to the resource
+      fetch_file_attributes :logo, :banner
+
+      # This is the class initializer. It can be ignored if you do not need
+      # to do anything special.
+      def initialize(form, resource)
+        @form = form
+        @resource = resource
+      end
+
+      private
+      # Tell the parent what is the ActiveRecord class needed
+      def resource_class = Decidim::MyModule::MyResource
+
+      # This method allows you to customize the log visibility
+      def extra_params = { visibility: "all" }
+
+      # The command has a before hook that you can use:
+      def run_before_hooks
+        # do something
+      end
+
+      # The command has an after hook that you can use:
+      def run_after_hooks
+        # do something
+      end
+
+      # Additionally, you can override the `attributes` method
+      # to add more attributes to the resource
+      def attributes
+        super.merge({
+          my_custom_attribute: form.my_custom_attribute
+        })
+      end
+
+      # You can also provide a custom form validation
+      # by overriding the `invalid?` method
+      def invalid?
+        return true if form.my_custom_attribute.blank?
+        super
+      end
+    end
+  end
+end
+```
+
+== Decidim::Commands::DestroyResource
+
+If you do not need to do anything special, you can just call this command for any resource you want to destroy.
+
+If you still want to customize the command, you can do it like this:
+
+```ruby
+# frozen_string_literal: true
+
+# app/commands/decidim/my_module/destroy_my_resource.rb
+module Decidim
+  module MyModule
+    class DestroyMyResource < Decidim::Commands::DestroyResource
+      # This is the class initializer, that can be safely ignored if you do not perform additional actions
+      def initialize(resource, current_user)
+        @resource = resource
+        @current_user = current_user
+      end
+
+      private
+
+      # This method allows you to customize the log visibility
+      def extra_params = { visibility: "all" }
+
+      # The command has a before hook that you can use:
+      def run_before_hooks
+        # do something
+      end
+
+      # The command has an after hook that you can use:
+      def run_after_hooks
+        # do something
+      end
+
+      # You can also provide a custom validation by overriding the `invalid?` method
+      def invalid? = false
+    end
+  end
+end
+```
+
+== Advanced usage
+
+In the below example, you will be able to see an advanced example on how you can write your custom command (`CreateMyResource`), events (`Decidim::MyModule::MyResourceEvent`) and jobs (`Decidim::MyModule::MyCustomJob`) can be used.
+
 ```ruby
 # frozen_string_literal: true
 
@@ -23,23 +200,23 @@ module Decidim
       end
 
       def call
-      return broadcast(:invalid) if form.invalid?
+        return broadcast(:invalid) if form.invalid?
 
-      transation do
-         create_resource
-         dispatch_event
-         process_jobs
+        transaction do
+          create_resource
+          dispatch_event
+          process_jobs
+        end
+        broadcast(:ok)
       end
-      broadcast(:ok)
-    end
 
       private
 
       attr_reader :form, :resource
 
       def process_jobs
-      Decidim::MyModule::MyCustomJob.perform_later(resource)
-    end
+        Decidim::MyModule::MyCustomJob.perform_later(resource)
+      end
 
       def dispatch_event
         Decidim::EventsManager.publish(
@@ -47,31 +224,33 @@ module Decidim
           event_class: Decidim::MyModule::MyResourceEvent,
           resource:
         )
-    end
+      end
 
       def create_resource
-      @resource = Decidim.traceability.create!(
-        resource,
-        form.current_user,
-        **attributes,
-        visibility: "public-only"
-      )
-    end
+        @resource = Decidim.traceability.create!(
+          resource,
+          form.current_user,
+          **attributes,
+          visibility: "public-only"
+        )
+      end
 
       # this is mapping of
       # ActiveRecord::attribute => form.attribute
       def attributes
-      {
-        title: form.title,
-        description: form.description,
-        resource: form.resource
-      }
-    end
+        {
+          title: form.title,
+          description: form.description,
+          resource: form.resource
+        }
+      end
     end
   end
 end
 ```
 
+== Overriding Decidim commands
+
 Sometimes you may need to extend a `Decidim` supplied command, then you can either override the `attributes` method, either extend it with a `super` call.
 
 ```ruby

data/docs/modules/develop/pages/components.adoc

@@ -6,7 +6,7 @@ Components are the core contract between external xref:develop:modules.adoc[modu
 
 If you want to create a new component, you can use https://github.com/decidim/decidim/tree/develop/decidim-generators[decidim-generators] to
 automatically generate a decidim component skeleton, or copy the basic structure
-of an existing mantained plugin.
+of an existing maintained plugin.
 
 [source,console]
 ----
@@ -43,7 +43,7 @@ Decidim.register_component(:my_component) do |component|
 
   # Component hooks get called whenever relevant lifecycle events happen, like
   # adding a new component o destroying it. You always get passed the instance
-  # so you can act on it. Creating or destroying a comoponent is transactional
+  # so you can act on it. Creating or destroying a component is transactional
   # along with its hooks, so you can decide to halt the transaction by raising
   # an exception.
   #
@@ -125,7 +125,7 @@ Each attribute defined can be described through properties:
 * `text` and `string` attributes can be `translated`, which will allow admin users to enter values for every language.
 * `text` attributes can use an `editor` to edit them as HTML code
 * `enum` attributes should have a `choices` attributes that list all the possible values. This could be a lambda function.
-* they can be `readonly` in some cases, throught a lambda function that received the current component within the `context`.
+* they can be `readonly` in some cases, through a lambda function that received the current component within the `context`.
 
 [source,ruby]
 ----
@@ -167,7 +167,7 @@ This sections explains how to add dummy content to a development application.
 === Tips and Tricks
 
 * Take advantage of the Faker gem, already in decidim.
-* If you need content for i18n fields, you can use https://github.com/decidim/decidim/blob/develop/decidim-core/lib/decidim/faker/localized.rb[Localizaed], which uses `Faker` internally.
+* If you need content for i18n fields, you can use https://github.com/decidim/decidim/blob/develop/decidim-core/lib/decidim/faker/localized.rb[Localized], which uses `Faker` internally.
 
 == Assets
 
@@ -187,7 +187,7 @@ While the component is being developed, it will be simpler and faster to update
 
 Also, components might have one or many entrypoints (for CSSs and javascripts) and images. These entrypoints need to be manually added to `config/webpack/custom.js`. **Any change in both files** requires to restart `webpack-dev-server` process.
 
-Take into account that generating a new development application **overwrites** Webpacker configuration so these changes might be overwriten. That is why it is necessary, once the changes are stable enough, to update the generators files.
+Take into account that generating a new development application **overwrites** Webpacker configuration so these changes might be overwritten. That is why it is necessary, once the changes are stable enough, to update the generators files.
 
 === Updating Webpacker configuration for the generators
 

data/docs/modules/develop/pages/custom_seed_data.adoc

@@ -27,5 +27,5 @@ If you set the variables _before_ creating the seeds data, the values in those v
 * `SMTP_PORT`: The port used to connect to your email sending system.
 * `DECIDIM_SYSTEM_USER_PASSWORD`: The password for the System user. Useful to hide access to the System panel, where the SMTP config can be retrieved in plain text.
 
-This is useful, for example, to set up a staging application open to anyone, and use Sendgrid as a mailing system. By changing the default password only you will be able to access the System panel, so nobody will be able to see the credentials used to connect to Sendgrid.
+This is useful, for example, to set up a staging application open to anyone, and use SendGrid as a mailing system. By changing the default password only you will be able to access the System panel, so nobody will be able to see the credentials used to connect to SendGrid.
 

data/docs/modules/develop/pages/embeddable.adoc

@@ -11,7 +11,7 @@ or even `Meetings` component in an easy way with the `embeddable` option that of
 
 == How to
 
-All that you have to do, is to enter into whathever space/component you want to share info to, and look for down right part of the page to find embeddable share option.
+All that you have to do, is to enter into whatever space/component you want to share info to, and look for down right part of the page to find embeddable share option.
 
 If it is embeddable, you will see `embed <\>` option there.
 

data/docs/modules/develop/pages/endorsable.adoc

@@ -20,7 +20,7 @@ For performance, an endorsable has a counter cache of endorsements.
 |   ((Proposal,...))   |                                   +-------------+
 +----------------------+  0..N +--------------------+   +--+Decidim::User|
 |-has_many endorsements|-------+Decidim::Endorsement|   |  +-------------+
-|#counter cahce column |       +--------------------+   |
+|#counter cache column |       +--------------------+   |
 |-endorsements_counter |       |-author: may be a   |<--+
 +----------------------+       |         user or a  |   |
                                |         user_group |   |  +------------------+
@@ -81,7 +81,7 @@ To render this button, `decidim-core` offers the `decidim/endorsement_buttons` c
 cell("decidim/endorsement_buttons", resource)
 ----
 
-This cell, renders the endorsements counter and the endorsement button by default. But it has the possibility to be invoked to render elements sepparately.
+This cell, renders the endorsements counter and the endorsement button by default. But it has the possibility to be invoked to render elements separately.
 
 [source,ruby]
 ----

data/docs/modules/develop/pages/guide_conventions.adoc

@@ -2,7 +2,7 @@
 
 == GitFlow Branching model
 
-The Decidim respository follows the GitFlow branching model. There are good documentations on it at:
+The Decidim repository follows the GitFlow branching model. There are good documentations on it at:
 
 * https://nvie.com/posts/a-successful-git-branching-model/[the original post]
 * https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow[Atlassian tutorial]
@@ -25,7 +25,7 @@ Please note that Decidim does not use the `master` branch.
 
 == Naming branches
 
-We would like to have all branches following this namings:
+We would like to have all branches following this naming convention:
 
 |===
 | Branch prefix | Comment
@@ -34,7 +34,7 @@ We would like to have all branches following this namings:
 | Internal work. For instance, automatisms, etc. No production code change.
 
 | ci/
-| For continous integration related tasks. No production code change.
+| For continuous integration related tasks. No production code change.
 
 | deps/
 | For dependency management tasks.
@@ -67,7 +67,7 @@ After the prefix we recommend to add some words that describe what the change is
 . feature/add-pagination-to-moderated-users
 . fix/free-text-choice-answer
 
-The rationale behind this is that we do not like to have the issue number (`fix/9123` or just `9123`) as that difficults working with `git`.
+The rationale behind this is that we do not like to have the issue number (`fix/9123` or just `9123`) as that is difficult to work with in `git`.
 
 == Git commit messages and Pull Request titles
 
@@ -87,7 +87,7 @@ For keeping track of changes we like the rules of https://keepachangelog.com/en/
 
 In the past we kept a file for all the development of a given version but that was difficult to maintain, as we had conflicts all the time. See the full discussion in https://github.com/decidim/decidim/issues/5908[#5908]. We decided that:
 
-* We will not ask CHANGELOG for all the changes make on this repository. We will ask for CHANGELOG instructions only for special changes that really need some actions on part of developers/implementers or something to comunicate on the releases notes
+* We will not ask CHANGELOG for all the changes make on this repository. We will ask for CHANGELOG instructions only for special changes that really need some actions on part of developers/implementers or something to communicate on the releases notes
 * The CHANGELOG will be manually made as part of the release process with the tooling from git (`git log v0.20.0..v0.20.1 --grep " (#[0-9]\+)" --oneline`) or https://github.com/decidim/decidim/compare/v0.20.0...v0.20.1[github]
 
 == Semantic Versioning
@@ -105,5 +105,5 @@ For more information, refer to the xref:develop:guide_accessibility.adoc[Decidim
 
 == JavaScript
 
-* Do not use CSS classes to bind JavaScript selectors or Ruby specs. Try to use an `id` (with the `js-` preffix) or a `data-attribute` as selector, in order to shrink the couplish between changing technologies.
+* Do not use CSS classes to bind JavaScript selectors or Ruby specs. Try to use an `id` (with the `js-` prefix) or a `data-attribute` as selector, in order to shrink the coupling between changing technologies.
 * Do not use jQuery if you can do it with vanilla JavaScript. Specially try to not introduce new code with jQuery, and if you are working with a legacy file take consider migrating it to vanilla JS.

data/docs/modules/develop/pages/guide_development_app.adoc

@@ -3,7 +3,7 @@
 In order to start developing you will need what is called a `development_app`. This is nearly the same as a new Decidim
 app (that you can create with `decidim app_name`) but with a Gemfile pre-configured for local development and some other small config modifications.
 
-We recommend that you first have a xref:install:manual.adoc[working Decidim app] so that you have fullfilled all the necessary
+We recommend that you first have a xref:install:manual.adoc[working Decidim app] so that you have fulfilled all the necessary
 system and services requirements, like having a working Ruby installation, PostgreSQL, Node.JS, etc.
 
 You will need to configure the PostgreSQL database before anything. For this,
@@ -49,6 +49,7 @@ On creation, these steps are automatically invoked by the generator:
 * `bin/rails decidim:upgrade`
 * `bin/rails db:create`
 * `bin/rails db:migrate`
+* `bin/rails assets:precompile`
 * `bin/rails db:seed`
 
 Mind that if everything went well you should not need to run these commands manually.

data/docs/modules/develop/pages/guide_example_apps.adoc

@@ -27,7 +27,7 @@ image::helsinki.png[Helsinki OmaStadi]
 
 Some highlights:
 
-* They have their https://github.com/City-of-Helsinki/decidim-helsinki/blob/b9a09e570eb6090dee93f2ee73b5951882c74755/Gemfile[Gemfile] with lots of modules with their own code. Some of them are also in ruybgems (like `decidim-access_requests`, `decidim-antivirus`, `decidim-mpassid`, `decidim-process_groups_content_block`, `decidim-suomifi`, `decidim-term_customizer`), others are only in Github (`decidim-accountability_simple`, `decidim-apiauth`, `decidim-combined_budgeting`, `decidim-plans`, `decidim-redirects`). They even use a module made by other organization in the community (`decidim-budgets_enhanced`)
+* They have their https://github.com/City-of-Helsinki/decidim-helsinki/blob/b9a09e570eb6090dee93f2ee73b5951882c74755/Gemfile[Gemfile] with lots of modules with their own code. Some of them are also in ruybgems (like `decidim-access_requests`, `decidim-antivirus`, `decidim-mpassid`, `decidim-process_groups_content_block`, `decidim-suomifi`, `decidim-term_customizer`), others are only in GitHub (`decidim-accountability_simple`, `decidim-apiauth`, `decidim-combined_budgeting`, `decidim-plans`, `decidim-redirects`). They even use a module made by other organization in the community (`decidim-budgets_enhanced`)
 * They have their UI customized to their needs. See the https://github.com/City-of-Helsinki/decidim-helsinki/tree/a7396a312cc04198654a86d66c2a7de556c212af/app/assets/stylesheets[CSS] and https://github.com/City-of-Helsinki/decidim-helsinki/tree/a7396a312cc04198654a86d66c2a7de556c212af/app/views[HTML (views)].
 * They have an awesome README explaining how it works and what changes have made.
 

data/docs/modules/develop/pages/guide_github_projects.adoc

@@ -1,6 +1,6 @@
 = GitHub Projects Workflow
 
-This is an internal document on how we are organizing the development of Decidim with external contractors through Github projects.
+This is an internal document on how we are organizing the development of Decidim with external contractors through GitHub projects.
 
 There are three teams:
 

data/docs/modules/develop/pages/guide_migrate_webpacker_app.adoc

@@ -43,7 +43,7 @@ This task do a few steps to allow the Rails instance to have a webpacker instanc
 
 This task is automatically performed every time decidim is updated, to get the latest Webpack configuration. This happens when you run the `decidim:upgrade` task.
 
-=== Copy Decidim custom CSS and Javascript
+=== Copy Decidim custom CSS and JavaScript
 
 `webpacker:install` task should have created to you the following dirs structure:
 
@@ -104,7 +104,7 @@ If any of the CSS is re-defining CSS vars add them to `_decidim-settings.scss`.
 
 === Migrate javascripts
 
-Existing javascripts should be moved from `app/assets/javascsripts` to `app/packs/src` and imported with `import` into `decidim_application.js`. Take into account that you might need to adjust a bit the paths of the `import` to adjust them to the new locations.
+Existing javascripts should be moved from `app/assets/javascripts` to `app/packs/src` and imported with `import` into `decidim_application.js`. Take into account that you might need to adjust a bit the paths of the `import` to adjust them to the new locations.
 
 If that JS file is replacing a Decidim file, there is no need to add it to `decidim_application.js`
 

data/docs/modules/develop/pages/guide_migrate_webpacker_module.adoc

@@ -109,7 +109,7 @@ What you should do instead is to follow the asset compilation migration guide ab
 
 base_path = File.expand_path("..", __dir__)
 
-# Register the additonal path for Webpacker in order to make the module's
+# Register the additional path for Webpacker in order to make the module's
 # stylesheets available for inclusion.
 Decidim::Webpacker.register_path("#{base_path}/app/packs")
 

data/docs/modules/develop/pages/maintainers/releases.adoc

@@ -231,10 +231,10 @@ NOTE: When you bump the version, the generator tests will fail because the gems
  .. Re-run the failed generators tests at the release branch.
  .. Create a new release at this repository, just go to the https://github.com/decidim/decidim/releases[releases page] and create a new one.
 . Update Decidim's Docker repository as explained in the Docker images section below.
-. Update Crowdin synchronization configuration with Github:
+. Update Crowdin synchronization configuration with GitHub:
  .. Add the new `release/x.y-stable` branch.
  .. Remove from Crowdin branches that are not officially supported anymore.
-That way they do not synchronize with Github.
+That way they do not synchronize with GitHub.
 . Update the version in the documentation system that we use, Antora. For the https://github.com/decidim/decididm[decidim repository] this is done automatically when bumping the versions. For the https://github.com/decidim/documentation[documentation repository]:
 ... Create and push the branch in that repository: `git checkout release/0.XX-stable && git push origin release/x.y-stable`
 ... Add the new version on the https://github.com/decidim/documentation/blob/develop/antora-playbook.yml[antora-playbook.yml] `branches` key, for the both sources (decidim and documentation repository). Do not forget to also remove the oldest and change the new default in the `start_page` key. For instance for v0.28 this is how it'd look like:
@@ -267,8 +267,6 @@ index 31be47c..75c7d5e 100644
          - release/0.27-stable
 -        - release/0.26-stable
          - develop
-     - url: https://github.com/decidim/decidim-bulletin-board
-       start_path: docs
 ----
 After you commit this change in `develop` branch you will have to wait a couple minutes for the automatic deployment to see it live at https://docs.decidim.org.
 

data/docs/modules/develop/pages/managing_translations_i18n.adoc

@@ -5,12 +5,12 @@
 Decidim uses https://crowdin.com/[Crowdin] to manage the translations.
 
 * Whenever someone https://github.com/decidim/decidim/pull/1814/files#diff-c78c80097da59920d55b3f462ca21afaR177[adds a new translation key] to _Decidim_, _Crowdin_ gets notified and the new content is available to be translated from https://crowdin.com/project/decidim[Crowdin's Decidim dashboard].
-* When a translator translates any key from Crowdin, it automatically creates a https://github.com/decidim/decidim/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3Adecidim-bot%20Crowdin[PR in Github], adding the keys in the corresponding _yaml_ files.
+* When a translator translates any key from Crowdin, it automatically creates a https://github.com/decidim/decidim/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3Adecidim-bot%20Crowdin[PR in GitHub], adding the keys in the corresponding _yaml_ files.
 * 🌈
 
 == Adding a new language
 
-* Setup the new language in https://crowdin.com/project/decidim[_Crowdin's Decidim project_] (or open an issue on Github asking an admin to do that).
+* Setup the new language in https://crowdin.com/project/decidim[_Crowdin's Decidim project_] (or open an issue on GitHub asking an admin to do that).
 * Add the locale mapping in the `crowdin.yml` file
 * Translate at least one key from every engine, so, your _yaml_ files are not empty. The easiest way to do this is to automatically translate and sync all the content. Later you will be able to fix the content that was not properly translated.
 * Add the new language to `available_locales` (https://github.com/decidim/decidim/pull/1991[PR]).

data/docs/modules/develop/pages/maps.adoc

@@ -6,7 +6,7 @@ If you want to create your own provider integration, you will need to find a ser
 
 * https://en.wikipedia.org/wiki/Geocoding[A geocoding server] in order to turn user entered addresses into https://en.wikipedia.org/wiki/Geographic_coordinate_system[geocoordinates].
 * https://en.wikipedia.org/wiki/Autocomplete[A geocoding autocompletion server] in order to suggest and predict addresses based on the user input and turning these suggested addresses into https://en.wikipedia.org/wiki/Geographic_coordinate_system[geocoordinates].
-* https://en.wikipedia.org/wiki/Tile_Map_Service[A map tile server] for the dynamic maps, preferrably one that is compatible with the default https://leafletjs.com/[Leaflet] map library.
+* https://en.wikipedia.org/wiki/Tile_Map_Service[A map tile server] for the dynamic maps, preferably one that is compatible with the default https://leafletjs.com/[Leaflet] map library.
 * https://wiki.openstreetmap.org/wiki/Static_map_images[A static map image server] for the static map images e.g.
 on the proposal pages.
 This service is optional as Decidim will use the dynamic map tiles to generate a similar map element if the static map image cannot be provided.
@@ -118,7 +118,7 @@ Please refer to the Geocoder gem's https://github.com/alexreisner/geocoder/blob/
 
 === Defining the geocoding autocompletion maps utility
 
-For the geocoding autocompletion map functionality, you should preferrably use a service provider that is compatible with https://github.com/komoot/photon[Photon] which is already integrated with Decidim.
+For the geocoding autocompletion map functionality, you should preferably use a service provider that is compatible with https://github.com/komoot/photon[Photon] which is already integrated with Decidim.
 
 If this is not possible, you can also create a custom geocoding autocompletion maps utility for your own service provider by defining the following empty class to start with:
 
@@ -145,7 +145,7 @@ See below for further notes about the builder class.
 * `builder_options` - A method that prepares the options for the builder instance that is used to create the maps in the front-end.
 By default, this is an empty hash that needs to be configured for each provider.
 
-To see an example how to customize the static map utility, take a look at the link:/decidim-core/lib/decidim/map/provider/autocomplete/here.rb[HERE Maps geocoding autocomletion utility].
+To see an example how to customize the static map utility, take a look at the link:/decidim-core/lib/decidim/map/provider/autocomplete/here.rb[HERE Maps geocoding autocompletion utility].
 
 In order to provide configuration options for the geocoding autocompletion, you can pass them directly through the maps configuration with the following syntax:
 
@@ -232,7 +232,7 @@ The result objects need to contain the following keys:
 * `key` - The key which will be matched against the user entered input
 * `value` - The value which will be added to the address input if the user decides to select this value
 
-Optionally, you can also include a `coordinates` key in the result object which contains an array of two cordinates (latitude and longitude respectively).
+Optionally, you can also include a `coordinates` key in the result object which contains an array of two coordinates (latitude and longitude respectively).
 You can also include any other data you might need in the front-end for these results but it will be not used by Decidim.
 
 The final code would look something like follows:
@@ -404,7 +404,7 @@ L.tileLayer(
 
 === Defining the static maps utility
 
-For the static map functionality, you should preferrably use a service provider that is compatible with https://github.com/jperelli/osm-static-maps[osm-static-maps] which is already integrated with Decidim.
+For the static map functionality, you should preferably use a service provider that is compatible with https://github.com/jperelli/osm-static-maps[osm-static-maps] which is already integrated with Decidim.
 
 If this is not possible, you can also create a custom static maps utility for your own service provider by defining the following empty class to start with:
 

data/docs/modules/develop/pages/metrics.adoc

@@ -76,7 +76,7 @@ Only available for `ParticipatorySpaces` (restricted to `ParticipatoryProcesses`
 
 == Persistence
 
-The metrics module percomutes calculations and persists them into
+The metrics module precomputes calculations and persists them into
 `decidim_metrics` database table. So this module only uses one single table to
 persist metrics from all times and types.
 

data/docs/modules/develop/pages/modules.adoc

@@ -140,7 +140,7 @@ module Decidim
           root to: "authorizations#new"
         end
 
-        # This is a Dedicim::Verifications specific initializer
+        # This is a Decidim::Verifications specific initializer
         initializer "decidim_verifications_my_verifier.verification_workflow" do |_app|
           Decidim::Verifications.register_workflow(:my_verifier) do |workflow|
             workflow.engine = Decidim::Verifications::MyVerifier::Engine

data/docs/modules/develop/pages/newsletter_templates.adoc

@@ -1,6 +1,6 @@
 = Newsletter templates
 
-The newsletter templates allow the user to select a template amongst a set of of them, and use it as base to send newsletters. This allow for more customization on newsletter, tematic newsletters, etc.
+The newsletter templates allow the user to select a template amongst a set of of them, and use it as base to send newsletters. This allow for more customization on newsletter, thematic newsletters, etc.
 
 Code-wise, they use the content blocks system internally, so xref:develop:content_blocks.adoc[check the docs] for that section first.
 
@@ -44,7 +44,7 @@ Then we define the cell that will be used to render the form in the admin sectio
 
 In the third line inside the block we define the I18n path to the public name of the template. This name will serve as identifier for the users who write the newsletters, so be sure to make it descriptive.
 
-After that we define the images this newsletter supports. We give it a unique name, the class name of the uploader we will use (the example one is the default one, but you might want to customize this value) and a way to preview this image. This preview image will only be used in the "Preview" page of the template, it is not a fallback. If you want a fallback, please implement it through a custom uploader (see ``carrierwave``'s docs for that). There is no limit of the amount of images you add.
+After that we define the images this newsletter supports. We give it a unique name, the class name of the uploader we will use (the example one is the default one, but you might want to customize this value) and a way to preview this image. This preview image will only be used in the "Preview" page of the template, it is not a fallback. If you want a fallback, please implement it through a custom uploader. There is no limit of the amount of images you add.
 
 Finally, we define the attributes for the newsletter. In this case we define a body attribute, which is a translatable text. Whether this text require an editor or not will be defined by the settings cell. We also have a way to preview that attribute. There is no limit on the number of attributes you define.