Merge branch 'develop' into patch-4

Author: paulinebessoles

antora-playbook.yml

@@ -5,16 +5,16 @@
 site:
   title: Decidim Docs
   url: https://docs.decidim.org
-  start_page: v0.29@en:ROOT:index.adoc
+  start_page: v0.30@en:ROOT:index.adoc
 content:
   sources:
     - url: &documentation https://github.com/decidim/documentation
       start_path: docs/en
-      branches: [release/0.29-stable, release/0.28-stable, release/0.27-stable, develop]
+      branches: [release/0.30-stable, release/0.29-stable, release/0.28-stable, release/0.27-stable, develop]
       edit_url: "https://github.com/decidim/documentation/edit/{refname}/{path}"
     - url: https://github.com/decidim/decidim
       start_path: docs
-      branches: [release/0.29-stable, release/0.28-stable, release/0.27-stable, develop]
+      branches: [release/0.30-stable, release/0.29-stable, release/0.28-stable, release/0.27-stable, develop]
 ui:
   bundle:
     url: https://github.com/decidim/documentation-antora-ui/releases/download/v0.4/ui-bundle.zip

docs/en/antora.yml

@@ -1,6 +1,6 @@
 name: en
 title: "Decidim Documentation"
-version: develop
+version: v0.30
 asciidoc:
   attributes:
     page-lang: en@

docs/en/modules/ROOT/pages/index.adoc

@@ -10,7 +10,7 @@ You’ve found the documentation for Decidim. Learn about the project at https:/
 
 [NOTE]
 ====
-This is the documentation for the `v0.30` version. You can see this same documentation site for other versions: xref:v0.29@ROOT:index.adoc[v0.29], xref:v0.28@ROOT:index.adoc[v0.28], xref:v0.27@ROOT:index.adoc[v0.27] and xref:develop@ROOT.index.adoc[develop].
+This is the documentation for the `develop` branch. You can see this same documentation site for other versions: xref:v0.30@ROOT:index.adoc[v0.30], xref:v0.29@ROOT:index.adoc[v0.29], xref:v0.28@ROOT:index.adoc[v0.28] and xref:v0.27@ROOT:index.adoc[v0.27]
 ====
 
 // * Read the xref:ROOT:getting-started.adoc[Getting Started guide]

docs/en/modules/admin/pages/components/blog.adoc

@@ -2,11 +2,11 @@
 
 == Understand the basics
 
-The Blog component allows administrators to post news about a participatory space, that participants can read to get updates. 
+The Blog component allows administrators to post news about a participatory space, which participants can read to get updates. 
 
 image::components/blog/example01.png[Example of blog posts list]
 
-All blog posts are available in the posts list, and participants can click each blog post to learn more about what's new. 
+All blog posts are available on the post list, and participants can click each blog post to learn more about what's new. 
 
 image::components/blog/example02.png[Example of a blog post]
 
@@ -24,7 +24,7 @@ Then:
 . Fill the component creation form
 
 You can still update this form and the configuration after creating the component, by clicking the 
-image:icons/action_configure.png[Configure icon] icon in the components list. 
+image:icons/action_configure.png[Configure icon] icon on the components list. 
 
 image::components/blog/component.png[Add component form]
 
@@ -54,7 +54,7 @@ image::components/blog/component.png[Add component form]
 
 |Comments enabled
 |Optional
-|Whether you want participants to be able to comment on the blog posts.
+|If you want participants to be able to comment on the blog posts.
 
 |Comments max length
 |Optional
@@ -69,7 +69,7 @@ image::components/blog/component.png[Add component form]
 
 |Announcement
 |Optional
-|A general announcement that'll be visible on the general blog landing page.
+|A general announcement that will be visible on the general blog landing page.
 
 |Comments blocked
 |Optional
@@ -87,7 +87,7 @@ image::components/blog/component.png[Add component form]
 
 == Manage posts
 
-To start creating and managing posts, click in the component title in the navigation bar or in the component list, or click in the 
+To start creating and managing posts, click on the component title in the navigation bar or on the component list, or click on the 
 image:icons/action_edit.png[Manage component icon] icon on the components list.
 
 image:components/blog/manage_posts.png[Manage posts table]
@@ -130,33 +130,33 @@ image:components/blog/new_post.png[New post form]
 
 |image:icons/action_edit.png[Edit icon]
 |Edit
