decidim 0.26.2 → 0.27.0.rc2

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

@@ -68,8 +68,8 @@ You can download these files directly with these commands:
 
 [source,console]
 ----
-mkdir -p app/packs/src/decidim app/packs/stylesheets/decidim app/packs/stylesheets/images
-touch app/packs/src/decidim/.keep app/packs/stylesheets/decidim/.keep app/packs/stylesheets/images/.keep
+mkdir -p app/packs/src/decidim app/packs/stylesheets/decidim app/packs/images
+touch app/packs/src/decidim/.keep app/packs/stylesheets/decidim/.keep app/packs/images/.keep
 wget https://raw.githubusercontent.com/decidim/decidim/develop/decidim-generators/lib/decidim/generators/app_templates/decidim_application.js -O app/packs/src/decidim/decidim_application.js
 wget https://raw.githubusercontent.com/decidim/decidim/develop/decidim-generators/lib/decidim/generators/app_templates/decidim_application.scss -O app/packs/stylesheets/decidim/decidim_application.scss
 wget https://raw.githubusercontent.com/decidim/decidim/develop/decidim-generators/lib/decidim/generators/app_templates/_decidim-settings.scss -O app/packs/stylesheets/decidim/_decidim-settings.scss
@@ -84,6 +84,16 @@ Copy the existing images from `app/assets/images` to `app/packs/images`. Images
 cp -rp app/assets/images/* app/packs/images/
 ----
 
+For instance, add the image "app/packs/images/test.png" in a view using the helper:
+
+[source,erb]
+----
+<%= image_pack_tag "media/images/test.png" %>
+----
+
+Note that, by default, all images are flattened in a single directory (any subdirectory structure is lost when requiring an image using the `image_pack_tag`).
+So, if you have a file in a subdirectory such as `app/packs/images/subfolder/test.png`, you still need to call for the image using `image_pack_tag "media/images/test.png"`
+
 === Migrate stylesheets
 
 Existing stylesheets should be moved from `app/assets/stylesheets` to `app/packs/stylesheets` and imported with `@import` into `decidim_application.scss`. Take into account that you might need to adjust a bit the paths of the `@import` to adjust them to the new locations.
@@ -111,6 +121,16 @@ Sometimes assets are included in `vendor/assets/` folder or imported from gems.
 1. if the asset is a javascript that is available as npm package the recommendation is to add it to package.json with `npm install`. If it's not available you might want to copy it to `app/packs/src` and import it.
 2. if the asset is a stylesheet it should be copied to `app/packs/stylesheets` and imported with `@import...` from `_decidim-settings.scss`. Alternatively you can use the optional asset includes as described below to include these in the Decidim main SCSS files.
 
+=== Migrate uploads to ActiveStorage
+
+The old method (CarrierWave) to handle user uploads has changed, now it uses ActiveStorage.
+This means that all the old files need to be migrated to the new system. Use the following rake task to perform this task:
+
+[source,console]
+----
+RAILS_ENV=production bin/rails decidim:active_storage_migrations:migrate_from_carrierwave_to_active_storage
+----
+
 === Optional asset includes
 
 Decidim Webpacker provides a new configuration convention that allows you to add extra configurations for webpacker using a configuration file named `config/assets.rb`. Within this file, you have the following API methods available:
@@ -177,7 +197,7 @@ Decidim.register_assets_path File.expand_path("app/packs", Rails.application.roo
 
 The deployment needs to be updated to manually run `npm install` before assets are precompiled.
 
-In the case of Capistrano this can be done with a before hook:
+In the case of Capistrano this can be done with a before hook (can be added at the end of your `config/deploy.rb` file):
 
 [source,ruby]
 ----
@@ -186,9 +206,7 @@ namespace :deploy do
   task :decidim_webpacker_install do
     on roles(:all) do
       within release_path do
-        with rails_env: fetch(:rails_env) do
-          execute "npm ci"
-        end
+        execute :npm, "install"
       end
     end
   end
@@ -199,6 +217,7 @@ end
 
 Also, in the case of Capistrano it's interesting to add to the shared_paths the following folders:
 
+* `storage` *IMPORTANT!*
 * `tmp/webpacker-cache`
 * `node_modules`
 * `public/decidim-packs`
@@ -215,3 +234,24 @@ npm ERR!
 ----
 
 Then you need to check again that you're using the correct Node.js and NPM versions.
+
+In some case it might be that some packages are not well resolved when installing NPM modules. If you get messages like:
+
+[source,console]
+----
+...
+[webpack-cli] Error: Cannot find module '@rails/webpacker'
+...
+----
+
+These might be due some kind of corruption in your `package-json.lock` file, you can try either to remove this file and recreate it with `npm install` or to add the package `@rails/webpacker` manually in your `package.json` file next to the `@decidim/webpacker` package:
+
+[source,json]
+----
+...
+    "@decidim/webpacker": "^0.25.2",
+    "@rails/webpacker": "^6.0.0-rc.5",
+...
+----
+
+Then execute `npm install`.

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

@@ -1,6 +1,6 @@
 = Custom map providers
 
-Decidim can be configured to use multiple different xref:/docs/services/maps.adoc[map service providers] but it can be also extended to use any possible service provider out there.
+Decidim can be configured to use multiple different xref:services:maps.adoc[map service providers] but it can be also extended to use any possible service provider out there.
 
 If you want to create your own provider integration, you will need to find a service provider that provides all the following services:
 
@@ -12,12 +12,12 @@ 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.
 
 One option is to host some or all of these services yourself as there are open source alternatives available for all of these services.
-More information about self hosting is available at the link:/docs/services/maps.md#combining-multiple-service-providers[maps and geocoding configuration] documentation.
+More information about self hosting is available at the xref:services:maps.adoc#combining-multiple-service-providers[maps and geocoding configuration documentation].
 
-You may also decide to link:/docs/services/maps.md#disabling[disable some of the services] that are not available at your service provider but in order to get the full out of Decidim, it is recommended to find a service provider with all these services.
+You may also decide to xref:services:maps.adoc#disabling[disable some of the services] that are not available at your service provider but in order to get the full out of Decidim, it is recommended to find a service provider with all these services.
 
 In case you want to use different service providers for the different categories of map services, that is also possible.
-Instructions for this are provided in the link:/docs/services/maps.md#combining-multiple-service-providers[maps and geocoding configuration] documentation.
+Instructions for this are provided in the xref:services:maps.adoc#combining-multiple-service-providers[maps and geocoding configuration documentation].
 
 == Creating your own map service provider
 
@@ -312,7 +312,7 @@ For the dynamic map functionality, you should primarily use a service provider t
 You can also integrate to services that are not compatible with Leaflet but it will cause you more work and is not covered by this guide.
 
 Please note that you don't necessarily even need to create your own dynamic maps utility if your service provider is already compatible with the link:/decidim-core/lib/decidim/map/provider/dynamic_map/osm.rb[`Decidim::Map::Provider::DynamicMap::Osm`] provider.
-In order to configure your custom OSM compatible service provider take a look at the link:/docs/services/maps.md#configuring-open-street-maps-based-service-providers[maps and geocoding configuration] documentation.
+In order to configure your custom OSM compatible service provider take a look at the xref:services:maps.adoc#configuring-open-street-maps-based-service-providers[maps and geocoding configuration] documentation.
 
 If your service provider is not fully compatible with the default OSM provider, you can start writing your customizations by creating an empty dynamic map provider utility with the following code:
 
@@ -496,4 +496,4 @@ In this case, the static map utility can be empty as you won't need any customiz
 
 After you have finished all the steps shown above, you will need to configure your service provider for Decidim.
 The configuration key for the example service provider referred to in this documentation would be `:your_provider`.
-For configuration, refer to the xref:/docs/services/maps.adoc[maps and geocoding configuration] documentation.
+For configuration, refer to the xref:services:maps.adoc[maps and geocoding configuration documentation].

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

@@ -117,3 +117,7 @@ Relations around `decidim_metrics` table:
                            | [polymorphic]  |
                            +----------------+
 ----
+
+== Troubleshooting
+
+If you find problems in your metrics numbers you can follow the guide xref:develop:troubleshooting_metrics.adoc[Troubleshooting metrics].

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

@@ -101,7 +101,7 @@ the https://github.com/decidim/decidim/network/dependents[dependency graph]. See
   . Using the Admin panel
   . Generate logs on Admin panel if admins can operate on it
   . GraphQL API
-  . Data Portability
+  . Download your data
   . Endorsable
   . Followable
   . Embeddable

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

@@ -2,7 +2,7 @@
 
 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.
 
-Code-wise, they use the content blocks system internally, so https://github.com/decidim/decidim/blob/develop/docs/advanced/content_blocks.md[check the docs] for that section first.
+Code-wise, they use the content blocks system internally, so xref:develop:content_blocks.adoc[check the docs] for that section first.
 
 == Adding a new template
 

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

@@ -41,7 +41,7 @@ data = {
   followers: [user3, user4]
 }
 
-Decidim::EventsManager.publish(data)
+Decidim::EventsManager.publish(**data)
 ----
 
 Both, `EmailNotificationGenerator` and `NotificationGenerator` are use the same arguments:

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

@@ -8,7 +8,7 @@ Remember to follow the Gitflow branching workflow.
 
 . Go to develop with `git checkout develop`
 . Create the release branch `git checkout -b release/x.y-stable && git push origin release/x.y-stable`.
-. If required, add the release branch to Crowdin so that any pending translations will generate a PR to this branch.
+. If required, add the release branch to Crowdin so that any pending translations will generate a PR to this branch. This needs to be done with the generic user `decidim` in the GitHub's Crowdin integration, as this is the user that initially configured the installation and other admins in the Crowdin organization can't change it.
 
 Mark `develop` as the reference to the next release:
 
@@ -92,8 +92,9 @@ If this is a *Release Candidate version* release, the steps to follow are:
 . Run `bin/rake update_versions`, this will update all references to the new version.
 . Run `bin/rake bundle`, this will update all the `Gemfile.lock` files
 . Run `bin/rake webpack`, this will update the JavaScript bundle.
+. Run `bin/rspec`, this will check things like if all the officially supported languages translations are OK.
 . Commit all the changes: `git add . && git commit -m "Bump to rcXX version" && git push origin release/x.y-stable`.
-. Tag the release candidate with `git tag vX.Y.Z.rcN && git push origin vX.Y.Z.rcN`.
+. Run `git pull && bin/rake release_all`, this will create all the tags, push the commits and tags and release the gems to RubyGems.
 
 Usually, at this point, the release branch is deployed to Metadecidim during, at least, one week to validate the stability of the version.
 

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

@@ -0,0 +1,138 @@
+= Reminders
+
+Reminders can be used to remind users about anything they need to know about regarding a specific component. It is assumed the reminders are always related to a component. Currently they are only implemented in the budgets component to remind users if they did not finish their vote but added something to their vote earlier.
+
+The automatic reminder generation should run once every day and the reminder generator will contain the logic that decides who to remind about what. The generator class will queue the reminders that need to be sent.
+
+* To run automatic reminder generator.
++
+[source,ruby]
+----
+bundle exec rake decidim:reminders:all
+----
+
+== Key concepts
+
+Reminders can be created either automatically or through an admin triggered action from the admin panel. For instance, we can send budgeting reminders automatically after two hours, one week and two weeks after voting has been started. If the admin wanted to remind all users at the start of final day of the voting, which would be two days after the last automatic reminder or 2.5 weeks after the voting start, they would have to trigger it manually or change the configuration of the budgeting reminder.
+
+The reminders are controlled by a generator class which generates the reminders to be sent. The generator controls how and when the reminders are generated as it can be very context specific when to send the reminders. For instance, in the budgeting component, we need to find all unfinished orders that have been started more than two hours ago and which have not been already reminded enough many times.
+
+Reminders are defined through their own manifests which defines the following parameters for the reminders:
+
+- The generator class which is used to run the logic for creating the reminders
+- The form class which is used for defining specific parameters for the view where admin users can manually trigger the reminders to be sent
+- The command class which will queue the reminders when admin triggers the reminders manually
+
+=== The reminder objects
+
+Reminders consist of the following database objects:
+
+- Reminder which holds the main reminder object that is attached to a user to be reminded about and the component for which the reminder is created for. The reminder can have many deliveries and many records to be reminded about.
+- ReminderDelivery which holds a log of all deliveries sent to the user. This may be useful in cases where we need to audit the system or solve a user support request asking why they were reminded for a specific thing at a specific time. In the backend, this also lets us do conditional logic based on how many times the user has been reminded and when the last reminder was sent.
+- ReminderRecord which holds information about the records the reminder is related to. This lets us combine reminders that are related to multiple records at a time, so that we don't need to send mulitple emails for each record. For example, the budgeting reminders will contain information about in which budgets the user has pending votes which allows us to combine this information in a single email, instead of sending one email per pending order in each budget.
+
+==== ReminderRecord states
+
+The ReminderRecord object holds a "state" attribute which tells whether the record is in one of the following states:
+
+- `active` - The reminder record is active for the reminder to be sent. Only active records should be included in the reminder.
+- `pending` - The reminder record is "pending" which means that the reminder should probably be sent soon but not for sure. For example, in the budgeting reminders the reminder record is "pending" if voting has been started but it has been started just a moment before automatically sending the reminders. In this situation, we would not want to remind the user if they started the voting process two minutes before the automatic reminder sending was run on the server.
+- `deleted` - The record has been "deleted", so it will not need any further reminders. We still keep the ReminderRecord in order to preserve the backlog about when the previous reminders were sent. For example, in the budgeting reminders, the ReminderRecord is related to a budgeting "order" (or vote) which can be deleted by the user, and therefore won't need any further reminders.
+- `completed` - The record has been "completed", so it will not need any further reminders. The reminders can be specific to the state of the remindable objects, so we change the ReminderRecord state to "completed" when the record will not need any further reminders. For example, in the budgeting reminders, we would not want to remind the user anymore if they completed their vote in a budget but they still have pending order in another budget that will still need further reminders. In this situation, we would want to include only the pending order in the further reminders, still keeping the backlog information about the previous reminders for the already completed budget order (vote).
+
+== Defining a reminder
+
+Reminders can be defined through initializers by defining calling the `registed` method on the reminders registry object at the Decidim main module as follows:
+
+[source,ruby]
+----
+Decidim.reminders_registry.register(:orders) do |reminder_registry|
+  reminder_registry.generator_class_name = "Decidim::YourModule::YourReminderGenerator"
+  reminder_registry.form_class_name = "Decidim::YourModule::Admin::YourReminderForm"
+  reminder_registry.command_class_name = "Decidim::YourModule::Admin::CreateYourReminders"
+
+  # The reminder settings object lets you define configurations that can be changed by the system administrators.
+  # For example, if you want to make the intervals configurable when the reminders will be sent, you can provide a
+  # configuration for that.
+  reminder_registry.settings do |settings|
+    # For example, if your reminder should be automatically sent three times at specific intervals
+    settings.attribute :reminder_times, type: :array, default: [2.hours, 1.week, 2.weeks]
+  end
+
+  # The messages that will be shown for the reminder user interface if the admin wants to manually trigger the
+  # reminders. The title is shown at the top of the page and the description will be shown under it where you can
+  # provide information e.g. on how many reminders would be sent if the admin triggered the action.
+  reminder_registry.messages do |msg|
+    msg.set(:title) { |count: 0| I18n.t("decidim.budgets.admin.reminders.orders.title", count: count) }
+    msg.set(:description) { I18n.t("decidim.budgets.admin.reminders.orders.description") }
+  end
+end
+----
+
+=== Defining a reminder generator
+
+The generator object holds the main logic for creating the reminders. You can see one example at `Decidim::Budgets::OrderReminderGenerator` which generates the reminders for the pending orders. Another example could be for the upcoming meetings that will be happening in the next two days which could be implemented by defining the following reminder generator:
+
+[source,ruby]
+----
+# frozen_string_literal: true
+
+module Decidim
+  module Meetings
+    # This class is the generator class which creates and updates meeting related reminders,
+    # after reminder is generated it is send to user who are participating to upcoming meetings.
+    class MeetingReminderGenerator
+      attr_reader :reminder_jobs_queued
+
+      def initialize
+        @reminder_manifest = Decidim.reminders_registry.for(:meetings)
+        @reminder_jobs_queued = 0
+        @queued_reminders = []
+      end
+
+      # Creates reminders and updates them if they already exists.
+      def generate
+        Decidim::Component.where(manifest_name: "meetings").each do |component|
+          send_reminders(component)
+        end
+      end
+
+      # This can be called by the admin command that manually triggers the reminders.
+      def generate_for(component)
+        send_reminders(component)
+      end
+
+      private
+
+      attr_reader :reminder_manifest, :queued_reminders
+
+      def send_reminders(component)
+        # before_days could be provided as a configuration option, e.g. `2.days`
+        before_days = reminder_manifest.settings.attributes[:before_days]
+        Decidim::Meetings::Meeting.where(component: component).where(
+          "start_time >= ? AND start_time <= ?",
+          DateTime.now + before_days.days
+          DateTime.now + before_days.days + 1.day
+        ).each do |meeting|
+          Decidim::Meetings::Registration.where(meeting: meeting).each do |registration|
+            reminder = Decidim::Reminder.find_or_create_by(user: registration.user, component: component)
+            record = Decidim::ReminderRecord.find_or_create_by(reminder: reminder, remindable: meeting)
+            record.update(state: "active") unless record.active?
+            reminder.records << record
+            reminder.save!
+            next if queued_reminders.include?(reminder.id)
+
+            Decidim::Meetings::SendMeetingRemindersJob.perform_later(reminder)
+            @reminder_jobs_queued += 1
+            queued_reminders << reminder.id
+          end
+        end
+      end
+    end
+  end
+end
+----
+
+The `Decidim::Meetings::SendMeetingRemindersJob` would be responsible for delivering the emails for the upcoming meetings in the specified component.
+
+In addition, you need to create the Command and the Form objects to handle the manually triggered reminders from the admin panel in case you decide to implement these for the specified component. Please take example from `Decidim::Budgets::Admin::CreateOrderReminders` and `Decidim::Budgets::Admin::OrderReminderForm` to implement these. Also note that providing the admin triggered manual notifications is not necessary when you can omit creating these classes and the related view changes.

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

@@ -1,6 +1,8 @@
 = How to test Decidim engines
 
-== Requirements
+== RSpec
+
+=== Requirements
 
 You need to create a dummy application to run your tests. Run the following command in the decidim root's folder:
 
@@ -9,7 +11,7 @@ You need to create a dummy application to run your tests. Run the following comm
 bundle exec rake test_app
 ----
 
-== Running a specific test file or just a single spec
+=== Running a specific test file or just a single spec
 
 If you are writing new specs, you can run the tests contained in a single file by opening a console window in the corresponding module and calling ``rspec``on the file. For example:
 
@@ -26,7 +28,14 @@ You can also run a single test by appending its start line number to the command
 bundle exec rspec spec/forms/participatory_process_form_spec.rb:134
 ----
 
-== Running tests for a specific component
+We also have a helper at `bin/rspec` that you can use to run a single spec from the command line:
+
+[source,bash]
+----
+bin/rspec decidim-participatory_processes/spec/forms/participatory_process_form_spec.rb
+----
+
+=== Running tests for a specific component
 
 A Decidim engine can be tested running the rake task named after it. For
 example, to test the proposals engine, you can run:
@@ -36,7 +45,7 @@ example, to test the proposals engine, you can run:
 bundle exec rake test_proposals
 ----
 
-== Running the whole test suite
+=== Running the whole test suite
 
 You can also run the full thing including test application generation and tests
 for all components by running
@@ -48,6 +57,59 @@ bundle exec rake test_all
 
 But beware, it takes a long time... :)
 
+=== Running specs in parallel
+
+We've configured the https://github.com/grosser/parallel_tests[parallel_tests gem]. For
+using it, you'll need to follow these steps:
+
+. Configure the TEST_ENV_NUMBER environment variable with the number of processes that you want to run in parallel.
+. Run the commands to prepare the test database
+
+[source,bash]
+----
+cd spec/decidim_dummy_app/
+bundle exec rake parallel:create
+bundle exec rake parallel:prepare
+cd -
+----
+
+From now on you can use the `bundle exec rake parallel:spec` task, for instance for running all
+the system specs from any module:
+
+[source,bash]
+----
+cd decidim-participatory_processes
+bundle exec rake parallel:spec[spec/system/]
+----
+
+This same commmand without the parallelization (`cd decidim-participatory_processes && bundle exec rspec spec/system/`)
+took 26 minutes 21 seconds. With parallel_specs, this runs in 10 minutes 27 seconds.
+
+[NOTE]
+-----
+These numbers are depend on your machine, the configuration was:
+* TEST_ENV_NUMBER=4
+* Intel(R) Core(TM) i5-6500T CPU @ 2.50GHz
+-----
+
+== Jest
+
+We use Jest for testing our Javascript code.
+
+=== Running a specific test file
+
+[source,bash]
+----
+npx jest decidim-core/app/packs/src/decidim/external_link.test.js
+----
+
+=== Running the whole test suite
+
+[source,bash]
+----
+npm run test
+----
+
 == Continuous integration
 
 The tests are also run when a new commit is added to the `develop` or releases
@@ -58,3 +120,5 @@ This means that the workflows defined for each module in the folder
 `.github/workflows/` should be always updated with the module's dependencies
 list. The script `.github/workflows/dependencies.sh` can be helpful to keep
 those files updated until we have an automatic process to do it.
+
+You can read more about the continuous integration configuration at https://github.com/decidim/decidim/blob/develop/.github/workflows/README.md[GitHub].

data/docs/modules/install/pages/checklist.adoc

@@ -34,6 +34,6 @@ As a technopolitical project, Decidim needs several things to work. This is a no
 . Texts for at least, *terms of use, privacy policy and frequently asked questions*. To show the "Terms and conditions" body text in the "Sign Up Form", it is a requirement that the slug of this page to be equal `terms-and-conditions`.
 . Comply with your current *legal requirements*, like to registrate your privacy policy with the autorities (eg LOPD on Spain).
 . Fill the *Participatory Processes Configuration Form* to prepare your Participatory Process for Decidim.
-. Read the *https://decidim.org/docs/[Administration manual]*.
+. Read the *xref:admin:index.adoc[Administration manual]*.
 . Participate on *http://meta.decidim.org[MetaDecidim]*.
 . Read the Decidim *https://decidim.org/contract/[Social Contract]*.

data/docs/modules/install/pages/empty-database.adoc

@@ -0,0 +1,32 @@
+= Empty database installation
+
+You may want to setup your decidim with an empty database.
+In this case, please follow the steps bellow:
+
+. Follow steps 1 through 5 of previous section(xref:install:manual.adoc[Manual Installation] section).
+
+. Run the migrations from the root of your project in the terminal.
+[source,bash]
+----
+bin/rails db:create db:migrate
+----
+[start=3]
+. Now you need to create your admin user, in order to be able to login to the system. in the terminal type the following:
+[source,bash]
+----
+bundle exec rails s
+----
+[start=4]
+. Then you can create a system admin account to log in to the system panel with the following command:
+[source,bash]
+----
+bin/rails decidim_system:create_admin
+----
+
+Follow the CLI to create your admin user. For the sake of conformity with the rest of documentation, you may create a user with email `system@example.org` and password `decidim123456789`. Of course this is not recommended for a production environment as it isn't secure.
+
+Now, you will be able to login to the system panel with the provided credentials.
+
+== Extra notes
+
+The objective of decidim is to define an organizational and representation system capable of transforming into an autonomous entity or association from which the whole community participate. Therefore, creating the organizational account is centric part of the process (refer to xref:admin:system.adoc[System panel] for more information).

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

@@ -27,12 +27,12 @@ You can see the xref:install:manual.adoc[official manual installation tutorial],
 
 === B. Installation script [experimental]
 
-There's also a installation script made by http://www.platoniq.net/[Platoniq] that allows you to install Decidim automatically. You can even check it on a Vagrant virtual machine if you want to. https://platoniq.github.io/decidim-install/script/[More information].
+There's also an installation script made by http://www.platoniq.net/[Platoniq] that allows you to install Decidim automatically. You can even check it on a Vagrant virtual machine if you want to. https://platoniq.github.io/decidim-install/script/[More information].
 
 [source,console]
 ----
 wget -O install-decidim.sh https://raw.githubusercontent.com/Platoniq/decidim-install/master/script/install-decidim.sh
-chmod +x decidim-install.sh
+chmod +x install-decidim.sh
 ./install-decidim.sh decidim_application
 ----
 
@@ -53,19 +53,19 @@ This will also create some default data so you can start testing the app:
 
 |Decidim::System::Admin
 |system@example.org
-|decidim123456
+|decidim123456789
 |/system
 |Administrator for the multitenant
 
 |Decidim::User
 |admin@example.org
-|decidim123456
+|decidim123456789
 |/admin
 |Administrator for the organization
 
 |Decidim::User
 |user@example.org
-|decidim123456
+|decidim123456789
 |/user/sign_in
 |User for the organization
 
@@ -86,7 +86,7 @@ Visit http://localhost:3000 to see your app running.
 
 == Configuration & setup
 
-Decidim comes pre-configured with some safe defaults, but can be changed through the `config/initializers/decidim.rb` file in your app. Check the comments there or read the comments in https://github.com/decidim/decidim/blob/develop/decidim-core/lib/decidim/core.rb[the source file] (the part with the `config_accessor` calls) for more up-to-date info.
+Decidim comes pre-configured with some safe defaults, but can be changed through xref:configure:environment_variables.adoc[Environment Variables] or the xref:configure:initializer.adoc[Initializer] file in your app.
 
 === Scheduled tasks
 
@@ -96,8 +96,8 @@ You can configure it with `crontab -e`, for instance if you've created your Deci
 
 [source,console]
 ----
-# Remove expired data portability files
-0 0 * * * cd /home/user/decidim_application && RAILS_ENV=production bundle exec rake decidim:delete_data_portability_files
+# Remove expired download your data files
+0 0 * * * cd /home/user/decidim_application && RAILS_ENV=production bundle exec rake decidim:delete_download_your_data_files
 
 # Compute metrics
 1 0 * * * cd /home/user/decidim_application && RAILS_ENV=production bundle exec rake decidim:metrics:all
@@ -107,31 +107,40 @@ You can configure it with `crontab -e`, for instance if you've created your Deci
 
 # Delete old registrations forms
 3 0 * * * cd /home/user/decidim_application && RAILS_ENV=production bundle exec rake decidim_meetings:clean_registration_forms
+
+# Generate reminders
+4 0 * * * cd /home/user/decidim_application && RAILS_ENV=production bundle exec rake decidim:reminders:all
+
+# Send notification mail digest daily
+5 0 * * * cd /home/user/decidim_application && RAILS_ENV=production bundle exec rake decidim:mailers:notifications_digest_daily
+
+# Send notification mail digest weekly on saturdays
+5 0 * * 6 cd /home/user/decidim_application && RAILS_ENV=production bundle exec rake decidim:mailers:notifications_digest_weekly
 ----
 
 === Further configuration
 
-We also have other guides on how to configure some extra components:
+We also have other guides on how to configure some extra mandatory components:
 
 * xref:services:activejob.adoc[ActiveJob]: For background jobs (like sending emails).
-* xref:services:geocoding.adoc[Geocoding]: How to enable geocoding for proposals and meetings.
+* xref:services:maps.adoc[Maps]: How to enable geocoding for proposals and meetings.
+* xref:services:smtp.adoc[SMTP]: For sending emails for account registrations, password reminders, notifications, etc.
 * xref:services:social_providers.adoc[Social providers integration]: Enable sign up from social networks.
 
 == Deploy
 
-Once you've successfully deployed your app to your favorite platform, you'll need to create your `System` user. First you'll need to create your `Decidim::System` user in your production Ruby on Rails console:
+Once you've successfully deployed your app to your favorite platform, you'll need to create your `System` user. First you'll need to create your `Decidim::System` user in your terminal:
 
-[source,ruby]
+[source,console]
 ----
-email = <your email>
-password = <a secure password>
-user = Decidim::System::Admin.new(email: email, password: password, password_confirmation: password)
-user.save!
+bin/rails decidim_system:create_admin
 ----
 
+You'll be asked for an email and a password. For security, the password will not get displayed back at you and you'll need to confirm it.
+
 This will create a system user with the email and password you set. We recommend using a random password generator and saving it to a password manager, so you have a more secure login.
 
-Then, visit the `/system` dashboard and login with the email and passwords you just entered and create your organization. You're done! :tada:
+Then, visit the `/system` dashboard and login with the email and passwords you just entered and create your organization. You're done! 🎉
 
 You can check the https://github.com/decidim/decidim/tree/develop/decidim-system/README.md[`decidim-system` README file] for more info on how organizations work.
 

data/docs/modules/install/pages/manual.adoc

@@ -113,15 +113,19 @@ Be careful where you put the `.rbenv-vars` file, as if you put it in the same fo
 
 == 6. Initializing your app for local development
 
-We should now create your database:
-
+We should now create your database. For a first local installation, we recommend to start with some example contents (also known as seeds).
 [source,bash]
 ----
 bin/rails db:create db:migrate
 bin/rails db:seed
 ----
 
-This will also create some default data so you can start testing the app, with an administrator account with email admin@example.org and password `decidim123456`
+[NOTE]
+====
+Please refer to xref:install:empty-database.adoc[Empty database installation] section if you want to setup your instance on an empty database (without any seeds)
+====
+
+This will also create some default data so you can start testing the app, with an administrator account with email admin@example.org and password `decidim123456789`
 
 == 7. Start your web server
 
@@ -143,8 +147,8 @@ With these steps you would only have an initial installation for trying Decidim,
 
 Other user accounts that you'll have in the seeds are:
 
-* To participate as a regular user, with email `user@example.org` and password `decidim123456`.
-* To manage the Multitenant and being able to log in at `/system`, with email `system@example.org` and password `decidim123456`.
+* To participate as a regular user, with email `user@example.org` and password `decidim123456789`.
+* To manage the Multitenant and being able to log in at `/system`, with email `system@example.org` and password `decidim123456789`.
 
 The seed data won't be created in production environments, if you still want to do it (for instance, for a Demo or Staging server), run: