decidim 0.27.9 → 0.28.0.rc4

data/docs/modules/customize/pages/content_security_policy.adoc

@@ -0,0 +1,53 @@
+= Configuring Content Security Policy Parameters
+
+This is a security feature that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks.
+By default, the CSP is enabled, and is configured to be as restrictive as possible, having the following default configuration:
+
+[source,ruby]
+....
+  {
+    "default-src" => %w('self' 'unsafe-inline'),
+    "script-src" => %w('self' 'unsafe-inline' 'unsafe-eval'),
+    "style-src" => %w('self' 'unsafe-inline'),
+    "img-src" => %w('self'),
+    "font-src" => %w('self'),
+    "connect-src" => %w('self'),
+    "frame-src" => %w('self'),
+    "media-src" => %w('self')
+  }
+....
+
+In order to customize the CSP we are providing, have 2 options, either by using a configuration key the initializer `config/initializers/decidim.rb` or by setting values in the Organization's system admin.
+
+Using the initializer is the recommended way to customize the CSP when you have multiple organizations sharing the same Decidim instance, sharing the same tools. Fox example, if you are using a custom map provider, you will need to add the domain to the CSP, so that the map can be displayed. In this case, you will need to add the following to your initializer:
+
+[source,ruby]
+....
+config.content_security_policies_extra = {
+  "connect-src" => %w(https://*.example.com),
+  "img-src" => %w(https://*.example.com)
+}
+....
+
+For specific organization setup, you could use the system panel to customize the Content Security Policies, by adding the domains or directives that you need to allow in the predesignated spots.
+
+Sometimes, there may be typos in your customization, and your rules will not be applied, if the directive is not in the allowed list of directives. Do not worry, if we encounter a directive that is not in the allowed list, we will log a warning to application console, and we will not apply the directive.
+
+You can check the https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP[Content Security Policy] documentation for more information.
+
+== Note for developers
+
+When developing custom modules, you may need to relax the CSP in order to be able to use a custom domain to load various things. In that case, you could build up your module so that would use a custom before action, that would relax the CSP for the specific request. For example:
+
+[source,ruby]
+....
+before_action :append_csp_directives
+
+# your controller actions here
+
+private
+
+def append_csp_directives
+  content_security_policy.append_csp_directive("frame-src", "https://example.com")
+end
+....

data/docs/modules/customize/pages/data_consent.adoc

@@ -15,7 +15,7 @@ By default there are four (4) data consent categories: **essential**, **preferen
 The recommended place for scripts is ```app/views/layouts/decidim/_head_extra.html.erb```.
 For example, if you want to add a script that requires marketing consent, you can add the following code:
 
-[source,javascript]
+[source,html]
 ----
 <script type="text/plain" data-consent="marketing">
   console.log("marketing data consent given");
@@ -72,7 +72,7 @@ Decidim.configure do |config|
 end
 ----
 
-When adding categories and items also remember to add the following translations:
+When adding categories and items also remember to add the following xref:customize:texts.adoc[translations]:
 
 For category:
 

data/docs/modules/customize/pages/images.adoc

@@ -2,6 +2,6 @@
 
 You can change most of the images (for instance the logo, main banner on homepage, contents of participatory processes, etc) through the Administration panel.
 
-As Decidim uses Webpacker, there's no way to override existing images including in Decidim.
+As Decidim uses Webpacker, there is no way to override existing images including in Decidim.
 
 If you want to add a new image you can do it as any Rails application, leaving it on your image's asset folder (`app/packs/images`) and using image_pack_tag helper (or asset_pack_path). You can see more documentation on http://guides.rubyonrails.org/webpacker.html[Rails guide].

data/docs/modules/customize/pages/index.adoc

@@ -16,9 +16,12 @@ Inside of your application you can customize it in different ways:
 
 * xref:customize:authorizations.adoc[Authorizations]
 * xref:customize:code.adoc[Code]
+* xref:customize:content_security_policy.adoc[Content security policy]
+* xref:customize:data_consent.adoc[Data consent]
 * xref:customize:gemfile.adoc[Gemfile]
 * xref:customize:images.adoc[Images]
 * xref:customize:javascript.adoc[Javascript]
+* xref:customize:logic.adoc[Logic]
 * xref:customize:menu.adoc[Menu]
 * xref:customize:oauth.adoc[OAuth]
 * xref:customize:styles.adoc[Styles]

data/docs/modules/customize/pages/javascript.adoc

@@ -17,12 +17,12 @@ $(function(){
 
 More information in https://guides.rubyonrails.org/webpacker.html[Rails Webpacker documentation].
 
-If you want to replace a whole file existin in Decidim you can do it by creating a file in your application with the same name and the same path. I.e: to replace `decidim-core/app/packs/src/decidim/editor.js` you should create in your Rails app a file in
-  `app/packs/src/decidim/editor.js` and it will have more priority over the Decidim file.
+If you want to replace a whole file existing in Decidim you can do it by creating a file in your application with the same name and the same path. I.e: to replace `decidim-core/app/packs/src/decidim/editor/index.js` you should create in your Rails app a file in
+  `app/packs/src/decidim/editor/index.js` and it will have more priority over the Decidim file.
 
 == Head extra file
 
-There's an special partial file for adding inline content in every public page. You just need to create a file called `app/views/layouts/decidim/_head_extra.html.erb`:
+There is an special partial file for adding inline content in every public page. You just need to create a file called `app/views/layouts/decidim/_head_extra.html.erb`:
 
 [source,javascript]
 ----
@@ -56,7 +56,7 @@ in your `config/initializers/decidim.rb` file. Please do notice that this has se
   config.enable_html_header_snippets = true
 ----
 
-Then you'll have a new textarea field called "Header snippets" in Administration -> Configuration -> Appearance (URL `/admin/organization/appearance/edit`):
+Then you will have a new textarea field called "Header snippets" in Administration -> Configuration -> Appearance (URL `/admin/organization/appearance/edit`):
 
 image::header-snippet.png[Header snippet]
 

data/docs/modules/customize/pages/logic.adoc

@@ -1,7 +1,7 @@
 = Change Decidim core logic within your application
 
 There are occasions you find yourself in a situation that you need to change Decidim core logic within your application. There are two ways to accomplish this goal, and we are going through these options here.
-As an example, we will add a new validation rule to the Admin panel, where Admin can not add projects with budgets more than half the total budget. Once we applied such limitation, admins should not be able to add a project with the cost of 5,001 euros to a budget with total of 10,000 euros.
+As an example, we will add a new validation rule to the Admin panel, where Admin cannot add projects with budgets more than half the total budget. Once we applied such limitation, admins should not be able to add a project with the cost of 5,001 euros to a budget with total of 10,000 euros.
 
 [#maximum-budget-rule]
 .Trying to create a project with the budget of €5,001 for a budget with the total amount of €10,000(My budget) reults in error(buttom-right error message)
@@ -49,7 +49,7 @@ The benefit of using concerns is that when we update Decidim gems to new version
 
 Concerns should be placed into the `concerns` folder within the top-level folder where you want to apply these concerns. In this case, we are adding a concern for the forms classes, so we should place the concerns related to forms to `app/forms/concerns`. If you do not have this folder available, create it first `mkdir -p app/forms/concerns`.
 
-Now, let's move our modifications from the first copy-paste example into a concern.
+Now, we can move our modifications from the first copy-paste example into a concern.
 
 . Create the file `app/forms/concerns/admin_project_form_extensions.rb`, and make the desired changes in that file as follows:
 [source,ruby]
@@ -71,13 +71,13 @@ end
 [source,ruby]
 ----
   config.to_prepare do
-    Decidim::Budgets::Admin::ProjectForm.include(Decidim::Budgets::Admin::ProjectForm.include(AdminProjectFormExtensions)
+    Decidim::Budgets::Admin::ProjectForm.include(AdminProjectFormExtensions)
   end
 ----
 This applies to almost all classes you want to change in Decidim but controllers and helpers are special cases due to order of how things are loaded in the Decidim boot process. If you want to add any changes to controllers or helpers, you need to wrap the `config.to_prepare` block within an initializer that is run at the correct phase of the boot process as follows:
 [source,ruby]
 ----
-  initializer "customizations", after: "decidim.action_controller" do
+  initializer "customizations", after: "decidim_core.action_controller" do
     config.to_prepare do
       # Add the controller/helper customizations here
     end

data/docs/modules/customize/pages/menu.adoc

@@ -9,15 +9,14 @@ After you install Decidim you can see it in several ways, depending on:
 . Which modules do you have activated
 . Which contents do you have in your database
 
-If you have the default modules and no contents, then you'll only see Home and Help.
+If you have the default modules and no contents, then you will only see Home and Help.
 
 Depending in the kind of space and module, then you can see or not some of the spaces:
 
-- For participatory processes, it appears when there's some published content by an administrator.
-- For assemblies, it appears when there's some published content by an administrator.
-- For consultations, you need to enable the module and it appears when there's some published content by an administrator.
-- For conferences, you need to enable the module and it appears when there's some published content by an administrator.
-- For initiatives, you need to enable the module. Every participant can see it, as anyone can create one. That's because is a bottom-up kind of mechanism.
+- For participatory processes, it appears when there is some published content by an administrator.
+- For assemblies, it appears when there is some published content by an administrator.
+- For conferences, you need to enable the module and it appears when there is some published content by an administrator.
+- For initiatives, you need to enable the module. Every participant can see it, as anyone can create one. That is because is a bottom-up kind of mechanism.
 
 Starting with 0.25.dev, Decidim Menu Api has been modified, in order to improve developer and administrators experience.
 The changes on the menu has deprecated the previous `menu.item` call, in favour of `menu.add_item` that has the following structure:
@@ -75,7 +74,7 @@ The menus are being defined as `Decidim.menu :identifier`. In order to render th
 - sidebar_menu will render the secondary admin section
 - simple_menu will render any submenus
 
-There's also a https://github.com/OpenSourcePolitics/decidim-module-navbar_links[NavBar links module] made by the community that you can use to add your custom links.
+There is also a https://github.com/OpenSourcePolitics/decidim-module-navbar_links[NavBar links module] made by the community that you can use to add your custom links.
 
 Finally if you want to dive in the code that handles this, a good starting point is the https://rubydoc.info/github/decidim/decidim/develop/Decidim/Menu[Menu API].
 

data/docs/modules/customize/pages/social_shares.adoc

@@ -0,0 +1,69 @@
+= Social shares services
+
+Starting with the v0.27.0, you have the following social shares services that you can enable:
+
+* Douban
+* Email
+* Facebook
+* Google Bookmark
+* Hacker News
+* LinkedIn
+* Odnoklassniki
+* Pinterest
+* Reddit
+* Telegram
+* Vkontakte
+* WhatsApp
+* X (former Twitter)
+* Xing
+
+== Configuration
+
+You can enable the social shares services by using the `DECIDIM_SOCIAL_SHARE_SERVICES` environment variable.
+
+The format of this variable is as follows
+
+[source,console]
+----
+DECIDIM_SOCIAL_SHARE_SERVICES="Facebook, X"
+----
+
+NOTE: Services names are case sensitive.
+
+== Default services
+
+By default we enable the following services: X, Facebook, WhatsApp and Telegram.
+
+image::social-share-modal-default.png[Social share modal]
+
+== Custom services
+
+If you have the need, you can enable your own service. To do that, as an example for a ficticious social service called "Foo", you will need to follow these steps:
+
+. Add the logo of your service to the images' pack at `app/packs/images/`. Following the example, it'd be "foo.svg"
+
+. Alternatively, you can provide any https://remixicon.com/ logo also. Simply as adding the icon key for such social share, e.g. "reddit-line"
+
+. In addition to the remixicon, icon_color property can be added, using an Hex color, e.g. "#ff4500"
+
+. Add the social share service block configuration at the bottom of your Decidim initializer:
+
+[source,ruby]
+----
+Decidim.register_social_share_service("Foo") do |service|
+  service.icon = "foo.svg" # (or "reddit-line")
+  service.icon_color = "#ff4500"
+  service.share_uri = "https://foo.example.com/share?url=%{url}"
+end
+----
+
+[NOTE]
+----
+Depending on the service, you could use the following variables in the share URI:
+* url
+* title
+* desc
+* image
+----
+
+. Add the "Foo" service to `DECIDIM_SOCIAL_SHARE_SERVICES` environment variable.

data/docs/modules/customize/pages/styles.adoc

@@ -1,6 +1,6 @@
 = CSS Styles with SASS
 
-One of the first things you'll want to do after you install Decidim is applying your own corporative image. You can do it on multiple ways:
+One of the first things you will want to do after you install Decidim is applying your own corporative image. You can do it on multiple ways:
 
 == Organization colors
 
@@ -12,7 +12,7 @@ This works for any Organization inside of a Muiltitenant.
 
 == Head extra file
 
-There's an special partial file for adding inline content in every public page. You just need to create a file called `app/views/layouts/decidim/_head_extra.html.erb`:
+There is an special partial file for adding inline content in every public page. You just need to create a file called `app/views/layouts/decidim/_head_extra.html.erb`:
 
 [source,stylesheet]
 ----
@@ -44,7 +44,7 @@ in your `config/initializers/decidim.rb` file. Please do notice that this has se
   config.enable_html_header_snippets = true
 ----
 
-Then you'll have a new textarea field called "Header snippets" in Administration -> Configuration -> Appearance (URL `/admin/organization/appearance/edit`):
+Then you will have a new textarea field called "Header snippets" in Administration -> Configuration -> Appearance (URL `/admin/organization/appearance/edit`):
 
 image::header-snippet.png[Header snippet]
 
@@ -54,14 +54,22 @@ Notice that you can resize this textarea.
 
 Decidim uses Webpacker to compile assets. There are two ways to customize CSS:
 
-1. if you want to redefine just CSS vars or Foundation settings, use _decidim-settings.scss
-2. if you want to redefine a specific snippet of CSS (let's say a few classes but not a whole file) you can use decidim_application.scss
-3. and of course you can overwrite whole files by copying them into the application i.e: to replace `decidim-core/app/packs/stylesheets/decidim/modules/_data-consent.scss` you should create in your Rails app a file in
-  `app/packs/stylesheets/decidim/modules/_data-consent.scss` and it will have more priority over the Decidim file.
+1. if you want to redefine a specific snippet of CSS (say a few classes but not a whole file) you can use decidim_application.scss
+2. and of course you can overwrite whole files by copying them into the application i.e: to replace `decidim-core/app/packs/stylesheets/decidim/modules/_data-consent.scss` you should create in your Rails app a file in `app/packs/stylesheets/decidim/modules/_data-consent.scss` and it will have more priority over the Decidim file.
+3. if you want to customize the application colors yo can use the admin interface.
 
 We use http://sass-lang.com/guide[SASS, with SCSS syntax] as CSS preprocessor.
 
-== Accesibility
+== Tailwind CSS
+
+Decidim uses Taiwind CSS as a CSS framework, which has a default configuration that is being handled by `tailwind.config.js` in the root of your project.
+
+Since this file is being managed by Decidim, it will be impossible to customize it.
+
+You can override the default configuration by creating a file  `config/tailwind.config.js.erb` starting from the following https://github.com/decidim/decidim/blob/develop/decidim-core/lib/decidim/assets/tailwind/tailwind.config.js.erb[content]
+
+== Accessibility
 
 To maintain accesibility level, if you add new colors use a http://webaim.org/resources/contrastchecker/[Color contrast checker] (WCAG AA is mandatory, WCAG AAA is recommended)
 
+For more information about accessibility, see the xref:develop:guide_accessibility.adoc[accessibility guide].

data/docs/modules/customize/pages/texts.adoc

@@ -4,7 +4,7 @@
 
 You can change most of the texts through the Administration panel.
 
-If you want to change a given text that isn't on the Administration panel, and belongs on Decidim code, you should first find out which key is being used. For instance, you want to change the home page text where it says "Let's build a more open, transparent and collaborative society.", you would search the text (using https://github.com/decidim/decidim/search?utf8=%E2%9C%93&q=%22Let%27s+build+a+more+open%2C+transparent+and+collaborative+society.%22&type=[github] or grep) and then you would extract that key and their parents. On this case it'd be:
+If you want to change a given text that is not on the Administration panel, and belongs on Decidim code, you should first find out which key is being used. For instance, you want to change the home page text where it says "Let's build a more open, transparent and collaborative society.", you would search the text (using https://github.com/decidim/decidim/search?utf8=%E2%9C%93&q=%22Let%27s+build+a+more+open%2C+transparent+and+collaborative+society.%22&type=[github] or grep) and then you would extract that key and their parents. On this case it'd be:
 
 [source,yml]
 ----

data/docs/modules/customize/pages/users_registration_mode.adoc

@@ -6,7 +6,7 @@ Decidim allows organizations to choose one of the three modes related to the reg
 
 This is the default mode. It enables the registration form and allow anyone to create a new account and log in.
 
-== Don't allow users to register, but allow existing users to login
+== Do not allow users to register, but allow existing users to login
 
 This mode disables the registration form, but allows existing users to log in. This mode could be useful for organizations with a closed census that do not want to offer other people to register.
 

data/docs/modules/customize/pages/views.adoc

@@ -1,10 +1,10 @@
 = Views (HTML)
 
-As usual you should make some tests with the changes that you made and configure a Continuous Integration environment for checking that your overrides doesn't get removed with new decidim versions.
+As usual you should make some tests with the changes that you made and configure a Continuous Integration environment for checking that your overrides does not get removed with new decidim versions.
 
 == Overrides
 
-To find what you need to change you'll need to make some detective work to find out which partial or view do you need to change. You can do so by:
+To find what you need to change you will need to make some detective work to find out which partial or view do you need to change. You can do so by:
 
 * looking at your application log and finding the lines that start with "Rendered"
 * inspecting with the web development tools of your browser, copying a special class and using `grep`, github search or your IDE search by multiple files to find out on which file this exists.
@@ -13,11 +13,11 @@ To find what you need to change you'll need to make some detective work to find
 
 If you want to override a view or partial given by Decidim you can do this just by naming it with the same filename that you already have. On more details, if you want to change the social media icons on the footer, you can do so by looking at which file you need to change, copying that file to your application with the same filename and directory structure, and making your local changes.
 
-As an example, if I want to change the footer, you'd need to search for the file (on this case, it's on https://github.com/decidim/decidim/blob/e181d7e67bdf915a3a8e58416c683f52346de047/decidim-core/app/views/layouts/decidim/_mini_footer.html.erb[`decidim-core/app/views/layouts/decidim/_mini_footer.html.erb`]), and copy that file to your own application on `app/views/layouts/decidim/_mini_footer.html.erb`).
+As an example, if I want to change the footer, you'd need to search for the file (on this case, it is on https://github.com/decidim/decidim/blob/5e636a1215774f27eddb29426ebc786c83df6c36/decidim-core/app/views/layouts/decidim/footer/_mini.html.erb[`decidim-core/app/views/layouts/decidim/footer/_mini.html.erb`]), and copy that file to your own application on `app/views/layouts/decidim/footer/_mini.html.erb`).
 
 == Deface method
 
-You'll need the https://github.com/spree/deface[`deface` gem] installed on your application, and follow their instructions on how to use the different overridign methods that they support.
+You will need the https://github.com/spree/deface[`deface` gem] installed on your application, and follow their instructions on how to use the different overridign methods that they support.
 
 As an example, if you want to change the footer, you can do so by creating the file `app/overrides/layouts/decidim/_main_footer/pre_footer.html.erb.deface` with these contents:
 
@@ -27,8 +27,36 @@ As an example, if you want to change the footer, you can do so by creating the f
 hello world
 ----
 
+=== View Models (a.k.a. Cells)
+
+Decidim uses the xref:develop:view_models_aka_cells.adoc[View Models (a.k.a. Cells)] to define parts of the user interface. Cells allow you to reduce complexity within the controllers and helpers, to separate relevant functionality only related to a specific part of a UI into its own encapsulated entity.
+
+Cells consists of two parts:
+
+. The cell class which controls the rendering logic and can define helper methods for the views
+. The view written in ERB as you are used to when writing normal Rails views
+
+If you want to customize any cells within your application, you can use the "filename method" described above to find the relevant cell in charge of rendering the content you want to modify and copying this file to the exact same path within your own `app` folder as where you found the view.
+
+If you want to customize the cell class logic, you can either copy that file to the same path where you found it and customize it there or implement concerns to keep better track of what you have changed in different parts of Decidim. See the xref:customize:logic.adoc[Logic customization guide] to learn more about this approach.
+
+If you want to customize cells within your modules, you need to add the following initializer to your module's engine to make them aware of the potential lookup path:
+
+[source,ruby]
+----
+module Decidim
+  module YourModule
+    class Engine < ::Rails::Engine
+      initializer "decidim_your_module.add_cells_view_paths" do
+        Cell::ViewModel.view_paths << File.expand_path("#{Decidim::YourModule::Engine.root}/app/cells")
+      end
+    end
+  end
+end
+----
+
 == New pages
 
 If you want to add a new HTML page, you can do this by working as a regular Rails application (ie, you can scaffold a new view and work with the HTML as usual).
 
-As an example of how to do this on Decidim Barcelona application, there's the https://github.com/AjuntamentdeBarcelona/decidim-barcelona/blob/d47d4a9ae6be26a0c5c4000907dda3c195579636/app/controllers/static_controller.rb[StaticController] (main accountability section pages). You should inherit your controller from Decidim::ApplicationController.
+As an example of how to do this on Decidim Barcelona application, there is the https://github.com/AjuntamentdeBarcelona/decidim-barcelona/blob/d47d4a9ae6be26a0c5c4000907dda3c195579636/app/controllers/static_controller.rb[StaticController] (main accountability section pages). You should inherit your controller from Decidim::ApplicationController.

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

@@ -8,4 +8,4 @@ Documentation for this API is auto-generated in each instance of Decidim, usuall
 
 Accessing that URL will give a full details of all the objects that can be requested and how. It includes the full field types reference.
 
-As an alternative, if you can't access that URL on your instance you can read about how this work https://github.com/decidim/decidim/blob/develop/decidim-api/docs/usage.md[Using the Decidim GraphQL API].
+As an alternative, if you cannot access that URL on your instance you can read about how this work https://github.com/decidim/decidim/blob/develop/decidim-api/docs/usage.md[Using the Decidim GraphQL API].

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

@@ -8,7 +8,7 @@ involved directly:
 
 But the presenters for the classes including `ActsAsAuthor` should also behave
 in a certain maneer. This has been resolved using the duck typing strategy
-(remember, if it quaks as as duck, then it is a duck). Thus, there's not any
+(remember, if it quaks as as duck, then it is a duck). Thus, there is not any
 interface declaring which are the methods to be implemented by the presenter
 of an author. Anyway one of the ``OfficialAuthorPresenter``s may be used as a
 reference.

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

@@ -0,0 +1,37 @@
+= Backports
+
+We only offer support for the last two mayor version.
+
+For instance, if we are on the version `0.28.0.dev`, we make backports for `v0.26.x` and `v0.27.x`. We only backport fixes and not features, as we want to respect xref:develop:guide_conventions.adoc[Semantic Versioning].
+
+The idea of a backport is to bring a given fix from the last development version to an older release.
+
+The process for making backports is the following:
+
+. Check in the git commit history what was the latest backports on the branch that you are working with. https://github.com/decidim/decidim/commits/release/0.27-stable[Example for v0.27]. Copy the number of the last PR backported.
+. Search in GitHub for the this PR in the list of merged PRs of the `type: fix`. https://github.com/decidim/decidim/pulls?page=1&q=is%3Apr+sort%3Aupdated-desc+label%3A%22type%3A+fix%22+is%3Amerged[Example URL].
+. Check the PRs merged just before and after this one. You need to find the last ones that were not backported already to start with the backport process. A fast way for checking this out is to open the PRs and see the mentions from the backports in the GitHub references.
+. Once you have the list of the PRs that you want to backport, you can start with the process by using the https://github.com/decidim/decidim/blob/develop/bin/backporter[backporter script]. This script mostly handles the branch creation, cherrypicking, labeling and pushing of the fix. For using it you will need to have a GitHub Personal Access Token.
+
+This is an example on how this command is called:
+
+```shell
+$ backporter --github-token=GITHUB_TOKEN --pull-request-id=10248 --version-number=0.27
+```
+
+And this is the current full documentation for this script:
+
+```shell
+$ ./bin/backporter --help
+Usage:
+  backporter --github-token=GITHUB_TOKEN --pull-request-id=PULL_REQUEST_ID --version-number=VERSION_NUMBER
+
+Options:
+  --github-token=GITHUB_TOKEN                                        # Required. Github Personal Access Token (PAT). It can be obtained from https://github.com/settings/tokens/new. You will need to create one with `public_repo` access.
+  --version-number=VERSION_NUMBER                                    # Required. The version number that you want to do the backport to. It must have the format MAJOR.MINOR.
+  --pull-request-id=PULL_REQUEST_ID                                  # Required. The ID of the pull request that you want to make the backport from. It should have the "type: fix" label.
+  [--exit-with-unstaged-changes], [--no-exit-with-unstaged-changes]  # Optional. Whether the script should exit with an error if there are unstaged changes in the current project.
+                                                                     # Default: true
+
+Backport a pull request to another branch
+```

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

@@ -9,7 +9,7 @@
 title System Component diagram for Decidim Applications (https://decidim.org)
 
 
-ContainerDb(rel_db, "Relational Database", "PostgreSQL 9.5.x", "Stores users, participatory processes, assemblies, consultations, initiatives, proposals, meetings, etc.")
+ContainerDb(rel_db, "Relational Database", "PostgreSQL 9.5.x", "Stores users, participatory processes, assemblies, initiatives, proposals, meetings, etc.")
 Container(filesystem, "File System", "Local or remote", "Stores uploads (images, documents, etc.)")
 Container(worker, "Worker", "Ruby on Rails 5.2", "ActiveJob queues for non syncronuos jobs. Works for open data requests, sending emails, etc.")
 
@@ -27,7 +27,6 @@ Container_Boundary(web_app, "Web Application") {
 
     Component(assemblies, "Assemblies module", "Ruby On Rails Engine (Space)", "A permament Space, mounted in /assemblies.")
     Component(conferences, "Conferences module", "Ruby On Rails Engine (Space)", "A temporal Space, mounted in /conferences.")
-    Component(consultations, "Consultations module", "Ruby On Rails Engine (Space)", "A temporal Space, mounted in /consultations.")
     Component(initiatives, "Initiatives module", "Ruby On Rails Engine (Space)", "A bottom-up Space, mounted in /initiatives. A participant can collect signatures to bring an issue to the organization.")
     Component(participatory_processes, "Participatory Processes module (Space)", "Ruby On Rails Engine", "A temporal Space, mounted in /processes.")
 
@@ -50,7 +49,6 @@ Container_Boundary(web_app, "Web Application") {
     ' Rel(proposals, participatory_processes, "Mounts in")
     ' Rel(proposals, conferences, "Mounts in")
 '
-    ' Rel(consultations, comments, "Consumes")
     ' Rel(initiatives, comments, "Consumes")
     ' Rel(accountability, comments, "Consumes")
     ' Rel(budgets, comments, "Consumes")
@@ -61,7 +59,6 @@ Container_Boundary(web_app, "Web Application") {
     ' Rel(proposals, comments, "Consumes")
     ' Rel(blogs, comments, "Consumes")
 '
-    ' Rel(consultations, admin, "Managed in")
     ' Rel(initiatives, admin, "Managed in")
     ' Rel(accountability, admin, "Managed in")
     ' Rel(budgets, admin, "Managed in")

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

@@ -14,8 +14,8 @@ Person(participant_user, "Participant User", "A registered user. Could also be v
 Person(administration_user, "Administration User", "A registered user with special permissions.")
 
 System_Boundary(decidim_system, "decidim"){
-    Container(web_app, "Web Application", "Ruby on Rails 5.2", "Allows participants to make decisions collaboratively through participatory processes, assemblies, consultations, initiatives, etc.")
-    ContainerDb(rel_db, "Relational Database", "PostgreSQL 9.5.x", "Stores users, participatory processes, assemblies, consultations, initiatives, proposals, meetings, etc.")
+    Container(web_app, "Web Application", "Ruby on Rails 5.2", "Allows participants to make decisions collaboratively through participatory processes, assemblies, initiatives, etc.")
+    ContainerDb(rel_db, "Relational Database", "PostgreSQL 9.5.x", "Stores users, participatory processes, assemblies, initiatives, proposals, meetings, etc.")
     Container(filesystem, "File System", "Local or remote", "Stores uploads (images, documents, etc.)")
     Container(worker, "Worker", "Ruby on Rails 5.2", "ActiveJob queues for non syncronuos jobs. Works for open data requests, sending emails, etc.")
 }

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

@@ -13,7 +13,7 @@ Person_Ext(visitor_user, "Visitor User", "Anonymous, non registered user.")
 Person(participant_user, "Participant User", "A registered user. Could also be verified.")
 Person(administration_user, "Administration User", "A registered user with special permissions.")
 
-System(decidim_system, "Decidim", "Allows participants to make decisions collaboratively through participatory processes, assemblies, consultations, initiatives, etc.")
+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.")

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

@@ -0,0 +1,44 @@
+= Cells
+
+As explained in dedicated page xref:develop:view_models_aka_cells.adoc[View Models (Cells)], a cell is an object that represent a fragment of your UI.
+
+In order to define a cell, you need to create a class that inherits from `Decidim::ViewModel` in your module.
+
+Cells classes are located in the `app/cells/decidim/<my_module>` directory, and named: `<my_cell>_cell.rb`.
+
+For example, if you want to create a cell that renders a simple text:
+
+```ruby
+# frozen_string_literal: true
+
+# app/cells/decidim/my_module/my_cell_cell.rb
+module Decidim
+  module MyModule
+    class MyCellCell < Decidim::ViewModel
+
+      def show
+        render if condition?
+      end
+
+      private
+
+      def condition?
+        true
+      end
+    end
+  end
+end
+```
+
+Then, you can render the cell in your view:
+
+```erb
+<%= cell("decidim/my_module/my_cell") =>
+```
+
+== More information
+
+* https://github.com/trailblazer/cells/blob/master/README.md[cells/README.md at master · trailblazer/cells]
+* http://trailblazer.to/gems/cells/[Trailblazer: Cells] / http://trailblazer.to/gems/cells/api.html[Trailblazer: Cells API]
+* https://www.sitepoint.com/introduction-to-cells-a-better-view-layer-for-rails/[Introduction to Cells: A Better View Layer for Rails -- SitePoint]
+