decidim-decidim_awesome 0.10.3 → 0.11.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2cf1da76fd4803091a1a436c61708acfffe4ce1766227e0dcdef5a03d43adb00
-  data.tar.gz: f6dbf35fc450c203eea9db332372c26432fb171d9a057fbdc44bd1725d319963
+  metadata.gz: 107f5d454725a66c2a3a7658d9c841616a4556f634a6615c5f124ad2815c94b2
+  data.tar.gz: cc18503da6d79d49787f40a6a6da9fe659d64c05183c599a30800a25a874c5b9
 SHA512:
-  metadata.gz: '01794da0b71c3719eab36c0c7a7107bd4873fa08bc78d78d61723cc6b238ad68eaed5bd281729c652e50c1afa0acdc0af2a47cbd1f2a0dea4fa7d40856dd5f5e'
-  data.tar.gz: 519112bb3fd8422b23c2fb36330e80ee18a2b5d3dc08f2c27bddf5c4e2be53e619cfc056a101fe8c37e7a903a160c4e57c0d9023c8919457d9cceaa94cfa1559
+  metadata.gz: 7da76c3a55fac5f16814946e9de813e7e30f2f56523a62143b20ad52bf16863abfd5da3a79ac44c7a0aedffc4e9ddec232bed2732153474ac586cecac0acb302
+  data.tar.gz: d5c566fe5297b253b6004ad23007fc22d7a47c5aa9a0a310de319799c2fdfced27cf1b0c0861e8c9341d041eeb556571c0d65b8ae16d56fcb6b16eafe30a7d54

data/CHANGELOG.md

@@ -1,11 +1,11 @@
 CHANGELOG
 =========
 
-v0.10.3
+v0.11.1
 ------
 
 Compatibility:
-  - Decidim v0.27.4
+  - Decidim v0.28.x
 
 Features:
   - Added Private Custom Fields feature
@@ -13,8 +13,17 @@ Features:
   - Added GraphQL types for custom fields in the API
   - Adds parsed information about custom fields in the Proposals export
   - Adds parsed information bout private custom fields when admins exports private data
-  - Adds a maintenance menu with tools to remove old private 
-  - SQL vulnerability fix for admin accountability
+  - Adds a maintenance menu with tools to remove old private data
+
+v0.11
+------
+
+Compatibility:
+  - Decidim v0.28.x
+
+Features:
+  - Redesign to version 0.28
+  - Removed markdown editor
 
 v0.10.2
 ------
@@ -71,7 +80,7 @@ Compatibility:
 
 Features:
   - Fixes for the menu hacker
-
+ 
 v0.9.1
 ------
 

data/README.md

@@ -1,16 +1,14 @@
 # Decidim::DecidimAwesome
 
