decidim 0.23.5 → 0.24.2

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

@@ -0,0 +1,22 @@
+= Authorizations
+
+Decidim offers several methods for allowing participants to get authorization to perform certain privileged actions. This module implements several of those methods and also offers a way for installation to implement their custom verification methods.
+
+There are several use cases for this, such as
+
+* Sending a SMS code to users to verify that their have a valid cellphone
+* Allowing users to upload a photo or scanned image of their identity document
+* Sending users a code through postal code
+* Allowing users to go to to a physical office and check their documentation
+* Checking some information through other systems (as a Municipal Census on the case of Municipalities, Cities or Towns)
+* Having a list of valid users emails
+
+Right now Decidim supports only a few of these cases, but we have an internal API where you can program your own kind of authorizations.
+Introduction
+
+Each decidim instance is in full control of its authorizations, and can customize:
+
+* The different methods to be used by users to get verified. For example, through a census, by uploading their identity documents, or by receiving a verification home at their address.
+* The different actions in decidim that require authorization, and which authorization method they require. For example, a decidim instance might choose to require census authorization to create proposals, but a fully verified address via a verification code sent by postal mail for voting on proposals.
+
+See https://github.com/decidim/decidim/blob/develop/decidim-verifications/README.md[decidim-verifications's README] and https://decidim.org/modules[Decidim's Modules page].

data/docs/{customization/code.md → modules/customize/pages/code.adoc}

@@ -1,4 +1,4 @@
-# Code
+= Code
 
 Decidim is multiple things:
 
@@ -7,24 +7,27 @@ Decidim is multiple things:
 
 Most of the time, you should work with the generated application. That application (development_app on this docs) should be named as your project, for instance for Barcelona City Council is `DecidimBarcelona`, so for creating it should be:
 
-```console
+[source,console]
+----
 decidim DecidimBarcelona
-```
+----
 
 If you want to override/change anything (for instance the homepage), you can just do it with the same name of the file, through Monkey Patching.
 
 If you want to extend Decidim, the prefered way should be by having a Module. This is a Ruby on Rails Engine which provides ruby code (models, views, controllers, assets, etc). You can use it through multiple ways:
 