-|To edit this post.
+|Edit this post.
 
 |image:icons/action_folder.png[Folder icon]
 |Folder
 |For classifying attachments.
 
 |image:icons/action_attachments.png[Attachments icon]
 |Attachments
-|To add documents related to the post.
+|Add documents related to the post.
 
 |image:icons/action_preview.png[Preview icon]
 |Preview
-|To see how it's shown in the frontend to participants.
+|See how it's shown in the frontend to participants.
 
 |image:icons/action_permissions.png[Permissions icon]
 |Permissions
-|To handle the authorizations needed to comment or endorse this specific blog post.
+|Handle the authorizations needed to comment or endorse this specific blog post.
 
 |image:icons/action_delete.png[Delete icon]
 |Delete
-|To delete this post.
+|Delete this post.
 
 |===
 
 == Examples
 
-Below, you can find some links to examples blog components:
+Below, you can find some links to example blog components:
 
 * https://meta.decidim.org/processes/news/f/1719/posts[Latest news of the Decidim association]
 * https://www.decidim.barcelona/processes/volem-decidir/f/6338/posts[News on a participatory process in Barcelona]

docs/en/modules/admin/pages/features/social_features/newsletters.adoc

@@ -23,7 +23,7 @@ for instance a Participatory Budgeting process.
 
 == Configuration
 
-To access the Newsletters panel, go in the administration panel and click the "Newsletters" item in the administration navigation bar.
+To access the Newsletters panel, go to the administration panel and click the "Newsletters" item in the administration navigation bar.
 
 image::features/newsletters/newsletter_menu.png[Newsletter administrator menu]
 
@@ -50,7 +50,7 @@ Click the "Use this template" button below the template you want to use.
 
 === Write the newsletter
 
-Depending in which template you've chosen, you have to fill a form with different fields. 
+Depending on which template you've chosen, you have to fill a form with different fields. 
 
 NOTE: You can use "%\{name}" anywhere in the body or subject to be automatically replaced by the participant's name.
 
@@ -104,7 +104,7 @@ Allowed file extensions: JPG JPEG PNG WEBP
 
 |===
 
-Once you wrote the newsletter, click the "Save and preview" button. 
+Once you have written the newsletter, click the "Save and preview" button. 
 
 === Preview the newsletter
 