-[![[CI] Tests 0.27](https://github.com/decidim-ice/decidim-module-decidim_awesome/actions/workflows/tests.yml/badge.svg)](https://github.com/decidim-ice/decidim-module-decidim_awesome/actions/workflows/tests.yml)
-[![[CI] Tests 0.26](https://github.com/decidim-ice/decidim-module-decidim_awesome/actions/workflows/tests-legacy.yml/badge.svg)](https://github.com/decidim-ice/decidim-module-decidim_awesome/actions/workflows/tests-legacy.yml)
+[![[CI] Tests 0.28](https://github.com/decidim-ice/decidim-module-decidim_awesome/actions/workflows/tests.yml/badge.svg)](https://github.com/decidim-ice/decidim-module-decidim_awesome/actions/workflows/tests.yml)
 [![[CI] Lint](https://github.com/decidim-ice/decidim-module-decidim_awesome/actions/workflows/lint.yml/badge.svg)](https://github.com/decidim-ice/decidim-module-decidim_awesome/actions/workflows/lint.yml)
-[![[CI] Precompile](https://github.com/decidim-ice/decidim-module-decidim_awesome/actions/workflows/precompile.yml/badge.svg)](https://github.com/decidim-ice/decidim-module-decidim_awesome/actions/workflows/precompile.yml)
 [![Maintainability](https://api.codeclimate.com/v1/badges/2dada53525dd5a944089/maintainability)](https://codeclimate.com/github/decidim-ice/decidim-module-decidim_awesome/maintainability)
 [![Test Coverage](https://codecov.io/gh/decidim-ice/decidim-module-decidim_awesome/branch/main/graph/badge.svg?token=TFBMCLLZJG)](https://codecov.io/gh/decidim-ice/decidim-module-decidim_awesome)
 
-Usability and UX tweaks for Decidim.
+**Usability and UX tweaks for Decidim.**
 
 This plugin allows the administrators to expand the possibilities of Decidim beyond some existing limitations.
-All tweaks are provided in a optional fashion with granular permissions that let the administrator to choose exactly where to apply those mods. Some tweaks can be applied to any assembly, other in an specific participatory process or even in type of component only.
+All tweaks are provided in a optional fashion with granular permissions that let the administrator to choose exactly where to apply those mods. Some tweaks can be applied to an assembly, other in an specific participatory process or even in a type of component only (for instance, only in proposals).
 
 **DISCLAIMER: This module is heavily tested and widely used, however we do not accept any responsibility for breaking anything. Feedback is appreciated though.**
 
@@ -31,13 +29,13 @@ Each hack can be scoped to one or more specific participatory spaces or componen
 
 ### Tweaks:
 
-#### 1. Image support for the Quill editor
+#### 1. Image support for the RichText editor
 
 Modifies the WYSIWYG editor in Decidim by adding the possibility to insert images. When uploading images, Drag & Drop is supported. Images will be uploaded to the server and inserted as external resources (it doesn't use base64 in-line encoding).
 
 This feature allows you use images in newsletters as well.
 
-![Images in Quill Editor](examples/quill-images.png)
+![Images in RichText Editor](examples/quill-images.png)
 
 #### 2. Auto-save for surveys and forms
 
@@ -47,27 +45,23 @@ It works purely in the client side by using LocalStorage capabilities of the bro
 
 Saving the form removes the stored data.
 
-![Auto save in forms](examples/auto-save.png)
+![Auto save in forms](examples/auto-save.gif)
 
 #### 3. Images in proposals
 
-Event if you haven't activated the WYSIWYG editor (Quill) in public views (eg: proposals use a simple textarea if rich text editor has not been activated for users). You can allow users to upload images in them by drag & drop over the text area.
+Event if you haven't activated the WYSIWYG editor (RichText) in public views (eg: proposals use a simple textarea if rich text editor has not been activated for users). You can allow users to upload images in them by drag & drop over the text area.
 
 ![Proposal images](examples/proposal-images.png)
 
-#### 4. Markdown editor for proposals
-
-Allows to use markdown when creating proposals instead of a bare textarea.
-
-#### 5. Admin scope configuration
+#### 4. Restrict scope for tweaks
 
 All tweaks can be configured and scoped to a specific participatory space, a type of participatory space, a type of component or a specific component.
 
-Many scopes can be defined for every tweak.
+Many scopes can be defined for every tweak. If a tweak is not scoped, it will be applied globally.
 
-![Admin tweaks for editors](examples/admin-editors.png)
+![Tweak scopes](examples/tweak-scopes.png)
 
-#### 6. Awesome map component
+#### 5. Awesome map component
 
 This is a component you can add in any participatory space. It retrieves all the geolocated content in that participatory space (meetings or proposals) and displays it in a big map.
 
@@ -75,25 +69,25 @@ It also provides a simple search by category, each category is assigned to a dif
 
 ![Awesome map](examples/awesome-map.png)
 
-#### 7. Fullscreen Iframe component
+#### 6. Fullscreen Iframe component
 
 Another simple component that can be used to embed and Iframe with any external content in it that fills all the viewport.
 
 ![Fullscreen iframe](examples/fullscreen-iframe.png)
 
-#### 8. Live support chat
+#### 7. Live support chat
 
-With this feature you can have a support chat in Decidim. It is linked to a [Telegram](https://telegram.org/) group or a single user chat using the [[IntergramBot](https://web.telegram.org/#/im?p=@IntergramBot). Just invite the bot to a group or chat with it directly, grab your ID, put it on the Awesome settings and have fun!. For more info or for hosting your own version of the bot check the [Intergram project](https://github.com/idoco/intergram).
+With this feature you can have a support chat in Decidim. It is linked to a [Telegram](https://telegram.org/) group or a single user chat using the [IntergramBot](https://web.telegram.org/#/im?p=@IntergramBot). Just invite the bot to a group or chat with it directly, grab your ID, put it on the Awesome settings and have fun!. For more info or for hosting your own version of the bot check the [Intergram project](https://github.com/idoco/intergram).
 
 ![Intergram screenshot](examples/intergram.png)
 
-#### 9. Custom CSS applied only according scoped restrictions
+#### 8. Custom CSS applied only according scoped restrictions
 
 With this feature you can create directly in the admin a CSS snipped that is only applied globally, in a particular assembly or even a single proposal!
 
 ![CSS screenshot](examples/custom_styles.png)
 
-#### 10. Change the main menu of Decidim entirely!
+#### 9. Change the main menu of Decidim entirely!
 
 Feel free to hide, modify or add items in the Decidim's main menu. You can also change the order, establish some conditions (like showing only for logged users) or open in a new window.
 
@@ -102,7 +96,7 @@ Feel free to hide, modify or add items in the Decidim's main menu. You can also
 ![Menu hacks screenshot](examples/menu-3.png)
 ![Menu hacks screenshot](examples/menu-4.png)
 
-#### 11. Assign admins to specific scopes and prevent them modify anything else
+#### 10. Assign admins to specific scopes and prevent them modify anything else
 
 Convert any user on the platform (that is not currently an admin) to a limited subset of participatory spaces or event components. Just add users to a box and scope them to some constraints. These users will see the "Edit" button in everywhere they have permissions. Any access to non allowed zones will redirect the user to the admin index page.
 
@@ -110,7 +104,7 @@ Convert any user on the platform (that is not currently an admin) to a limited s
 ![Scoped admins unauthorized](examples/scoped_admins_unauthorized.png)
 ![Scoped admins configuration](examples/scoped_admins_config.png)
 
-#### 12. Custom fields for proposals
+#### 11. Custom fields for proposals
 
 Now admins can substitute the body of a proposal with a set of form fields.
 Edition is make with a Drag & Drop interface in the admin and can (and should) be scoped to apply only to certain proposal components.
@@ -137,7 +131,9 @@ Decidim::DecidimAwesome.configure do |config|
 end
 ```
 
-##### 12.1. GraphQL types for custom fields
+##### 11.1. GraphQL types for custom fields
+
+#### 11.1. GraphQL types for custom fields
 
 Custom fields are displayed in the GaphQL API according to their definition in a formatted array of objects in the attribute `bodyFields`.
 
@@ -179,14 +175,14 @@ A query to extract this information could look like this (see that the original
 You can then use this custom type in your GraphQL queries and mutations to handle the custom fields in proposals.
 
 
-##### 12.2. Private Custom fields
+##### 11.2. Private Custom fields
 
 Similar to the custom fields feature, but only admins can see the content of the fields. This is useful for adding metadata to proposals that should not be visible to the public (such as contact data).
 Data is stored encrypted in the database.
 
 ![Private Custom fields screenshot](examples/private_custom_fields.png)
 
-#### 13. Custom Redirections (or URL shortener feature)
+#### 12. Custom Redirections (or URL shortener feature)
 
 Admins can create custom paths that redirect to other places. Destinations can be internal absolute paths or external sites.
 There's also possible to choose to sanitize (ie: remove) any query string or to maintain it (so you can decide to use).
@@ -206,7 +202,7 @@ Using a link with a query string (ie: `/take-me-somewhere?locale=es`) that will
 
 ![Custom redirections screenshot](examples/custom-redirections.png)
 
-#### 14. Custom validation rules for title and body in proposals
+#### 13. Custom validation rules for title and body in proposals
 
 Configure as you wish how the fields "title" and "body" are validated in proposals creation.
 
@@ -219,7 +215,7 @@ Rules available:
 
 ![Custom validations](examples/custom_validations.png)
 
-#### 15. Admin accountability
+#### 14. Admin accountability
 
 This feature allows you to list all the users that are, or have been at any point in time, admins, valuators, user managers or any other role in Decidim. Including global admin roles or private admins of a particular participatory space.
 
@@ -227,7 +223,7 @@ Results can be filtered by role and by time range and also exported as CSV or ot
 
 ![Admin accountability](examples/admin_accountability.png)
 
-#### 16. Additional proposal sortings
+#### 15. Additional proposal sortings
 
 ![Proposal sorting](examples/proposal_sorting.png)
 ![Proposal sorting admin](examples/proposal_sorting-admin.png)
@@ -256,7 +252,7 @@ Decidim::DecidimAwesome.configure do |config|
 end
 ```
 
-#### 17. Weighted voting
+#### 16. Weighted voting
 
 This feature allows you to configure a proposals component to use a weighted voting system. This means that each vote can have a different weight and the result of the vote is calculated as the sum of all the weights.
 
@@ -279,7 +275,7 @@ if Decidim::DecidimAwesome.enabled?(:weighted_proposal_voting)
     voting.show_vote_button_view = "decidim/decidim_awesome/voting/no_admins_vote/show_vote_button"
     voting.show_votes_count_view = "decidim/decidim_awesome/voting/no_admins_vote/show_votes_count"
     # voting.show_votes_count_view = "" # hide votes count if needed
-    voting.proposal_m_cell_footer = "decidim/decidim_awesome/voting/no_admins_vote/proposal_m_cell_footer"
+    voting.proposal_metadata_cell = "decidim/decidim_awesome/voting/proposal_metadata"
     # define a weight validator (optional, by default all weights are valid)
     voting.weight_validator do |weight, context|
       # don't allow admins to vote
@@ -305,11 +301,11 @@ A manifest must define a vote button view for the main proposal view, a vote cou
 
 All views are optional, if set to `nil` they will use the original ones. If set to an empty string `""` they will be hidden.
 
-The `weight_validator` is a Proc that receives the weight value and the context with the current user and the proposal and returns true or false if the weight is valid or not.
+The `weight_validator` is a `Proc` that receives the weight value and the context with the current user and the proposal and returns true or false if the weight is valid or not.
 
 **Notes for view `show_vote_button_view`**
 
-When building a new view for the vote button ([see the original](https://github.com/decidim/decidim/blob/release/0.27-stable/decidim-proposals/app/views/decidim/proposals/proposals/_vote_button.html.erb)) is important to take into account the following situations:
+When building a new view for the vote button ([see the original](https://github.com/decidim/decidim/blob/release/0.28-stable/decidim-proposals/app/views/decidim/proposals/proposals/_vote_button.html.erb)) is important to take into account the following situations:
 
 - If there's a `current_user` logged in
 - If votes are blocked `if current_settings.votes_blocked?`
@@ -317,7 +313,7 @@ When building a new view for the vote button ([see the original](https://github.
 - If maximum votes have already reached `if proposal.maximum_votes_reached?`
 - If the proposal can accumulate supports beyond maximum `if proposal.can_accumulate_supports_beyond_threshold`
 - If the current component allows the user to participate `if current_component.participatory_space.can_participate?(current_user)`
-- Note that the [original view](https://github.com/decidim/decidim/blob/release/0.27-stable/decidim-proposals/app/views/decidim/proposals/proposals/_vote_button.html.erb) is overridden only inside the tag  `<div id="proposal-<%= proposal.id %>-vote-button" class="button--vote-button">`. You only need to substitute the part inside.
+- Note that the [original view](https://github.com/decidim/decidim/blob/release/0.28-stable/decidim-proposals/app/views/decidim/proposals/proposals/_vote_button.html.erb) is overridden only inside the tag  `<div id="proposal-<%= proposal.id %>-vote-button" class="button--vote-button">`. You only need to substitute the part inside.
 
 To cast a vote a `POST` action is needed with the parameters `proposal_id`, `from_proposals_list` and `weight`. The route where to send the vote can be constructed such as:
 
@@ -333,13 +329,13 @@ This view must implement the number of votes already cast. It requires an HTML t
 
 You can also completely hide this view (using `voting.show_votes_count_view = ""` in the manifest declaration). This is useful if you are using the same `show_vote_button_view` to also display the total counters (or your implementation does not use that).
 
-**Notes for view `proposal_m_cell_footer`**
+**Notes for cell `voting.proposal_metadata_cell`**
 
-This view is used by the proposal cell in lists. It must implement the vote button and the vote count. The vote button must be a link with the same characteristics as the one explained above for the `show_vote_button_view` (typically you can just render the same view using `<%= render partial: my/path/to/view, { locals: model: proposal, from_proposals_list: true } %>`).
+This is the Decidim cell used to provide the metadata that is rendered at the bottom of a proposal card. If empty, defaults to [ProposalMetadataCell](https://github.com/decidim/decidim/blob/release/0.28-stable/decidim-proposals/app/cells/decidim/proposals/proposal_metadata_cell.rb), **wich does not renders the votes**.
 
-Note that, it is strongly recommended to add and HTML tag element with the id `proposal-<%= proposal.id %>-votes-count` so the Ajax vote re-loader can work. Even if you don't use (in this case use a `style="display:none"` attribute), this is because the Ajax reloader always look for this element and throw JavaScript errors if not.
+What this cell must do is to provide an array of items to render as part of the cell footer. Check the example used at the [voting cards implementation](app/cells/decidim/decidim_awesome/voting/proposal_metadata_cell.rb) for reference.
 
-##### 17.1 GraphQL Types for weighted voting
+##### 16.1 GraphQL Types for weighted voting
 
 When a weighed voting mechanism is selected, the GraphQL API will show those weights separated in each proposal.
 The attribute that holds this information is `vote_weights`, a query example could look like this:
@@ -361,7 +357,7 @@ The attribute that holds this information is `vote_weights`, a query example cou
 }
 ```
 
-#### 18. Limiting amendments in proposals
+#### 17. Limiting amendments in proposals
 
 By default, when proposals can be amended, any number of amendments can be created.
 
@@ -401,9 +397,8 @@ And then execute:
 
 ```bash
 bundle
-bundle exec rails decidim_decidim_awesome:install:migrations
-bundle exec rails decidim:upgrade
-bundle exec rails db:migrate
+bin/rails decidim:upgrade
+bin/rails db:migrate
 ```
 
 Go to `yourdomain/admin/decidim_awesome` and start tweaking things!
@@ -417,6 +412,7 @@ Go to `yourdomain/admin/decidim_awesome` and start tweaking things!
 > bin/rails decidim_decidim_awesome:webpacker:install
 > ```
 
+
 If you are upgrading from a version prior to 0.8, make sure to visit the URL `/admin/decidim_awesome/checks` and run image migrations for the old images:
 
 ![Check image migrations](examples/check_image_migrations.png)
@@ -433,25 +429,27 @@ RAILS_ENV=production bin/rails decidim_awesome:active_storage_migrations:check_m
 ```
 
 The correct version of Decidim Awesome should resolved automatically by the Bundler.
-However you can force some specific version using `gem "decidim-decidim_awesome", "~> 0.10.0"` in the Gemfile.
+However you can force some specific version using `gem "decidim-decidim_awesome", "~> 0.11.0"` in the Gemfile.
 
 Depending on your Decidim version, choose the corresponding Awesome version to ensure compatibility:
 
 | Awesome version | Compatible Decidim versions |
-|-----------------|-----------------------------|
-| 0.10.x          | >= 0.26.7, >= 0.27.3        |
-| 0.9.2           | >= 0.26.7, >= 0.27.3        |
-| 0.9.x           | 0.26.x, 0.27.x              |
-| 0.8.x           | 0.25.x, 0.26.x              |
-| 0.7.x           | 0.23.x, 0.24.x              |
-| 0.6.x           | 0.22.x, 0.23.x              |
-| 0.5.x           | 0.21.x, 0.22.x              |
+|---|---|
+| 0.11.x | 0.28.x |
+| 0.10.x | >= 0.26.7, >= 0.27.x |
+| 0.9.2 | >= 0.26.7, >= 0.27.3 |
+| 0.9.x | 0.26.x, 0.27.x |
+| 0.8.x | 0.25.x, 0.26.x |
+| 0.7.x | 0.23.x, 0.24.x |
+| 0.6.x | 0.22.x, 0.23.x |
+| 0.5.x | 0.21.x, 0.22.x |
 
 > *Heads up!*
+> * version 0.11.0 is only compatible with Decidim v0.28 as a major redesign makes backward compatibility impractical.
 > * version 0.10.0 requires database migrations! Don't forget the migrations step when updating.
 > * version 0.8.0 removes CSS Themes for tenants. If you have been using them you will have to manually migrate them to custom styles.
 > * version 0.8.0 uses ActiveStorage, same as Decidim 0.25. 2 new rake task have been introduced to facilitate the migration: `bin/rails decidim_awesome:active_storage_migrations:check_migration_from_carrierwave` and
-    `bin/rails decidim_awesome:active_storage_migrations:migrate_from_carrierwave`
+`bin/rails decidim_awesome:active_storage_migrations:migrate_from_carrierwave`
 > * version 0.7.1 requires database migrations! Don't forget the migrations step when updating.
 
 ## Configuration
@@ -469,13 +467,10 @@ In order to personalize default values, create an initializer such as:
 # Change some variables defaults
 Decidim::DecidimAwesome.configure do |config|
   # Enabled by default to all scopes, admins can still limit it's scope
-  config.allow_images_in_full_editor = true
+  config.allow_images_in_editors = true
 
   # Disabled by default to all scopes, admins can enable it and limit it's scope
-  config.allow_images_in_small_editor = false
-
-  # De-activated, admins don't even see it as an option
-  config.use_markdown_editor = :disabled
+  config.allow_videos_in_editors = false
 
   # Disable scoped admins
   config.scoped_admins = :disabled
@@ -567,6 +562,9 @@ DATABASE_USERNAME=<username> DATABASE_PASSWORD=<password> bundle exec rake test_
 DATABASE_USERNAME=<username> DATABASE_PASSWORD=<password> bundle exec rspec
 ```
 
+> Note: the following is not currently applicable as version v0.11 is only compatible with version Decidim v0.28
+> Is left here for future reference
+
 However, this project works with different versions of Decidim. In order to test them all, we maintain two different Gemfiles: `Gemfile` and `Gemfile.legacy`. The first one is used for development and testing the latest Decidim version supported, the second one is used for testing against the old Decidim version.
 
 You can run run tests against the legacy Decidim versions by using:
@@ -574,24 +572,24 @@ You can run run tests against the legacy Decidim versions by using:
 ```bash
 export DATABASE_USERNAME=<username>
 export DATABASE_PASSWORD=<password>
-RBENV_VERSION=2.7.6 BUNDLE_GEMFILE=Gemfile.legacy bundle
-RBENV_VERSION=2.7.6 BUNDLE_GEMFILE=Gemfile.legacy bundle exec rake test_app
-RBENV_VERSION=2.7.6 BUNDLE_GEMFILE=Gemfile.legacy bundle exec rspec
+RBENV_VERSION=3.1.1 BUNDLE_GEMFILE=Gemfile.legacy bundle
+RBENV_VERSION=3.1.1 BUNDLE_GEMFILE=Gemfile.legacy bundle exec rake test_app
+RBENV_VERSION=3.1.1 BUNDLE_GEMFILE=Gemfile.legacy bundle exec rspec
 ```
 
-For convenience, you can use the scripts `bin/rspec` and `bin/rspec-legacy` to run tests against one or the other version:
+For convenience, you can use the scripts `bin/test` and `bin/test-legacy` to run tests against one or the other version:
 
 ```bash
-bin/rspec spec/
-bin/rspec-legacy spec/
+bin/test spec/
+bin/test-legacy spec/
 ```
 
 - Rbenv is required for this script to work.
 
 > **NOTE:** Remember to reset the database when changing between tests:
 > ```bash
-> bin/rspec --reset
-> bin/rspec-legacy --reset
+> bin/test --reset
+> bin/test-legacy --reset
 > ```
 
 
@@ -626,4 +624,4 @@ This engine is distributed under the GNU AFFERO GENERAL PUBLIC LICENSE.
 
 ## Credits
 
-This plugin maintainted by ![PokeCode](app/packs/images/decidim/decidim_awesome/pokecode-logo.png)
+This plugin maintainted by [![PokeCode](app/packs/images/decidim/decidim_awesome/pokecode-logo.png) PokeCode](https://pokecode.net/)

data/app/cells/concerns/decidim/decidim_awesome/global_menu_cell_override.rb

@@ -0,0 +1,20 @@
+# frozen_string_literal: true
+
+module Decidim
+  module DecidimAwesome
+    module GlobalMenuCellOverride
+      extend ActiveSupport::Concern
+
+      included do
+        def cache_hash
+          [
+            "decidim/content_blocks/global_menu",
+            current_organization.cache_key_with_version,
+            I18n.locale,
+            awesome_config[:home_content_block_menu].to_s
+          ].join(Decidim.cache_key_separator)
+        end
+      end
+    end
+  end
+end

data/app/cells/concerns/decidim/decidim_awesome/proposal_l_cell_override.rb

@@ -0,0 +1,44 @@
+# frozen_string_literal: true
+
+module Decidim
+  module DecidimAwesome
+    module ProposalLCellOverride
+      extend ActiveSupport::Concern
+
+      included do
+        private
+
+        def metadata_cell
+          awesome_voting_manifest_for(resource&.component)&.proposal_metadata_cell.presence || "decidim/proposals/proposal_metadata"
+        end
+
+        # rubocop:disable Metrics/CyclomaticComplexity
+        # rubocop:disable Metrics/PerceivedComplexity
+        def cache_hash
+          hash = []
+          hash << I18n.locale.to_s
+          hash << model.cache_key_with_version
+          hash << model.proposal_votes_count
+          hash << model.extra_fields&.reload&.vote_weight_totals
+          hash << model.endorsements_count
+          hash << model.comments_count
+          hash << Digest::MD5.hexdigest(model.component.cache_key_with_version)
+          hash << Digest::MD5.hexdigest(resource_image_path) if resource_image_path
+          hash << render_space? ? 1 : 0
+          if current_user
+            hash << current_user.cache_key_with_version
+            hash << current_user.follows?(model) ? 1 : 0
+          end
+          hash << model.follows_count
+          hash << Digest::MD5.hexdigest(model.authors.map(&:cache_key_with_version).to_s)
+          hash << (model.must_render_translation?(model.organization) ? 1 : 0) if model.respond_to?(:must_render_translation?)
+          hash << model.component.participatory_space.active_step.id if model.component.participatory_space.try(:active_step)
+
+          hash.join(Decidim.cache_key_separator)
+        end
+        # rubocop:enable Metrics/CyclomaticComplexity
+        # rubocop:enable Metrics/PerceivedComplexity
+      end
+    end
+  end
+end

data/app/cells/decidim/decidim_awesome/content_blocks/map/show.erb

@@ -1,14 +1,7 @@
-<section class="wrapper-home map-block home-section">
-  <div class="row">
+<section class="map-block home__section">
+  <%= content_tag("h3", section_title) if section_title.present? %>
 
-    <%= section_title %></h3>
-
-    <div class="row">
-      <div class="columns medium-12">
-        <%= awesome_map_for global_map_components do %>
-          <%= render partial: "decidim/decidim_awesome/map_component/map/map_template.html", locals: { categories: all_categories, map_height: model.settings.map_height } %>
-        <% end %>
-      </div>
-    </div>
-  </div>
+  <%= awesome_map_for global_map_components do %>
+    <%= render partial: "decidim/decidim_awesome/map_component/map/map_template.html", locals: { categories: all_categories, map_height: model.settings.map_height } %>
+  <% end %>
 </section>

data/app/cells/decidim/decidim_awesome/voting/proposal_metadata_cell.rb

@@ -0,0 +1,54 @@
+# frozen_string_literal: true
+
+module Decidim
+  module DecidimAwesome
+    module Voting
+      # This cell renders metadata for an instance of a Proposal
+      class ProposalMetadataCell < ::Decidim::Proposals::ProposalMetadataCell
+        private
+
+        def proposal_items
+          [coauthors_item, comments_count_item, endorsements_count_item, weight_count_item, state_item, emendation_item]
+        end
+
+        def current_vote
+          @current_vote ||= Decidim::Proposals::ProposalVote.find_by(author: current_user, proposal: resource)
+        end
+
+        def user_voted_weight
+          current_vote&.weight
+        end
+
+        def all_weights
+          @all_weights ||= begin
+            weights = [3, 2, 1]
+            weights << 0 if resource.component.settings.voting_cards_show_abstain
+            weights.index_with do |weight|
+              resource.weight_count(weight)
+            end
+          end
+        end
+
+        def weight_tags
+          @weight_tags ||= all_weights.map do |num, weight|
+            content_tag "span", title: resource.manifest.label_for(num), class: "voting-weight_#{num}" do
+              "#{t("decidim.decidim_awesome.voting.voting_cards.weights.weight_#{num}_short")} #{weight}"
+            end.html_safe
+          end
+        end
+
+        def weight_count_item
+          return unless resource.respond_to?(:weight_count)
+          return if resource.component.current_settings.votes_hidden?
+          return if resource&.rejected? || resource&.withdrawn?
+
+          {
+            text: weight_tags.join(" | ").html_safe,
+            icon: "#{user_voted_weight ? "checkbox" : "close"}-circle-line",
+            data_attributes: all_weights.transform_keys { |num| "weight-#{num}" }
+          }
+        end
+      end
+    end
+  end
+end

data/app/cells/decidim/decidim_awesome/voting/voting_cards_proposal/modal.erb

@@ -0,0 +1,18 @@
+<%= decidim_modal id: "voting-cards-modal-help", class:"reveal vote_proposal_modal voting-voting_cards" do %>
+  <div data-dialog-container>
+    <div class="reveal__content">
+      <div class="instructions mb-4"><%= vote_instructions %></div>
+      <div class="current-choice voting-voting_cards mb-4">
+        <div class="vote-card"></div>
+      </div>
+      <div class="future-dismiss">
+          <%= check_box_tag "voting_cards-skip_help", current_component.id, false %>
+          <%= label_tag "voting_cards-skip_help", t("decidim.decidim_awesome.voting.voting_cards.modal.skip") %>
+      </div>
+    </div>
+  </div>
+  <div data-dialog-actions>
+    <button type="button" class="button button__lg button__primary hover:bg-secondary vote-action" style="background-color: #e02d2d;"><%= t("decidim.decidim_awesome.voting.voting_cards.modal.proceed") %></button>
+    <button type="button" class="button button__lg button__transparent-secondary cancel-action hollow secondary" data-dialog-close="voting-cards-modal-help"><%= t("decidim.decidim_awesome.voting.voting_cards.modal.cancel") %></button>
+  </div>
+<% end %>