-* Putting it on the same directory as your app and pointing on the Gemfile. [See example on GitHub](https://github.com/AjuntamentdeBarcelona/decidim-barcelona/tree/c210b5338d7ba1338c9879627e081da1441f1946). For instance:
+* Putting it on the same directory as your app and pointing on the Gemfile. https://github.com/AjuntamentdeBarcelona/decidim-barcelona/tree/c210b5338d7ba1338c9879627e081da1441f1946[See example on GitHub]. For instance:
 
-```ruby
+[source,ruby]
+----
 gem "decidim-debates", path: "decidim-debates"
-```
+----
 
-* Publishing on a git reposotory and pointing in on the Gemfile. For instance:
+* Publishing on a git repository and pointing in on the Gemfile. For instance:
 
-```ruby
+[source,ruby]
+----
 gem "decidim-consultations", git: "https://github.com/decidim/decidim-module-consultations"
-```
+----
 
 * Publishing it on rubygems.org

data/docs/{customization/gemfile.md → modules/customize/pages/gemfile.adoc}

@@ -1,10 +1,11 @@
-# Gemfile
+= Gemfile
 
-You can add and change your Gemfile as you want, this is a classic Ruby on Rails application. For example to add [rails-footnotes](https://github.com/josevalim/rails-footnotes) gem you would just add:
+You can add and change your Gemfile as you want, this is a classic Ruby on Rails application. For example to add https://github.com/josevalim/rails-footnotes[rails-footnotes] gem you would just add:
 
-```ruby
+[source,ruby]
+----
 gem 'rails-footnotes', '~> 4.0'
-```
+----
 
 And then just do the classic Ruby on Rails flow bundle install and following any gem specific install steps from its own documentation.
 

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

@@ -0,0 +1,7 @@
+= Images
+
+You can change most of the images (for instance the logo, main banner on homepage, contents of participatory processes, etc) through the Administration panel.
+
+If you want to override the standard images given by Decidim (for instance the initial image for user's avatars) you can do it by naming it the same way as the original image, in this case it should be `app/assets/images/decidim/default-avatar.svg`
+
+If you want to add a new image you can do it as any Rails application, leaving it on your image's asset folder and using image_tag helper. You can see more documentation on http://guides.rubyonrails.org/asset_pipeline.html[Rails guide].

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

@@ -0,0 +1,59 @@
+= Javascript
+
+You can add Javascript code by multiple ways in Decidim:
+
+== Asset pipeline
+
+Just add it to `app/assets/javascripts/application.js`. For example to create a new alert just add:
+
+[source,javascript]
+----
+$(function(){
+  alert('foobar');
+});
+----
+
+More information in https://guides.rubyonrails.org/asset_pipeline.html[Rails Asset Pipeline documentation].
+
+== 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`:
+
+[source,javascript]
+----
+<script type="text/javascript">
+$(function(){
+  alert('foobar');
+});
+</script>
+----
+
+== Custom HTML Header snippets
+
+If you need changes on a multitenant installation, you can do so by enabling a configuration
+in your `config/initializers/decidim.rb` file. Please do notice that this has security implications:
+
+[source,ruby]
+----
+  # Custom HTML Header snippets
+  #
+  # The most common use is to integrate third-party services that require some
+  # extra JavaScript or CSS. Also, you can use it to add extra meta tags to the
+  # HTML. Note that this will only be rendered in public pages, not in the admin
+  # section.
+  #
+  # Before enabling this you should ensure that any tracking that might be done
+  # is in accordance with the rules and regulations that apply to your
+  # environment and usage scenarios. This feature also comes with the risk
+  # that an organization's administrator injects malicious scripts to spy on or
+  # take over user accounts.
+  #
+  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`):
+
+image::header-snippet.png[Header snippet]
+
+Notice that you can resize this textarea.
+

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

@@ -0,0 +1,25 @@
+= Menu
+
+The menu also known as Navigation Bar, is the main way of navigation by Decidim.
+
+image::menu.png[Decidim Menu]
+
+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.
+
+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.
+
+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.
+
+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/oauth.adoc

@@ -0,0 +1,33 @@
+= OAuth
+
+Decidim is both and OAuth client (via https://github.com/omniauth/omniauth[omniauth]) and an OAuth provider (via https://github.com/doorkeeper-gem/doorkeeper[doorkeeper]).
+
+Check the xref:services:social_providers.adoc[Social Providers] document to check the provider and client configurations.
+
+== Performing more actions on omniauth registration
+
+Some times, there is the need to perform more actions than just creating a user on registration, this is why `CreateOmniauthRegistration` command publishes a `"decidim.user.omniauth_registration` event after registration so that developers can subscribe to it and perform other actions like user verification or alike.
+
+This event comes with the following payload:
+
+* user_id: The id for the registered User.
+* identity_id: The id for the social Identity.
+* provider: The name for the social provider.
+* uid: OAuth's uid
+* email: User's email.
+* name: User's name.
+* nickname: User's nickname after being normalized.
+* avatar_url: Avatar's url, if any.
+* raw_data: The raw hash received directly from the Omniauth gem.
+
+To be notified after a registration one should subscribe to the event, in the passed block the after registration code should be implemented:
+
+[source,ruby]
+----
+ActiveSupport::Notifications.subscribe "decidim.user.omniauth_registration" do |name, started, finished, unique_id, data|
+  puts "the data: #{data.inspect}"
+  IdCatMobilVerificationJob.perform_later(data[:raw_data])
+end
+----
+
+It is a good practice to delegate the required implementation to a Job to bring a fastest response to the user, also it will avoid that crashes in this code to propagate to the registration process.

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

@@ -0,0 +1,64 @@
+= 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:
+
+== Organization colors
+
+If you only want to change colors and anything more, the most easy and fast way is doing this in the Administrator panel, in Administration -> Configuration -> Appearance (URL `/admin/organization/appearance/edit`):
+
+image::organization-colors.png[Organization colors]
+
+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`:
+
+[source,stylesheet]
+----
+<style type="text/css">
+ p { color: red; }
+</style>
+----
+
+== Custom HTML Header snippets
+
+If you need changes on a multitenant installation, you can do so by enabling a configuration
+in your `config/initializers/decidim.rb` file. Please do notice that this has security implications:
+
+[source,ruby]
+----
+  # Custom HTML Header snippets
+  #
+  # The most common use is to integrate third-party services that require some
+  # extra JavaScript or CSS. Also, you can use it to add extra meta tags to the
+  # HTML. Note that this will only be rendered in public pages, not in the admin
+  # section.
+  #
+  # Before enabling this you should ensure that any tracking that might be done
+  # is in accordance with the rules and regulations that apply to your
+  # environment and usage scenarios. This feature also comes with the risk
+  # that an organization's administrator injects malicious scripts to spy on or
+  # take over user accounts.
+  #
+  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`):
+
+image::header-snippet.png[Header snippet]
+
+Notice that you can resize this textarea.
+
+== Asset pipeline
+
+You can go to app/assets/stylesheets/application.css.sass on your generated applications. There you can override any class using CSS with SASS.
+
+In https://github.com/decidim/decidim/blob/develop/decidim-core/app/assets/stylesheets/decidim/_variables.scss[decidim-core/app/assets/stylesheets/decidim/_variables.scss] you can find the `variables` that can be overriden in your `sass`.
+
+We use http://sass-lang.com/guide[SASS, with SCSS syntax] as CSS preprocessor.
+
+== Accesibility
+
+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)
+

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

@@ -0,0 +1,30 @@
+= Custom Texts
+
+== Using custom locales
+
+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:
+
+[source,yml]
+----
+en:
+  pages:
+    home:
+      footer_sub_hero:
+        footer_sub_hero_body: Let's build a more open, transparent and collaborative society.<br /> Join, participate and decide.
+----
+
+You need to create a file for this translation as http://guides.rubyonrails.org/i18n.html[Ruby on Rails i18n documentation] says, for instance config/locales/home.en.yml, you can see a currently working example in https://github.com/AjuntamentdeBarcelona/decidim-barcelona/pull/206[this PR].
+
+== Using external module
+
+There is an external module https://github.com/mainio/decidim-module-term_customizer[decidim-term_customizer], according with the project README:
+
+____
+The module allows administrators to add "translation sets" through the admin panel which contain customized terms for any module in the system. These sets can be applied against different scopes within the system, e.g. the whole system, participatory space scope (e.g. all participatory processes or a specific participatory process) or a specific component within a participatory space.
+____
+
+To implement this on your decidim installation follow the https://github.com/mainio/decidim-module-term_customizer/blob/master/README.md[documentation in the external module].
+
+You can see an example in https://github.com/decidim/metadecidim/pull/38[this PR].

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

@@ -0,0 +1,17 @@
+= Users registration mode
+
+Decidim allows organizations to choose one of the three modes related to the registration and login of users. This can be configured by the system user, in the organization manager zone.
+
+== Allow users to register and login
+
+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
+
+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.
+
+NOTE: if you have configured xref:services:social_providers.adoc[social providers], users will still be able to sign in with external accounts even when this mode is configured.
+
+== Access only can be done with external accounts
+
+This mode disables the registration form and the login form. With this mode, users only can access through xref:services:social_providers.adoc[social providers], so it is recommended to configure at least one of them. This can be useful when an organization needs to allow participation only to users of another application of the organization itself.

data/docs/{customization/views.md → modules/customize/pages/views.adoc}

@@ -1,34 +1,34 @@
-# Views (HTML)
+= 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.
 
-## Overrides
+== 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:
 
-- 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.
+* 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.
 
-### Filename method
+=== Filename method
 
 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 [`decidim-core/app/views/layouts/decidim/_mini_footer.html.erb`](https://github.com/decidim/decidim/blob/e181d7e67bdf915a3a8e58416c683f52346de047/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'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`).
 
-## Deface method
+== Deface method
 
-You'll need the [`deface` gem](https://github.com/spree/deface) installed on your application, and follow their instructions on how to use the different overridign methods that they support.
+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.
 
 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:
 
-```html
+[source,html]
+----
 <!-- insert_before ".main-footer" -->
 hello world
-```
+----
 
-## New pages
+== 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 [StaticController](
-https://github.com/AjuntamentdeBarcelona/decidim-barcelona/blob/d47d4a9ae6be26a0c5c4000907dda3c195579636/app/controllers/static_controller.rb) (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'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.

data/docs/{advanced/api.md → modules/develop/pages/api.adoc}

@@ -1,4 +1,4 @@
-# API
+= API
 
 Decidim comes with a powerful API in read-only mode based in the GraphQL specification.
 
@@ -10,6 +10,6 @@ Accessing that URL will give a full details of all the objects that can be reque
 
 For a quick introduction about how to use the Decidim API, please refer to this document:
 
-[Using the Decidim GraphQL API](../../decidim-api/docs/usage.md)
+xref:../../decidim-api/docs/usage.adoc[Using the Decidim GraphQL API]
 
 Note that this document is available under the `api/docs` URL nicely formatted as well. It also includes the full field types reference.

data/docs/{advanced/authorship.md → modules/develop/pages/authorable.adoc}

@@ -1,14 +1,14 @@
-# Authorship
+= Authorship
 
 Regarging authorship of Decidim resources/entities, there are three concerns
 involved directly:
 
-- `Decidim::ActsAsAuthor`: which defines how an author should behave.
-- `Decidim::Authorable` and `Decidim::Coauthorable`: which define the behaviour around who authored a resource.
+* `Decidim::ActsAsAuthor`: which defines how an author should behave.
+* `Decidim::Authorable` and `Decidim::Coauthorable`: which define the behaviour around who authored a resource.
 
 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
 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.
+of an author. Anyway one of the ``OfficialAuthorPresenter``s may be used as a
+reference.

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

@@ -0,0 +1,91 @@
+[plantuml]
+....
+@startuml
+!includeurl https://raw.githubusercontent.com/plantuml-stdlib/C4-PlantUML/v2.0.1/C4_Component.puml
+
+' uncomment the following line to make proposals
+'LAYOUT_AS_SKETCH()
+
+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.")
+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.")
+
+Container_Boundary(web_app, "Web Application") {
+
+    Component(admin, "Admin module", "Ruby On Rails Engine", "Internal. Admin panel, mounted in /admin")
+    Component(api, "API module", "Ruby On Rails Engine", "Internal. GraphQL API, mounted in /api")
+    Component(core, "Core module", "Ruby On Rails Engine", "Internal. Provides APIs as building blocks to be consumed by the rest of the modules.")
+    Component(comments, "Comments module", "Ruby On Rails Engine", "Provides the Commentable capability to other modules.")
+    Component(dev, "Dev module", "Ruby On Rails Engine", "Aids the local development of Decidim's components.")
+    Component(forms, "Forms module", "Ruby On Rails Engine", "Provides APIs for working with forms to other modules (like Surveys and Meetings)")
+    Component(generators, "Generator module", "Ruby On Rails Engine", "Provides the decidim Command Line Interface.")
+    Component(system, "System module", "Ruby On Rails Engine", "Multitenant configuration, mounted in /system. Can create and manage all the instances of an installation.")
+    Component(verifications, "Verifications module", "Ruby On Rails Engine", " Offers several methods for allowing participants to get authorization to perform certain privileged actions.")
+
+    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.")
+
+    Component(accountability, "Accountability module", "Ruby On Rails Engine", "Component. Adds an accountability section to any participatory space so users can follow along the state of the accepted proposals.")
+    Component(budgets, "Budgets module", "Ruby On Rails Engine", "Component. Adds a participatory budgets system to any participatory space.")
+    Component(blogs, "Blogs module", "Ruby On Rails Engine", "Component. Makes possible to add posts ordered by publication time to spaces.")
+    Component(debates, "Debates module", "Ruby On Rails Engine", "Component. Adds a CRUD engine to the admin and public view scoped inside the participatory process.")
+    Component(elections, "Elections module", "Ruby On Rails Engine", "Components. Adds voting with cryptographic capabilities.")
+    Component(meetings, "Meetings module", "Ruby On Rails Engine", "Component. Adds a CRUD engine to the admin and public view scoped inside the participatory process.")
+    Component(pages, "Pages module", "Ruby On Rails Engine", "Component. adds static page capabilities to any participatory space. It basically provides an interface to include arbitrary HTML content to any step.")
+    Component(proposals, "Proposals module", "Ruby On Rails Engine", "Component. Adds one of the main components of Decidim: allows users to contribute to a participatory space by creating proposals.")
+    Component(surveys, "Surveys module", "Ruby On Rails Engine", "Component. Makes possible to publish surveys (for registered participants or visitors users).")
+    Component(sortitions, "Sortitions module", "Ruby On Rails Engine", "Component. makes possible to select randomly a number of proposals among a set of proposals (or a category of proposals within a set) maximizing guarantees of randomness and avoiding manipulation of results by the administrator.")
+
+    Rel(surveys, forms, "Consumes")
+    Rel(meetings, forms, "Consumes")
+    Rel_Back(forms, elections, "Consumes")
+
+    ' Rel(proposals, assemblies, "Mounts in")
+    ' 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")
+    ' Rel(sortitions, comments, "Consumes")
+    ' Rel(dev, comments, "Consumes")
+    ' Rel(meetings, comments, "Consumes")
+    ' Rel(debates, comments, "Consumes")
+    ' 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")
+    ' Rel(sortitions, admin, "Managed in")
+    ' Rel(meetings, admin, "Managed in")
+    ' Rel(debates, admin, "Managed in")
+    ' Rel(proposals, admin, "Managed in")
+    ' Rel(blogs, admin, "Managed in")
+    ' Rel(elections, admin, "Managed in")
+
+}
+
+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..")
+System_Ext(oauth_system, "OAUTH2 System", "Optional. Third party sign on systems. Could be Twitter, Facebook, Google or any other OAUTH2 providers.")
+
+Rel_Back_Neighbor(decidim_bulletin_board_system, elections, "Uses")
+Rel_Neighbor(worker, mail_system, "Sends e-mails", "SMTP")
+Rel(web_app, rel_db, "Uses")
+Rel(web_app, filesystem, "Uses")
+Rel(web_app, oauth_system, "Uses")
+Rel(web_app, geocoding_system, "Uses")
+Rel(web_app, etherpad_system, "Embeds", "Through an Iframe")
+@enduml
+....