@@ -116,23 +116,23 @@ image::features/newsletters/newsletter_preview_basic_example.png[Newsletter new
 === Send a test email
 
 If you want to review the newsletter directly in your mailbox, click the "Send me a test email" button at the top right of the page. 
-You receive the newsletter directly at the email address registered for your participant account. 
+You will receive the newsletter directly on the email address registered for your participant account. 
 
 === Select recipients to deliver
 
-If you want to only communicate about a given space or neighborhood, you can choose the which participants you're sending the newsletter to. 
+If you want to only communicate about a given space or neighborhood, you can choose which participants you're sending the newsletter to. 
 To do so, click the "Select recipients to deliver" button. 
 
 NOTE: If you don't want to send your newsletter to a specific segment, select "Send to all users"
 
 There, you can choose between sending the newsletter to:
 
 * All confirmed users
-* All confirmed users that have participated in any of the selected participatory spaces in the list
-* All confirmed users that have followed any of the selected participatory spaces in the list
-* All the participants that have selected an scope in their "My interests" settings in their account.
+* All confirmed users that have participated in any of the selected participatory spaces on the list
+* All confirmed users that have followed any of the selected participatory spaces on the list
+* All the participants that have selected an scope in their "My interests" settings on their account.
 
-NOTE: Even if a participant has a confirmed account and is following a space, the system don't send them a newsletter email if they
+NOTE: Even if a participant has a confirmed account and is following a space, the system won't send them a newsletter email if they
 haven't accepted it in their xref:admin:features/participant_actions/my_account#_notifications_settings.adoc[notifications] settings.
 
 image::features/newsletters/newsletter_select_recipients.png[Newsletter select recipients]
@@ -149,7 +149,7 @@ Before sending it, a pop-up appears to make sure you reviewed everything and are
 
 image::features/newsletters/newsletter_deliver_modal.png[Newsletter deliver modal]
 
-NOTE: Once a newsletter is sent it can't be undone nor edited. If you have multiple languages active, 
+NOTE: Once a newsletter is sent it can't be undone or edited. If you have multiple languages active, 
 be careful with reviewing all the languages well before sending.
 
 == Manage newsletters

docs/en/modules/admin/pages/features/transparency/fingerprint.adoc

@@ -18,7 +18,7 @@ yourself, you can use a http://www.md5calc.com/sha256[MD5 calculator online] and
 . Click in the "Check fingerprint" link at the bottom of the page
 . Copy the source field value
 . Go to a MD5 calculator online (External link) and copy-paste the source data
-. Check that fingerprint are the same
+. Check that the fingerprints are the same
 
 image:features/fingerprint/content.png[Check fingerprint link in page bottom]
 

docs/en/modules/admin/pages/spaces/assemblies/assembly_creation.adoc

@@ -2,14 +2,13 @@
 
 == Understand the basics
 
-Assemblies allows administrators to configure components inside a long-lasting space, with defined members. 
-To start creating an assembly, when on the assembly list, click the "New assembly" button at the top right of the page. 
+Assemblies allow administrators to configure components inside a long-lasting space, with defined members. To start creating an assembly, when on the link:https://docs.decidim.org/en/develop/admin/spaces/assemblies#_manage_assemblies[assembly list], click the "New assembly" button at the top right of the page. 
 
 The assembly creation form is divided into different sections that are detailed in the sections below. 
 
-Once you created an assembly, in the secondary navigation panel, you can see all the assembly configurations available:
+Once you create an assembly, you can see all the assembly configurations available in the secondary navigation panel:
 
-* xref:admin:spaces/assemblies/assembly_creation.adoc[About this assembly]: here you can access and edit all the fields from the creation form.
+* xref:admin:spaces/assemblies/assembly_creation.adoc[About this assembly] (Here you can access and edit all the fields from the creation form.)
 * xref:admin:spaces/assemblies/landing_page.adoc[Landing page]
 * xref:admin:spaces/assemblies/components.adoc[Components]
 * xref:admin:spaces/assemblies/categories.adoc[Categories]
@@ -21,7 +20,7 @@ Once you created an assembly, in the secondary navigation panel, you can see all
 
 == General information
 
-This section allows to provide a general description about the assembly, mainly a title, URL, and description. 
+This section allows an admin to provide general information about the assembly: title, URL, and description. 
 
 image::spaces/assemblies/assemblies_new_form_general_info.png[New assembly form general info section]
 
@@ -32,7 +31,7 @@ image::spaces/assemblies/assemblies_new_form_general_info.png[New assembly form
 
 |Title
 |Required
-|Title of the assembly, "General Committee" or "neighborhood city council" for example. 
+|Title of the assembly: "General Committee" or "neighborhood city council" for example. 
 |Visible in the card of the assembly on the homepage, the assemblies index, the navigation, and the "Hero image and CTA" landing page block.
 
 |Subtitle
@@ -58,12 +57,12 @@ start with a letter.
 
 |Short description
 |Required
-|A short explanation of what's your participatory process about.
+|A short explanation of what your assembly is about.
 |Visible in the "Main data" landing page block.
 
 |Description
 |Required
-|A long explanation of what's your assembly about.
+|A long explanation of what your assembly is about.
 |Visible in the "Main data" landing page block.
 
 |Purpose of action
@@ -90,7 +89,7 @@ start with a letter.
 
 == Duration
 
-This section allows to provide information about the assembly important dates. 
+This section allows to provide information about the assembly's important dates. 
 
 image::spaces/assemblies/assemblies_new_form_duration.png[New assembly form duration section]
 
@@ -138,11 +137,11 @@ image::spaces/assemblies/assemblies_new_form_images.png[New assembly form images
 |Home image
 |Optional
 |Image used in presentation cards of this process. Guidance for file: Has to be an image or a document.
-For images, use preferably landscape images, the service crops the image. Maximum file size: 10 MB
+For images, landscape images are preferred, as the service crops the image. Maximum file size: 10 MB
 
 |Banner image
-|Optional
-|Deprecated, isn't used anywhere. Use "Hero image and CTA" content block on the landing page instead. 
+|Deprecated
+|Use link:https://docs.decidim.org/en/develop/admin/spaces/assemblies/landing_page.html#_hero_image_and_cta[Hero image and CTA] content block on the landing page instead. 
 
 |===
 
@@ -164,11 +163,11 @@ image::spaces/assemblies/assemblies_new_form_filters.png[New assembly form filte
 
 |Scope
 |Optional
-|Which xref:admin:settings/scopes.adoc[Scopes] does this assembly belongs to.
+|Which xref:admin:settings/scopes.adoc[Scopes] this assembly belongs to.
 
 |Area
 |Optional
-|Which xref:admin:settings/areas.adoc[Area] does this assembly belongs to.
+|Which xref:admin:settings/areas.adoc[Areas] this assembly belongs to.
 
 |===
 
@@ -185,33 +184,33 @@ image::spaces/assemblies/assemblies_new_form_metadata.png[New assembly form meta
 
 |What is decided
 |Optional
-|The issue of the assembly, the object of what is decided. 
+|The issue of the assembly; the object of what is decided. 
 
 |How is it decided
 |Optional
 |The decision making process inside the assembly. 
 
 |Scope metadata
 |Optional
-|Metadata on the assembly scope, if it's relevant. 
+|Metadata on the assembly scope, if relevant. 
 
 |Promoter group
 |Optional
 |If a specific group is at the origin of the assembly, like a city direction, an association committee, etc. 
 
 |Organization area
 |Optional
-|The organization domain or category, if it's relevant. 
+|The organization domain or category, if relevant. 
 
 |Who participates
 |Optional
-|Who are the authorized participants, who can participate to the assembly. 
+|Who are the authorized participants that can participate to the assembly. 
 
 |===
 
 == Visibility
 
-This section allows administrators to configure the process placement in the different pages and its publicity or no. 
+This section allows administrators to configure the process placement in the different pages and its publicity. 
 
 image::spaces/assemblies/assemblies_new_form_visibility.png[New assembly form visibility section]
 
@@ -222,7 +221,7 @@ image::spaces/assemblies/assemblies_new_form_visibility.png[New assembly form vi
 
 |Parent assembly
 |Optional
-|To what other assemblies this assembly belongs. Assemblies can be nested inside one another. 
+|To which other assemblies this assembly belongs. Assemblies can be nested inside one another. 
 
 |Highlighted
 |Optional
@@ -251,7 +250,7 @@ image::spaces/assemblies/assemblies_new_form_other.png[New assembly form other s
 
 |Created by
 |Optional
-|Choose "City Council" "Public" or "Other" in case you want to specify the name of the organization that created
+|Choose "City Council", "Public", or "Other" if you want to specify the name of the organization that created
 this assembly.
 
 |Assembly type
@@ -264,6 +263,6 @@ this assembly.
 
 |Social
 |Optional
-|Which social networks profile does this assembly has. Can be X, Facebook, Instagram, YouTube, and/or GitHub. 
+|Which social networks profile this assembly has. Can be X, Facebook, Instagram, YouTube, and/or GitHub. 
 
 |===

docs/en/modules/admin/pages/spaces/conferences/registrations/invites.adoc

@@ -3,8 +3,8 @@
 == Understand the basics
 
 Administrators can invite participants to join the conference. 
-They can invite already existing participants, with an account on the platform, but also people without an account. 
-Inviting a participant sends an email to the account email address, to encourage the participant to register to the conference. 
+They can invite already existing participants, with an account on the platform, but also people without an account.
+Inviting a participant sends an email to the account email address, encouraging the participant to register for the conference. 
 
 == Manage invites
 
@@ -27,14 +27,14 @@ image::spaces/conferences/invite_participant_form.png[Invite a participant form]
 
 |Attendee type
 |Required
-|Wether this invited person already has an account or not. 
+|Whether or not this invited person already has an account.
 
 |Name
-|Required if it's a non-existing participant.
+|Required if the invitee is not already a participant.
 |Name of the invited person.
 
 |Email
-|Required if it's a non-existing participant.
+|Required if the invitee is not already a participant.
 |Email of the invited person.
 
 |User

docs/en/modules/contribute/pages/translations.adoc

@@ -21,7 +21,7 @@ If your language isn't created yet, then we need to do it as it's necessary to m
 
 == How it works
 
-If you're curios, in the technical level we have a bot (the great decidim-bot) that periodically makes a PR to the relevant branches (last releases and develop).
+If you're curious, in the technical level we have a bot (the great decidim-bot) that periodically makes a PR to the relevant branches (last releases and develop).
 
 image::translation-bot.png[Decidim Bot in GitHub]