diff --git a/.github/styles/config/vocabularies/Decidim/accept.txt b/.github/styles/config/vocabularies/Decidim/accept.txt index aa90167f8d..9bc269b2d6 100644 --- a/.github/styles/config/vocabularies/Decidim/accept.txt +++ b/.github/styles/config/vocabularies/Decidim/accept.txt @@ -4,9 +4,12 @@ CSV [Dd]ecidim [Ee]mail [Ff]aq +[Ff]avicon [Gg]amification initializer +[Kk]akogawa Keka +Mautic [Mm]oderations [Nn]ickame [Oo]fficialization diff --git a/docs/en/modules/ROOT/nav.adoc b/docs/en/modules/ROOT/nav.adoc index b5ef63ebc4..f1a6d0f437 100644 --- a/docs/en/modules/ROOT/nav.adoc +++ b/docs/en/modules/ROOT/nav.adoc @@ -31,14 +31,15 @@ *** xref:services:social_providers.adoc[Social Providers] * xref:admin:index.adoc[Admin] -** xref:admin:first_steps.adoc[First steps in Decidim] -** Settings -*** xref:admin:configuration.adoc[Configuration] -*** xref:admin:appearance.adoc[Appearance] -*** xref:admin:homepage.adoc[Homepage] -*** xref:admin:scopes.adoc[Scopes] -*** xref:admin:areas.adoc[Areas] -*** xref:admin:help_sections.adoc[Help sections] +** xref:admin:first_steps.adoc[First steps] +** xref:admin:settings.adoc[Settings] +*** xref:admin:settings/configuration.adoc[Configuration] +*** xref:admin:settings/appearance.adoc[Appearance] +*** xref:admin:settings/homepage.adoc[Homepage] +*** xref:admin:settings/scopes.adoc[Scopes] +*** xref:admin:settings/areas.adoc[Areas] +*** xref:admin:settings/help_sections.adoc[Help sections] +*** xref:admin:settings/allowed_external_domains.adoc[Allowed external domains] ** xref:admin:pages.adoc[Pages and Topics] *** xref:admin:pages/pages.adoc[Pages] *** xref:admin:pages/topics.adoc[Topics] @@ -54,16 +55,20 @@ **** xref:admin:participants/authorizations/census.adoc[Organization's census] ** xref:admin:spaces.adoc[Spaces] *** xref:admin:spaces/processes.adoc[Participatory Processes] -**** xref:admin:spaces/processes/phases.adoc[Phases] -**** xref:admin:spaces/processes/components.adoc[Components] -**** xref:admin:spaces/processes/categories.adoc[Categories] -**** xref:admin:spaces/processes/attachments.adoc[Attachments] -**** xref:admin:spaces/processes/admins.adoc[Process admins] -**** xref:admin:spaces/processes/private_participants.adoc[Private participants] -**** xref:admin:spaces/processes/moderations.adoc[Moderations] **** xref:admin:spaces/processes/groups.adoc[Process Groups] **** xref:admin:spaces/processes/types.adoc[Process Types] +**** xref:admin:spaces/processes/process_creation.adoc[Process creation] +***** xref:admin:spaces/processes/landing_page.adoc[Landing page] +***** xref:admin:spaces/processes/phases.adoc[Phases] +***** xref:admin:spaces/processes/components.adoc[Components] +***** xref:admin:spaces/processes/categories.adoc[Categories] +***** xref:admin:spaces/processes/attachments.adoc[Attachments] +***** xref:admin:spaces/processes/admins.adoc[Process admins] +***** xref:admin:spaces/processes/private_participants.adoc[Private participants] +***** xref:admin:spaces/processes/moderations.adoc[Moderations] *** xref:admin:spaces/assemblies.adoc[Assemblies] +**** xref:admin:spaces/assemblies/types.adoc[Assembly types] +**** xref:admin:spaces/assemblies/assembly_creation.adoc[Assembly creation] **** xref:admin:spaces/assemblies/components.adoc[Components] **** xref:admin:spaces/assemblies/categories.adoc[Categories] **** xref:admin:spaces/assemblies/attachments.adoc[Attachments] diff --git a/docs/en/modules/admin/assets/images/account_my_interests.png b/docs/en/modules/admin/assets/images/account_my_interests.png deleted file mode 100644 index a3bede039f..0000000000 Binary files a/docs/en/modules/admin/assets/images/account_my_interests.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/admin_appearance.png b/docs/en/modules/admin/assets/images/admin_appearance.png deleted file mode 100644 index c4e28bfe71..0000000000 Binary files a/docs/en/modules/admin/assets/images/admin_appearance.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/admin_configuration.png b/docs/en/modules/admin/assets/images/admin_configuration.png deleted file mode 100644 index 60f1f14582..0000000000 Binary files a/docs/en/modules/admin/assets/images/admin_configuration.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/admin_homepage.png b/docs/en/modules/admin/assets/images/admin_homepage.png deleted file mode 100644 index 349a1dd15d..0000000000 Binary files a/docs/en/modules/admin/assets/images/admin_homepage.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/assemblies_list.png b/docs/en/modules/admin/assets/images/assemblies_list.png deleted file mode 100644 index 0f73c4a365..0000000000 Binary files a/docs/en/modules/admin/assets/images/assemblies_list.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/assemblies_list_filter.png b/docs/en/modules/admin/assets/images/assemblies_list_filter.png deleted file mode 100644 index b6486cefeb..0000000000 Binary files a/docs/en/modules/admin/assets/images/assemblies_list_filter.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/assemblies_new_form.png b/docs/en/modules/admin/assets/images/assemblies_new_form.png deleted file mode 100644 index 53022d3191..0000000000 Binary files a/docs/en/modules/admin/assets/images/assemblies_new_form.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/assemblies_new_type_form.png b/docs/en/modules/admin/assets/images/assemblies_new_type_form.png deleted file mode 100644 index 5996f1e8d6..0000000000 Binary files a/docs/en/modules/admin/assets/images/assemblies_new_type_form.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/assemblies_organization_chart.png b/docs/en/modules/admin/assets/images/assemblies_organization_chart.png deleted file mode 100644 index 09b71e2c00..0000000000 Binary files a/docs/en/modules/admin/assets/images/assemblies_organization_chart.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/assemblies_organization_chart_filtered.png b/docs/en/modules/admin/assets/images/assemblies_organization_chart_filtered.png deleted file mode 100644 index 9af1d3605e..0000000000 Binary files a/docs/en/modules/admin/assets/images/assemblies_organization_chart_filtered.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/assemblies_settings.png b/docs/en/modules/admin/assets/images/assemblies_settings.png deleted file mode 100644 index 663c613ef7..0000000000 Binary files a/docs/en/modules/admin/assets/images/assemblies_settings.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/assemblies_type_filters.png b/docs/en/modules/admin/assets/images/assemblies_type_filters.png deleted file mode 100644 index 11fcfb8890..0000000000 Binary files a/docs/en/modules/admin/assets/images/assemblies_type_filters.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/assembly_members.png b/docs/en/modules/admin/assets/images/assembly_members.png deleted file mode 100644 index dd9e9b7b7c..0000000000 Binary files a/docs/en/modules/admin/assets/images/assembly_members.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/assembly_submenu.png b/docs/en/modules/admin/assets/images/assembly_submenu.png deleted file mode 100644 index 48428bf278..0000000000 Binary files a/docs/en/modules/admin/assets/images/assembly_submenu.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/help_sections_backend.png b/docs/en/modules/admin/assets/images/help_sections_backend.png deleted file mode 100644 index 3cc446f852..0000000000 Binary files a/docs/en/modules/admin/assets/images/help_sections_backend.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/help_sections_disable_backend.png b/docs/en/modules/admin/assets/images/help_sections_disable_backend.png deleted file mode 100644 index 8fe74c420a..0000000000 Binary files a/docs/en/modules/admin/assets/images/help_sections_disable_backend.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/help_sections_disable_frontend.png b/docs/en/modules/admin/assets/images/help_sections_disable_frontend.png deleted file mode 100644 index d2b24a3592..0000000000 Binary files a/docs/en/modules/admin/assets/images/help_sections_disable_frontend.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/help_sections_frontend.png b/docs/en/modules/admin/assets/images/help_sections_frontend.png deleted file mode 100644 index 393379c42e..0000000000 Binary files a/docs/en/modules/admin/assets/images/help_sections_frontend.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/help_sections_frontend_hide.png b/docs/en/modules/admin/assets/images/help_sections_frontend_hide.png deleted file mode 100644 index 832e7081a2..0000000000 Binary files a/docs/en/modules/admin/assets/images/help_sections_frontend_hide.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_footer_sub_hero_banner.png b/docs/en/modules/admin/assets/images/homepage_footer_sub_hero_banner.png deleted file mode 100644 index f97cd9ec83..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_footer_sub_hero_banner.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_hero_image_back.png b/docs/en/modules/admin/assets/images/homepage_hero_image_back.png deleted file mode 100644 index 9472b2cf67..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_hero_image_back.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_hero_image_front.png b/docs/en/modules/admin/assets/images/homepage_hero_image_front.png deleted file mode 100644 index dd1c819ffc..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_hero_image_front.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_highlighted_assemblies.png b/docs/en/modules/admin/assets/images/homepage_highlighted_assemblies.png deleted file mode 100644 index bbfbfabe03..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_highlighted_assemblies.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_highlighted_conferences.png b/docs/en/modules/admin/assets/images/homepage_highlighted_conferences.png deleted file mode 100644 index e25e5ec937..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_highlighted_conferences.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_highlighted_consultations.png b/docs/en/modules/admin/assets/images/homepage_highlighted_consultations.png deleted file mode 100644 index 8f1937aa06..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_highlighted_consultations.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_highlighted_content_banner.png b/docs/en/modules/admin/assets/images/homepage_highlighted_content_banner.png deleted file mode 100644 index 3678150399..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_highlighted_content_banner.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_highlighted_initiatives.png b/docs/en/modules/admin/assets/images/homepage_highlighted_initiatives.png deleted file mode 100644 index ca0aa8ebf4..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_highlighted_initiatives.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_highlighted_processes.png b/docs/en/modules/admin/assets/images/homepage_highlighted_processes.png deleted file mode 100644 index 80395beae3..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_highlighted_processes.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_how_to_participate.png b/docs/en/modules/admin/assets/images/homepage_how_to_participate.png deleted file mode 100644 index e0d392a73a..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_how_to_participate.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_html_block.png b/docs/en/modules/admin/assets/images/homepage_html_block.png deleted file mode 100644 index a3be350e7c..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_html_block.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_last_activity.png b/docs/en/modules/admin/assets/images/homepage_last_activity.png deleted file mode 100644 index 6389c2e370..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_last_activity.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_organization_metrics.png b/docs/en/modules/admin/assets/images/homepage_organization_metrics.png deleted file mode 100644 index cacdde2513..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_organization_metrics.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_organization_statistics.png b/docs/en/modules/admin/assets/images/homepage_organization_statistics.png deleted file mode 100644 index 4a46468e62..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_organization_statistics.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_sub_hero_banner.png b/docs/en/modules/admin/assets/images/homepage_sub_hero_banner.png deleted file mode 100644 index 0d466a1d78..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_sub_hero_banner.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/homepage_upcoming_meetings.png b/docs/en/modules/admin/assets/images/homepage_upcoming_meetings.png deleted file mode 100644 index 97ac35d458..0000000000 Binary files a/docs/en/modules/admin/assets/images/homepage_upcoming_meetings.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/icons/action_activate.png b/docs/en/modules/admin/assets/images/icons/action_activate.png new file mode 100644 index 0000000000..d1a9576b8f Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_activate.png differ diff --git a/docs/en/modules/admin/assets/images/icons/action_assemblies.png b/docs/en/modules/admin/assets/images/icons/action_assemblies.png new file mode 100644 index 0000000000..9759727a8d Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_assemblies.png differ diff --git a/docs/en/modules/admin/assets/images/icons/action_browse.png b/docs/en/modules/admin/assets/images/icons/action_browse.png new file mode 100644 index 0000000000..72c62d49eb Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_browse.png differ diff --git a/docs/en/modules/admin/assets/images/icons/action_export.png b/docs/en/modules/admin/assets/images/icons/action_export.png new file mode 100644 index 0000000000..1fdcc1ba86 Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_export.png differ diff --git a/docs/en/modules/admin/assets/images/icons/action_moderate.png b/docs/en/modules/admin/assets/images/icons/action_moderate.png new file mode 100644 index 0000000000..a6ed95b8ab Binary files /dev/null and b/docs/en/modules/admin/assets/images/icons/action_moderate.png differ diff --git a/docs/en/modules/admin/assets/images/process_backend_metadata.png b/docs/en/modules/admin/assets/images/process_backend_metadata.png deleted file mode 100644 index 061bd43dec..0000000000 Binary files a/docs/en/modules/admin/assets/images/process_backend_metadata.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/process_frontend_metadata.png b/docs/en/modules/admin/assets/images/process_frontend_metadata.png deleted file mode 100644 index 84b207acd0..0000000000 Binary files a/docs/en/modules/admin/assets/images/process_frontend_metadata.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/process_phases.png b/docs/en/modules/admin/assets/images/process_phases.png deleted file mode 100644 index cfcdc7e06c..0000000000 Binary files a/docs/en/modules/admin/assets/images/process_phases.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/process_phases_header.png b/docs/en/modules/admin/assets/images/process_phases_header.png deleted file mode 100644 index bad9cd7a58..0000000000 Binary files a/docs/en/modules/admin/assets/images/process_phases_header.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/process_phases_list.png b/docs/en/modules/admin/assets/images/process_phases_list.png deleted file mode 100644 index 417788cccf..0000000000 Binary files a/docs/en/modules/admin/assets/images/process_phases_list.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/process_phases_new_form.png b/docs/en/modules/admin/assets/images/process_phases_new_form.png deleted file mode 100644 index fc3ab824a1..0000000000 Binary files a/docs/en/modules/admin/assets/images/process_phases_new_form.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/process_submenu.png b/docs/en/modules/admin/assets/images/process_submenu.png deleted file mode 100644 index e27c15663d..0000000000 Binary files a/docs/en/modules/admin/assets/images/process_submenu.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/processes_group_example.png b/docs/en/modules/admin/assets/images/processes_group_example.png deleted file mode 100644 index 27c64ca9a8..0000000000 Binary files a/docs/en/modules/admin/assets/images/processes_group_example.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/processes_group_landing.png b/docs/en/modules/admin/assets/images/processes_group_landing.png deleted file mode 100644 index f9c9fd785a..0000000000 Binary files a/docs/en/modules/admin/assets/images/processes_group_landing.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/processes_group_list.png b/docs/en/modules/admin/assets/images/processes_group_list.png deleted file mode 100644 index 6b31d8f8e6..0000000000 Binary files a/docs/en/modules/admin/assets/images/processes_group_list.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/processes_group_new_form.png b/docs/en/modules/admin/assets/images/processes_group_new_form.png deleted file mode 100644 index 08e1dfc26d..0000000000 Binary files a/docs/en/modules/admin/assets/images/processes_group_new_form.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/processes_list.png b/docs/en/modules/admin/assets/images/processes_list.png deleted file mode 100644 index 652c25660f..0000000000 Binary files a/docs/en/modules/admin/assets/images/processes_list.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/processes_list_filter.png b/docs/en/modules/admin/assets/images/processes_list_filter.png deleted file mode 100644 index 2dfdffa022..0000000000 Binary files a/docs/en/modules/admin/assets/images/processes_list_filter.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/processes_new_form.png b/docs/en/modules/admin/assets/images/processes_new_form.png deleted file mode 100644 index e6e0680777..0000000000 Binary files a/docs/en/modules/admin/assets/images/processes_new_form.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/scopes_filter_initiatives.png b/docs/en/modules/admin/assets/images/scopes_filter_initiatives.png deleted file mode 100644 index 2b5b042e45..0000000000 Binary files a/docs/en/modules/admin/assets/images/scopes_filter_initiatives.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/scopes_filter_processes.png b/docs/en/modules/admin/assets/images/scopes_filter_processes.png deleted file mode 100644 index 84159fd8b4..0000000000 Binary files a/docs/en/modules/admin/assets/images/scopes_filter_processes.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/scopes_list.png b/docs/en/modules/admin/assets/images/scopes_list.png deleted file mode 100644 index 8812b6c074..0000000000 Binary files a/docs/en/modules/admin/assets/images/scopes_list.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/scopes_new_form.png b/docs/en/modules/admin/assets/images/scopes_new_form.png deleted file mode 100644 index 5195f47484..0000000000 Binary files a/docs/en/modules/admin/assets/images/scopes_new_form.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/scopes_types_new_form.png b/docs/en/modules/admin/assets/images/scopes_types_new_form.png deleted file mode 100644 index bf550922e7..0000000000 Binary files a/docs/en/modules/admin/assets/images/scopes_types_new_form.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/settings/account_my_interests.png b/docs/en/modules/admin/assets/images/settings/account_my_interests.png new file mode 100644 index 0000000000..915d447247 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/account_my_interests.png differ diff --git a/docs/en/modules/admin/assets/images/settings/admin_appearance_colors.png b/docs/en/modules/admin/assets/images/settings/admin_appearance_colors.png new file mode 100644 index 0000000000..dcb230490d Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/admin_appearance_colors.png differ diff --git a/docs/en/modules/admin/assets/images/settings/admin_appearance_highlighted_banner.png b/docs/en/modules/admin/assets/images/settings/admin_appearance_highlighted_banner.png new file mode 100644 index 0000000000..1c250dd44e Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/admin_appearance_highlighted_banner.png differ diff --git a/docs/en/modules/admin/assets/images/settings/admin_appearance_homepage_appearance.png b/docs/en/modules/admin/assets/images/settings/admin_appearance_homepage_appearance.png new file mode 100644 index 0000000000..47560fbb76 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/admin_appearance_homepage_appearance.png differ diff --git a/docs/en/modules/admin/assets/images/settings/admin_appearance_layout.png b/docs/en/modules/admin/assets/images/settings/admin_appearance_layout.png new file mode 100644 index 0000000000..fad021b183 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/admin_appearance_layout.png differ diff --git a/docs/en/modules/admin/assets/images/settings/admin_appearance_omnipresent_banner.png b/docs/en/modules/admin/assets/images/settings/admin_appearance_omnipresent_banner.png new file mode 100644 index 0000000000..1916b51aa0 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/admin_appearance_omnipresent_banner.png differ diff --git a/docs/en/modules/admin/assets/images/settings/admin_configuration.png b/docs/en/modules/admin/assets/images/settings/admin_configuration.png new file mode 100644 index 0000000000..457183cc1b Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/admin_configuration.png differ diff --git a/docs/en/modules/admin/assets/images/settings/admin_homepage.png b/docs/en/modules/admin/assets/images/settings/admin_homepage.png new file mode 100644 index 0000000000..91ad46c3f5 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/admin_homepage.png differ diff --git a/docs/en/modules/admin/assets/images/settings/allowed_external_domains_admin_panel.png b/docs/en/modules/admin/assets/images/settings/allowed_external_domains_admin_panel.png new file mode 100644 index 0000000000..3bf50a0477 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/allowed_external_domains_admin_panel.png differ diff --git a/docs/en/modules/admin/assets/images/settings/allowed_external_domains_pop-up.png b/docs/en/modules/admin/assets/images/settings/allowed_external_domains_pop-up.png new file mode 100644 index 0000000000..6824f2799f Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/allowed_external_domains_pop-up.png differ diff --git a/docs/en/modules/admin/assets/images/settings/appearance_colors.png b/docs/en/modules/admin/assets/images/settings/appearance_colors.png new file mode 100644 index 0000000000..e8bc61d5b7 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/appearance_colors.png differ diff --git a/docs/en/modules/admin/assets/images/settings/appearance_layout_footer_logo.png b/docs/en/modules/admin/assets/images/settings/appearance_layout_footer_logo.png new file mode 100644 index 0000000000..4deb9e0ce9 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/appearance_layout_footer_logo.png differ diff --git a/docs/en/modules/admin/assets/images/settings/appearance_omnipresent_banner.png b/docs/en/modules/admin/assets/images/settings/appearance_omnipresent_banner.png new file mode 100644 index 0000000000..09823272a9 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/appearance_omnipresent_banner.png differ diff --git a/docs/en/modules/admin/assets/images/settings/example_homepage_barcelona.png b/docs/en/modules/admin/assets/images/settings/example_homepage_barcelona.png new file mode 100644 index 0000000000..43a1b1e4db Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/example_homepage_barcelona.png differ diff --git a/docs/en/modules/admin/assets/images/settings/example_homepage_beta.png b/docs/en/modules/admin/assets/images/settings/example_homepage_beta.png new file mode 100644 index 0000000000..bf1d930498 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/example_homepage_beta.png differ diff --git a/docs/en/modules/admin/assets/images/settings/example_homepage_borgerkraft.png b/docs/en/modules/admin/assets/images/settings/example_homepage_borgerkraft.png new file mode 100644 index 0000000000..cf175bf96f Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/example_homepage_borgerkraft.png differ diff --git a/docs/en/modules/admin/assets/images/settings/example_homepage_metadecidim.png b/docs/en/modules/admin/assets/images/settings/example_homepage_metadecidim.png new file mode 100644 index 0000000000..c4ccc06e66 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/example_homepage_metadecidim.png differ diff --git a/docs/en/modules/admin/assets/images/settings/help_sections_backend.png b/docs/en/modules/admin/assets/images/settings/help_sections_backend.png new file mode 100644 index 0000000000..408c3689db Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/help_sections_backend.png differ diff --git a/docs/en/modules/admin/assets/images/settings/help_sections_disable_backend.png b/docs/en/modules/admin/assets/images/settings/help_sections_disable_backend.png new file mode 100644 index 0000000000..1c87d223ba Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/help_sections_disable_backend.png differ diff --git a/docs/en/modules/admin/assets/images/settings/help_sections_frontend.png b/docs/en/modules/admin/assets/images/settings/help_sections_frontend.png new file mode 100644 index 0000000000..b5451ee3cd Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/help_sections_frontend.png differ diff --git a/docs/en/modules/admin/assets/images/settings/help_sections_frontend_hide.png b/docs/en/modules/admin/assets/images/settings/help_sections_frontend_hide.png new file mode 100644 index 0000000000..bcb16bedf0 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/help_sections_frontend_hide.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_footer_sub_hero_banner.png b/docs/en/modules/admin/assets/images/settings/homepage_footer_sub_hero_banner.png new file mode 100644 index 0000000000..c60a5db336 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_footer_sub_hero_banner.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_global_menu.png b/docs/en/modules/admin/assets/images/settings/homepage_global_menu.png new file mode 100644 index 0000000000..a37446cc56 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_global_menu.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_hero_image_back.png b/docs/en/modules/admin/assets/images/settings/homepage_hero_image_back.png new file mode 100644 index 0000000000..25e0faf5a2 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_hero_image_back.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_hero_image_front.png b/docs/en/modules/admin/assets/images/settings/homepage_hero_image_front.png new file mode 100644 index 0000000000..e13886aca3 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_hero_image_front.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_highlighted_assemblies.png b/docs/en/modules/admin/assets/images/settings/homepage_highlighted_assemblies.png new file mode 100644 index 0000000000..701878c22d Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_highlighted_assemblies.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_highlighted_conferences.png b/docs/en/modules/admin/assets/images/settings/homepage_highlighted_conferences.png new file mode 100644 index 0000000000..3cdb14fdf0 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_highlighted_conferences.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_highlighted_content_banner.png b/docs/en/modules/admin/assets/images/settings/homepage_highlighted_content_banner.png new file mode 100644 index 0000000000..a59fda37b9 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_highlighted_content_banner.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_highlighted_initiatives.png b/docs/en/modules/admin/assets/images/settings/homepage_highlighted_initiatives.png new file mode 100644 index 0000000000..6d0c84ca1b Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_highlighted_initiatives.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_highlighted_processes.png b/docs/en/modules/admin/assets/images/settings/homepage_highlighted_processes.png new file mode 100644 index 0000000000..06179acceb Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_highlighted_processes.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_how_to_participate.png b/docs/en/modules/admin/assets/images/settings/homepage_how_to_participate.png new file mode 100644 index 0000000000..c85370d1d4 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_how_to_participate.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_html_block.png b/docs/en/modules/admin/assets/images/settings/homepage_html_block.png new file mode 100644 index 0000000000..becaa06815 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_html_block.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_html_block_barcelona.png b/docs/en/modules/admin/assets/images/settings/homepage_html_block_barcelona.png new file mode 100644 index 0000000000..b69c3d7148 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_html_block_barcelona.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_html_block_kakogawa.png b/docs/en/modules/admin/assets/images/settings/homepage_html_block_kakogawa.png new file mode 100644 index 0000000000..29539514fa Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_html_block_kakogawa.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_html_block_lausanne.png b/docs/en/modules/admin/assets/images/settings/homepage_html_block_lausanne.png new file mode 100644 index 0000000000..3a4a3c0765 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_html_block_lausanne.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_html_block_nyc.png b/docs/en/modules/admin/assets/images/settings/homepage_html_block_nyc.png new file mode 100644 index 0000000000..6d73c51bc0 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_html_block_nyc.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_last_activity.png b/docs/en/modules/admin/assets/images/settings/homepage_last_activity.png new file mode 100644 index 0000000000..845e773eb6 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_last_activity.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_organization_metrics.png b/docs/en/modules/admin/assets/images/settings/homepage_organization_metrics.png new file mode 100644 index 0000000000..891af80cc1 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_organization_metrics.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_organization_statistics.png b/docs/en/modules/admin/assets/images/settings/homepage_organization_statistics.png new file mode 100644 index 0000000000..332aa3db88 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_organization_statistics.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_sub_hero_banner.png b/docs/en/modules/admin/assets/images/settings/homepage_sub_hero_banner.png new file mode 100644 index 0000000000..000312f93c Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_sub_hero_banner.png differ diff --git a/docs/en/modules/admin/assets/images/settings/homepage_upcoming_meetings.png b/docs/en/modules/admin/assets/images/settings/homepage_upcoming_meetings.png new file mode 100644 index 0000000000..a274f47d37 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/homepage_upcoming_meetings.png differ diff --git a/docs/en/modules/admin/assets/images/settings/scopes_filter_assemblies.png b/docs/en/modules/admin/assets/images/settings/scopes_filter_assemblies.png new file mode 100644 index 0000000000..0d90f6d022 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/scopes_filter_assemblies.png differ diff --git a/docs/en/modules/admin/assets/images/settings/scopes_filter_processes.png b/docs/en/modules/admin/assets/images/settings/scopes_filter_processes.png new file mode 100644 index 0000000000..5f205c6cb5 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/scopes_filter_processes.png differ diff --git a/docs/en/modules/admin/assets/images/settings/scopes_list.png b/docs/en/modules/admin/assets/images/settings/scopes_list.png new file mode 100644 index 0000000000..7d11e64bde Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/scopes_list.png differ diff --git a/docs/en/modules/admin/assets/images/settings/scopes_new_form.png b/docs/en/modules/admin/assets/images/settings/scopes_new_form.png new file mode 100644 index 0000000000..a47d6faf23 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/scopes_new_form.png differ diff --git a/docs/en/modules/admin/assets/images/settings/scopes_types_new_form.png b/docs/en/modules/admin/assets/images/settings/scopes_types_new_form.png new file mode 100644 index 0000000000..aaf13f6410 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/scopes_types_new_form.png differ diff --git a/docs/en/modules/admin/assets/images/settings/settings_configuration_social.png b/docs/en/modules/admin/assets/images/settings/settings_configuration_social.png new file mode 100644 index 0000000000..95518ac382 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/settings_configuration_social.png differ diff --git a/docs/en/modules/admin/assets/images/settings/settings_configuration_welcome.png b/docs/en/modules/admin/assets/images/settings/settings_configuration_welcome.png new file mode 100644 index 0000000000..c0338e7b0f Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/settings_configuration_welcome.png differ diff --git a/docs/en/modules/admin/assets/images/settings/settings_menu.png b/docs/en/modules/admin/assets/images/settings/settings_menu.png new file mode 100644 index 0000000000..b10dd36a57 Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/settings_menu.png differ diff --git a/docs/en/modules/admin/assets/images/settings/settings_sidebar_menu.png b/docs/en/modules/admin/assets/images/settings/settings_sidebar_menu.png new file mode 100644 index 0000000000..27c509e5cb Binary files /dev/null and b/docs/en/modules/admin/assets/images/settings/settings_sidebar_menu.png differ diff --git a/docs/en/modules/admin/assets/images/settings_configuration_social.png b/docs/en/modules/admin/assets/images/settings_configuration_social.png deleted file mode 100644 index fb8c684802..0000000000 Binary files a/docs/en/modules/admin/assets/images/settings_configuration_social.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/settings_configuration_welcome.png b/docs/en/modules/admin/assets/images/settings_configuration_welcome.png deleted file mode 100644 index c72a0000b0..0000000000 Binary files a/docs/en/modules/admin/assets/images/settings_configuration_welcome.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_list.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_list.png new file mode 100644 index 0000000000..ef5c37b868 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_list.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_list_filter.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_list_filter.png new file mode 100644 index 0000000000..b5176de4c5 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_list_filter.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_menu.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_menu.png new file mode 100644 index 0000000000..c55652fd52 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_menu.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_duration.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_duration.png new file mode 100644 index 0000000000..d80dc795c9 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_duration.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_filters.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_filters.png new file mode 100644 index 0000000000..d0acaded72 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_filters.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_general_info.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_general_info.png new file mode 100644 index 0000000000..0afad7485c Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_general_info.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_images.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_images.png new file mode 100644 index 0000000000..67f4a1e5fe Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_images.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_metadata.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_metadata.png new file mode 100644 index 0000000000..dbca9bbe11 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_metadata.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_other.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_other.png new file mode 100644 index 0000000000..8b8983b083 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_other.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_visibility.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_visibility.png new file mode 100644 index 0000000000..1926290e29 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_new_form_visibility.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_types_edit_process.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_types_edit_process.png new file mode 100644 index 0000000000..1d5e6397de Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_types_edit_process.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_types_filter.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_types_filter.png new file mode 100644 index 0000000000..835f90f1de Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_types_filter.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_types_form.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_types_form.png new file mode 100644 index 0000000000..0697afbd00 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_types_form.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_types_list.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_types_list.png new file mode 100644 index 0000000000..ae1c91020a Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assemblies_types_list.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assembly_members.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assembly_members.png new file mode 100644 index 0000000000..82c8f9c9df Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assembly_members.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assembly_members_list.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assembly_members_list.png new file mode 100644 index 0000000000..3316b3c825 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assembly_members_list.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/assembly_members_new_form.png b/docs/en/modules/admin/assets/images/spaces/assemblies/assembly_members_new_form.png new file mode 100644 index 0000000000..29d5023ae3 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/assembly_members_new_form.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/assemblies/import_menu.png b/docs/en/modules/admin/assets/images/spaces/assemblies/import_menu.png new file mode 100644 index 0000000000..e9654047d3 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/assemblies/import_menu.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/import_menu.png b/docs/en/modules/admin/assets/images/spaces/processes/import_menu.png new file mode 100644 index 0000000000..b361dafc7d Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/import_menu.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/process-types-admin-backend.png b/docs/en/modules/admin/assets/images/spaces/processes/process-types-admin-backend.png deleted file mode 100644 index 03ef36090a..0000000000 Binary files a/docs/en/modules/admin/assets/images/spaces/processes/process-types-admin-backend.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/process-types-edit-process.png b/docs/en/modules/admin/assets/images/spaces/processes/process-types-edit-process.png deleted file mode 100644 index 614b8bb5e0..0000000000 Binary files a/docs/en/modules/admin/assets/images/spaces/processes/process-types-edit-process.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/process-types-front-end.png b/docs/en/modules/admin/assets/images/spaces/processes/process-types-front-end.png deleted file mode 100644 index 960b9a21e9..0000000000 Binary files a/docs/en/modules/admin/assets/images/spaces/processes/process-types-front-end.png and /dev/null differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/process_phases.png b/docs/en/modules/admin/assets/images/spaces/processes/process_phases.png new file mode 100644 index 0000000000..b20123d9b1 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/process_phases.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/process_phases_block.png b/docs/en/modules/admin/assets/images/spaces/processes/process_phases_block.png new file mode 100644 index 0000000000..cb722f73ce Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/process_phases_block.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/process_phases_list.png b/docs/en/modules/admin/assets/images/spaces/processes/process_phases_list.png new file mode 100644 index 0000000000..02ee76bf52 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/process_phases_list.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/process_phases_new_form.png b/docs/en/modules/admin/assets/images/spaces/processes/process_phases_new_form.png new file mode 100644 index 0000000000..f12917ada1 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/process_phases_new_form.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/process_types_edit_process.png b/docs/en/modules/admin/assets/images/spaces/processes/process_types_edit_process.png new file mode 100644 index 0000000000..4837891e08 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/process_types_edit_process.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/process_types_filter.png b/docs/en/modules/admin/assets/images/spaces/processes/process_types_filter.png new file mode 100644 index 0000000000..35f9e1aa82 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/process_types_filter.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/process_types_form.png b/docs/en/modules/admin/assets/images/spaces/processes/process_types_form.png new file mode 100644 index 0000000000..cbd2683631 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/process_types_form.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/process_types_list.png b/docs/en/modules/admin/assets/images/spaces/processes/process_types_list.png new file mode 100644 index 0000000000..c181530286 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/process_types_list.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group__barcelona_example.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group__barcelona_example.png new file mode 100644 index 0000000000..82dd904010 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group__barcelona_example.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group__cd44_example.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group__cd44_example.png new file mode 100644 index 0000000000..c3f1c86059 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group__cd44_example.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group_form_about.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_form_about.png new file mode 100644 index 0000000000..9403ee3eac Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_form_about.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group_form_metadata.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_form_metadata.png new file mode 100644 index 0000000000..8237c5a139 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_form_metadata.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group_form_visibility.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_form_visibility.png new file mode 100644 index 0000000000..b5ec51d194 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_form_visibility.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing.png new file mode 100644 index 0000000000..4ae114dc32 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_events.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_events.png new file mode 100644 index 0000000000..332cb05742 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_events.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_hero.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_hero.png new file mode 100644 index 0000000000..fb11b0d9a5 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_hero.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_html.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_html.png new file mode 100644 index 0000000000..e738d00ee0 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_html.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_metadata.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_metadata.png new file mode 100644 index 0000000000..1b97d712d7 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_metadata.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_processes.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_processes.png new file mode 100644 index 0000000000..933aec2673 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_processes.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_proposals.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_proposals.png new file mode 100644 index 0000000000..cb5c895e0a Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_proposals.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_stats.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_stats.png new file mode 100644 index 0000000000..43ae9beef3 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_stats.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_title.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_title.png new file mode 100644 index 0000000000..f1dc000175 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_landing_title.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_group_list.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_list.png new file mode 100644 index 0000000000..07b4feb0d1 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_group_list.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_list.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_list.png new file mode 100644 index 0000000000..20db763f5f Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_list.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_list_filter.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_list_filter.png new file mode 100644 index 0000000000..033ce6aa19 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_list_filter.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_menu.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_menu.png new file mode 100644 index 0000000000..6f5740e277 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_menu.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_duration.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_duration.png new file mode 100644 index 0000000000..8d65cadefa Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_duration.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_filters.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_filters.png new file mode 100644 index 0000000000..c466991e02 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_filters.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_general_info.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_general_info.png new file mode 100644 index 0000000000..e2f7db3bb0 Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_general_info.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_images.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_images.png new file mode 100644 index 0000000000..ee561426fa Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_images.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_metadata.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_metadata.png new file mode 100644 index 0000000000..647e82134e Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_metadata.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_related_processes.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_related_processes.png new file mode 100644 index 0000000000..729036590d Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_related_processes.png differ diff --git a/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_visibility.png b/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_visibility.png new file mode 100644 index 0000000000..48529f63ae Binary files /dev/null and b/docs/en/modules/admin/assets/images/spaces/processes/processes_new_form_visibility.png differ diff --git a/docs/en/modules/admin/assets/images/spaces_admin.png b/docs/en/modules/admin/assets/images/spaces_admin.png index 5c1bc5d6f0..4c8fc9e09d 100644 Binary files a/docs/en/modules/admin/assets/images/spaces_admin.png and b/docs/en/modules/admin/assets/images/spaces_admin.png differ diff --git a/docs/en/modules/admin/assets/images/spaces_visitor.png b/docs/en/modules/admin/assets/images/spaces_visitor.png index 7c1cd808e1..0f8907a919 100644 Binary files a/docs/en/modules/admin/assets/images/spaces_visitor.png and b/docs/en/modules/admin/assets/images/spaces_visitor.png differ diff --git a/docs/en/modules/admin/pages/appearance.adoc b/docs/en/modules/admin/pages/appearance.adoc deleted file mode 100644 index 6ecd34676d..0000000000 --- a/docs/en/modules/admin/pages/appearance.adoc +++ /dev/null @@ -1,81 +0,0 @@ -= Appearance - -In this page you can configure the look and feel of your Decidim instance. - -Please mind that this would be incompatible with some of the changes that your implementers could change in your general installation. For instance if there were changes in the xref:customize:styles.adoc[Styles] this could not work. - -image::admin_appearance.png[Decidim Admin Appearance] - ---- - -NOTE: This is a legacy setting that will be removed in the next version. https://github.com/decidim/decidim/pull/6575[See PR]. - -* **Show statistics**: whether you want to show or not the statistics sections in the homepage. - ---- - -* **Description**: What's the description of this site. Used for metatags for Google and Twitter embeds. Also used by the "SubHero" ContentBlock in the Homepage. - ---- - -NOTE: These area legacy settings that will be removed in the next version. https://github.com/decidim/decidim/pull/6284[See PR]. - -* **Call To Action button path**: You can overwrite where the Call To Action button in the homepage links to. Use partial paths, not full URLs here. Accepts letters, numbers, dashes and slashes, and must start with a letter. The Call To Action button is shown in the homepage between the welcome text and the description. Example: https://meta.decidim.org/conferences/decidimfest2020/ - -* **Call To Action button text**: You can overwrite the Call To Action button text in the homepage for each available language in your organization. If not set, the default value will be used. The Call To Action button is shown in the homepage between the welcome text and the description. - ---- - - -NOTE: This is a legacy setting that will be removed in the next version. There's no PR yet. - - -* **Highligted content banner** -** *Show the highlighted content banner* -** *Title* -** *Short description* -** *Action button title* -** *Action button subtitle* -** *Action button URL* -** *Image* - ---- - -* *Edit omnipresent banner* -** **Show omnipresent banner** -** **Title** -** **Short description** -** **URL** - ---- - -* **Edit layout appearance** - -This subsection defines the images for the layout that will be visible in almost all the pages. These are: - -** Icon -** Logo -** Official logo header -** Official logo footer -** Official organization URL - -// TODO: Add examples - ---- - -* **Organization colors**: What are the colors for your organization. Please notice that this could generate accessibility problems, for instance with people that doesn't have a good contrast notion. You can set -** Primary -** Secondary -** Success -** Warning -** Alert -** Highlight -** Highlight, alternative - -// TODO: Add examples - ---- - -* **Header snippets**: Use this field to add things to the HTML head. 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. - -// TODO: reference to HTML snippet setting diff --git a/docs/en/modules/admin/pages/areas.adoc b/docs/en/modules/admin/pages/areas.adoc deleted file mode 100644 index 6dc75aa56f..0000000000 --- a/docs/en/modules/admin/pages/areas.adoc +++ /dev/null @@ -1,11 +0,0 @@ -= Areas - -include::partial$deprecated.adoc[] - -Areas are all the sectors that an Organization can have. - -They are pretty similar to xref:admin:scopes.adoc[scopes], meaning that they are a way of allowing a better navigation and filtering in the spaces and components. - -We don't recommend using them, as probably in the future they will be removed. - -You can read more information about the history of Areas in this https://github.com/decidim/decidim/issues/3540#issuecomment-427324532[GitHub comment]. diff --git a/docs/en/modules/admin/pages/configuration.adoc b/docs/en/modules/admin/pages/configuration.adoc deleted file mode 100644 index eae6e6a6e3..0000000000 --- a/docs/en/modules/admin/pages/configuration.adoc +++ /dev/null @@ -1,53 +0,0 @@ -= Configuration - -In this page you can configure general settings from Decidim. - -image::admin_configuration.png[Decidim Admin Configuration] - -These are: - -* **Name**. Required. The name that the platform has. Visible at title, emails, etc. -* **Social**. Social handlers for different social networks. Visible at the footer in every page. This are: -** Twitter -** Facebook -** Instagram -** YouTube -** GitHub - -image::settings_configuration_social.png[Social networks configuration in Decidim] - -* **Default locale**. Required. -* **Time Zone**. Required. In which Time Zone is your organization. Used by things like calendars in Meetings. -* **Reference prefix**. Required. -* **Enable badges**. Whether you want or not that your participants have badges as a gamification mechanism, for instance for creating proposals or making comments. -* **Enable groups**. Whether you want or not that your participants have the possibility to create xref:participants/groups.adoc[User Groups]. Useful for example for associations or other collectives. -* **Enable rich text editor for participants**. Whether you want or not that your participants have the possibility to have a https://en.wikipedia.org/wiki/WYSIWYG[What You See Is What You Get (WYSIWYG) editor]. In some text areas, participants will be able to insert some HTML tags by using the rich text editor. -* **Send welcome notification**. Whether you want or not that your participants receive a notification when their first created their account. If enabled you can customize this notification. -** **Customize welcome notification**. -** **Welcome notification subject**. -** **Welcome notification body**. - -.Welcome notification -==== -Hi {\{name}}, thanks for joining {\{organization}} and welcome! - -If you want to get a quick idea of what you can do here, have a look at the Help section. -Once you have read it you will get your first badge. Here's a list of all the badges you can get as you participate in {\{organization}} - -Last but not least, join other people, share with them the experience of being engaged and participating in {\{organization}}. Make proposals, comments, debate, think about how to contribute to the common good, provide arguments to convince, listen and read to be convinced, express your ideas in a concrete and direct way, respond with patience and decision, defend your ideas and keep an open mind to collaborate and join other people's ideas. -==== - -image::settings_configuration_welcome.png[Welcome notification configuration in Decidim] - -* **Admin terms of use body**. Which message an Administrator user will see when accessing for the first time to the Administration panel. - -.Admin terms of use -==== -ADMIN TERMS OF USE - -We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things: - -* Respect the privacy of others. -* Think before you click. -* With great power comes great responsibility. -==== \ No newline at end of file diff --git a/docs/en/modules/admin/pages/help_sections.adoc b/docs/en/modules/admin/pages/help_sections.adoc deleted file mode 100644 index 9be6d5e3d7..0000000000 --- a/docs/en/modules/admin/pages/help_sections.adoc +++ /dev/null @@ -1,23 +0,0 @@ -= Help sections - -The first time a visitor goes to any Space page they will see an information box about what's this Space about. - -This is how the information box is shown to participants and visitors: - -image:help_sections_frontend.png[Help sections: frontend] - -They can hide this box by clicking in the close button [X]. This gets remembered by the application. They can open this box again by clicking in [Help: ?]. - -image:help_sections_frontend_hide.png[Help sections: hide] - -As this is something that depends on your given installation, an administrator can customize these *Help sections*, adapting them to your needs. - -image:help_sections_backend.png[Help sections: backend] - -== Disable - -You can disable these information boxes by leaving the contents all empty for every language: - -image:help_sections_disable_backend.png[Disable help section in admin] - -image:help_sections_disable_frontend.png[Disabled help section] \ No newline at end of file diff --git a/docs/en/modules/admin/pages/homepage.adoc b/docs/en/modules/admin/pages/homepage.adoc deleted file mode 100644 index 7dd3e7a32d..0000000000 --- a/docs/en/modules/admin/pages/homepage.adoc +++ /dev/null @@ -1,101 +0,0 @@ -= Homepage - -include::partial$under-construction.adoc[] - -You can control how it's the Homepage of your organization. To do so you have the Settings -> Homepage section through the Administration panel: - -image::admin_homepage.png[Decidim Admin Homepage] - ---- - -== How this works - -This means that every section in the Homepage is called **content block**. - -For instance, this is the *How to participate* content block: - -image::homepage_how_to_participate.png[How to participate example] - -For managing these contents you need to Drag and Drop the contents between the two columns, on the left are the Active and in the Right are the Inactive content blocks. - -As an example, here you can see how your page will look with only the *Hero image* content block: - -// TODO: add screenshot - -At the admin this is handled with: - -// TODO: add screenshot - -In your installation you could have other content blocks, as this depends on which modules you have active. Please contact your system administrator if you see something different here, like a missing content block. - -== Content blocks - -These are the different content blocks enabled with the official Decidim modules: - -=== Hero image - -image::homepage_hero_image_back.png[Hero image in Homepage backend content block] - -image::homepage_hero_image_front.png[Hero image in Homepage frontend content block] - -=== Sub hero banner - -Displays the description text of the instance. See xref:admin:appearance.adoc[Appearance]. - -image::homepage_sub_hero_banner.png[Sub hero banner in Homepage content block] - -=== Footer sub hero banner - -// TODO: I think this should be changed with an HTML text and probably removed - -image::homepage_footer_sub_hero_banner.png[Hero image in Homepage content block] - -=== How to participate - -// TODO: I think this should be changed with an HTML text and probably removed - -image::homepage_how_to_participate.png[How to participate in Homepage content block] - -=== Upcoming meetings - -image::homepage_upcoming_meetings.png[Upcoming meetings in Homepage content block] - -=== Last activity - -image::homepage_last_activity.png[Last activity in Homepage content block] - -=== HTML block - -image::homepage_html_block.png[HTML block in Homepage content block] - -=== Highlighted processes - -image::homepage_highlighted_processes.png[Highlighted processes in Homepage content block] - -=== Highlighted assemblies - -image::homepage_highlighted_assemblies.png[Highlighted assemblies in Homepage content block] - -=== Highlighted initiatives - -image::homepage_highlighted_initiatives.png[Highlighted initiatives in Homepage content block] - -=== Highlighted consultations - -image::homepage_highlighted_consultations.png[Highlighted consultations in Homepage content block] - -=== Highlighted conferences - -image::homepage_highlighted_conferences.png[Highlighted conferences in Homepage content block] - -=== Highlighted content banner - -image::homepage_highlighted_content_banner.png[Highlighted content banner in Homepage content block] - -=== Organization statistics - -image::homepage_organization_statistics.png[Organizations statistics in Homepage content block] - -=== Organization metrics - -image::homepage_organization_metrics.png[Organzation metrics in Homepage content block] diff --git a/docs/en/modules/admin/pages/scopes.adoc b/docs/en/modules/admin/pages/scopes.adoc deleted file mode 100644 index 8657bdbba0..0000000000 --- a/docs/en/modules/admin/pages/scopes.adoc +++ /dev/null @@ -1,105 +0,0 @@ -= Scopes - -Scopes are the set of territories or subjects that an Organization has. A scope may have child scopes. - -For instance, in the case of the city of Barcelona the scopes are its districts, and the children of a district are its neighborhoods. They can also have types, so it can be configured, for example, by thematic and also territorial scopes. - -Most of the components and spaces in Decidim allow you to configure Scopes in one way or another. There are mainly three ways of using Scopes: - -To configure Scope on the Decidim platform, go to menu:Settings[Scopes] in the admin sidebar menu. A list will appear with the existing scopes if there are any: - -image:scopes_list.png[Scopes list] - -If you need so, you need to first configure the Scope type. - -== Form - -image:scopes_types_new_form.png[New scope type form] - -.Admin New Scope Type form -|=== -|Field |Type |Description - -|Singular -|Required -|Name of the scope type in singular. - -|Plural -|Required -|Name of the scope type in plural. - -|=== - -image:scopes_new_form.png[New scope form] - -.Admin New Scope Form -|=== -|Field |Type |Description - -|Name -|Required -|Name of the scope. - -|Code -|Required -|(Internal) name of the scope. - -|Scope type -|Required -|Which type of scope it's. - -|=== - -== Actions - -You have 3 possible actions in this list after a Scope is created: - -|=== -|Icon |Name |Definition - -|image:action_browse.png[Browse icon] -|Browse -|See and configure the children scopes for this Scope. - -|image:action_edit.png[Edit icon] -|Edit -|Edit form for a Scope. It's the same form as "Create a new scope". - -|image:action_delete.png[Delete icon] -|Delete -|To delete this scope. - -|=== - -== Features -The main features related with scopes are: - -. Filtering -. User interests and Newsletters - -=== Filtering - -For filtering. Most of the spaces and components allows an administrator or a participant to associate them to a scope. This allows to filter by scopes when exploring them. - -image:scopes_filter_initiatives.png[Initiatives scopes filtering] - -image:scopes_filter_processes.png[Processes scopes filtering] - -Some examples: - -* With Accountability module, so it's possible to filter Results -* Assemblies and Processes can have Scopes. It's used for filtering multiple assemblies in the main listing page (/assemblies or /processes). These can be hidden by unchecking the "Enable participatory space filters" in the xref:admin:configuration.adoc[admin's configuration page]. -* Filtering in the sidebar is possible in Budgets Projects, Initiatives and Proposals. In some of these components you can control if these filters are shown with the "Scopes enabled" checkbox in the component settings. This will also enable or disable the scope selector in the resource creation form. - -You can also configure a participatory space so the filtering will only concern one scope and its children scopes. For example, let's imagine your organization have 3 different scopes for 3 cities, each of them having children scopes for the cities neighbourhoods. -On a participatory space which concerns only one of the cities, you will be able to select only this scope and its children so that users do not see the scopes of other cities in the filter options. - -=== User interests and Newsletters - -A Participant can choose which Scopes they want to follow in its account. - -image:account_my_interests.png[Account: my interests] - -This is used by the xref:admin:newsletters.adoc[Newsletters], in the "Select recipients to deliver" step, "Filter for users having activated any selected scope in their account's My Interests settings." section. - -image:newsletter_select_recipients.png[Newsletter: select recipients] diff --git a/docs/en/modules/admin/pages/settings.adoc b/docs/en/modules/admin/pages/settings.adoc new file mode 100644 index 0000000000..b568446122 --- /dev/null +++ b/docs/en/modules/admin/pages/settings.adoc @@ -0,0 +1,43 @@ += Settings + +== Understand the basics + +The settings tab allows you: + +* To start configuring your instance +* To enable general features across the instance +* To update the appearance of the homepage and the general look and feel of your instance +* To create and manage the scopes and areas +* To add user help information +* To configure the allowed external domains + +== Configuration + +To access the Settings configuration panel, go in the administration panel and click the "Settings" item in the administration +navigation bar. + +image::settings/settings_menu.png[Settings: Access settings panel] + +In the secondary navigation panel, you can see all the settings panel available: + +* xref:admin:settings/configuration.adoc[Configuration]: to configure general settings. +* xref:admin:settings/appearance.adoc[Appearance]: to configure the instance look and feel. +* xref:admin:settings/homepage.adoc[Homepage]: to configure what to display on the homepage. +* xref:admin:settings/scopes.adoc[Scopes]: to manage scopes, a categorization feature. +* xref:admin:settings/areas.adoc[Areas]: to manage areas, another categorization feature. +* xref:admin:settings/help_sections.adoc[Help sections]: to create and edit help texts for participants. +* xref:admin:settings/allowed_external_domains.adoc[Allowed external domains]: to manage authorized external domains. + +image::settings/settings_sidebar_menu.png[Settings sidebar menu] + +== Examples + +Thanks to this section, Decidim instances can have very different look and feel, with different colours, features, homepages, etc. + +image::settings/example_homepage_beta.png[Homepage screenshot of beta.try.decidim.org] + +image::settings/example_homepage_borgerkraft.png[Homepage screenshot of borgerkraft.no] + +image::settings/example_homepage_metadecidim.png[Homepage screenshot of meta.decidim.org] + +image::settings/example_homepage_barcelona.png[Homepage screenshot of decidim.barcelona] diff --git a/docs/en/modules/admin/pages/settings/allowed_external_domains.adoc b/docs/en/modules/admin/pages/settings/allowed_external_domains.adoc new file mode 100644 index 0000000000..a4cdc44017 --- /dev/null +++ b/docs/en/modules/admin/pages/settings/allowed_external_domains.adoc @@ -0,0 +1,20 @@ += Allowed external domains + +As means to protect against spam, and increase the security on your instance, Decidim can identify any links that direct +to an external webpage, and add the following alert pop-up after the user clicks it: + +image::settings/allowed_external_domains_pop-up.png[Pop-up that appears when clicking any external domains on Decidim] + +It warns participants that they're leaving your instance. + +== Allow an external domains + +There may be some websites redirection for which you don't want this feature enabled. +For example, if your site is deployed at a URL like `+decidim.example.org+` and you want every `+example.org+` URLs +to omit this alert message, you can configure this by adding your URL, and as many as you want, in the Allowed external domains page. + +To do so, click the "Add to allowed list" button and enter the website URL you want to authorize. + +image::settings/allowed_external_domains_admin_panel.png[Allowed external domains panel] + +When clicking on a URL to those domains, participants won't see the alert message. diff --git a/docs/en/modules/admin/pages/settings/appearance.adoc b/docs/en/modules/admin/pages/settings/appearance.adoc new file mode 100644 index 0000000000..2496778385 --- /dev/null +++ b/docs/en/modules/admin/pages/settings/appearance.adoc @@ -0,0 +1,175 @@ += Appearance + +In this page you can configure the look and feel of your Decidim instance. + +NOTE: Please mind that this would be incompatible with some of the changes that your implementers could make in your general installation. +For instance if there were changes in the xref:customize:styles.adoc[Styles] some parameters couldn't be applied as expected. + +== Edit homepage appearance + +This section allows to provide a general description about the instance, and to configure a call to action button that can be +shown to participants on the homepage to encourage them to go to a specific process, like a proposal component where they can participate. + +image::settings/admin_appearance_homepage_appearance.png[Decidim Admin Appearance edit homepage appearance toggle] + +.Edit Homepage appearance toggle form + +|=== +|Field |Type |Description |Visibility + +|Description +|Optional +|The description of this instance, used for meta tags for Google and Twitter embeds. +|Visible in the footer and in the "Sub hero banner" content block in homepage if this block is enabled. + +|Call To Action button path +|Optional +|Path to the place on the platform when you want to quickly redirect participants. +|Visible in the "Hero image and CTA" content block in homepage if this block is enabled. + +|Call To Action button text +|Optional +|Text displayed on the CTA button. +|Visible in the "Hero image and CTA" content block in homepage if this block is enabled. + +|=== + +NOTE: To understand how to enable the different homepage blocks, go to the xref:admin:settings/homepage.adoc[homepage] article. + +== Highlighted content banner + +This section allows to enable and give a description and CTA button to a banner, for example to highlight a specific space +on your instance, to encourage users to create an account or to register to a meeting. You can make it evolve depending on the +actuality of your instance, and deactivate it when it's not needed. + +NOTE: To appear on the homepage, the "Highlighted content banner" content block needs to be enabled on the xref:admin:settings/homepage.adoc[homepage]. + +image::settings/admin_appearance_highlighted_banner.png[Decidim Admin Appearance edit Highlighted content banner toggle] + +.Edit Highlighted content banner toggle form + +|=== +|Field |Type |Description + +|Show the highlighted content banner +|Checkbox +|When checked, the highlighted content banner appears on the homepage if the "Highlighted content banner" content block is also enabled. + +|Title +|Required +|The title of the banner. + +|Short description +|Required +|The description for the banner. + +|Action button title +|Required +|The text displayed in the banner CTA. + +|Action button subtitle +|Optional +|An optional subtitle displayed in your CTA. + +|Action button URL +|Required +|The URL where the CTA button redirects. + +|Image +|Optional +|The background image for the banner. + +|=== + +== Edit omnipresent banner + +This section allows to enable a banner at the top of your instance, above the headers, visible at any time from every page. +It can be useful to display very important information that all participants need to see, like announcing a maintenance date, +availability of a process results, an important notice, etc. + +NOTE: This banner is configured on this page only, and doesn't need to be enabled in the homepage section. + +image::settings/admin_appearance_omnipresent_banner.png[Decidim Admin Appearance edit omnipresent banner toggle] + +.Edit Highlighted content banner toggle form + +|=== +|Field |Type |Description + +|Show omnipresent banner +|Checkbox +|When checked, the omnipresent banner appears at the top of each page of the platform, above the headers. + +|Title +|Required +|The title of the banner. + +|Short description +|Required +|The description for the banner. + +|URL +|Required +|The URL where the banner redirects. + +|=== + +image::settings/appearance_omnipresent_banner.png[Decidim Appearance omnipresent banner frontend] + +== Edit layout appearance + +This section allows to download logos and icons, to be displayed in the header and footer, notification emails, newsletters, etc. + +image::settings/admin_appearance_layout.png[Decidim Admin layout appearance toggle] + +.Edit layout appearance toggle + +|=== +|Field |Type |Description + +|Icon +|Download +|Displayed as a "favicon" in the browser tabs of the instance. + +|Logo +|Download +|Displayed in the header of the instance, and the header of the newsletter and notification emails. + +|Official logo footer +|Download +|Displayed in the footer of the instance, and redirects to the official organization URL. + +|Official organization URL +|Optional +|The URL where the official logo footer redirects. + +|=== + +image::settings/appearance_layout_footer_logo.png[Decidim Appearance official footer logo] + +== Organization colors + +This section allows to choose colors for the organization. + +NOTE: Be aware of potential accessibility issues, for instance with people that doesn't have a good contrast notion. +You can check the contrast of your choosing with WebAIM Contrast Checker or other similar tools. + +image::settings/admin_appearance_colors.png[Decidim Admin layout appearance toggle] + +You can configure: + +* Primary color: Used for global menu background, components menu backgrounds, etc. +* Secondary color: Used for titles links, primary buttons, header font color, etc. +* Tertiary color: Used for titles underlines, card border color, etc. + +In the following screenshot, the three different colors are displayed. + +image::settings/appearance_colors.png[Decidim layout appearance colors example] + +== Header snippets + +NOTE: You might not see this field. For more information on how to enable it, see the xref:customize:styles.adoc[Styles] documentation. + +This field allows to add code to the HTML head. 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 is only rendered in public pages, not in the administration. \ No newline at end of file diff --git a/docs/en/modules/admin/pages/settings/areas.adoc b/docs/en/modules/admin/pages/settings/areas.adoc new file mode 100644 index 0000000000..4bd5f94db7 --- /dev/null +++ b/docs/en/modules/admin/pages/settings/areas.adoc @@ -0,0 +1,11 @@ += Areas + +include::partial$deprecated.adoc[] + +Areas are all the sectors that an organization can have. + +Areas re pretty similar to xref:admin:settings/scopes.adoc[scopes], meaning that they're a way of allowing a +better navigation and filtering in the spaces and components. + +You can read more information about the history of Areas in +this https://github.com/decidim/decidim/issues/3540#issuecomment-427324532[GitHub comment]. diff --git a/docs/en/modules/admin/pages/settings/configuration.adoc b/docs/en/modules/admin/pages/settings/configuration.adoc new file mode 100644 index 0000000000..c0ecc26fdb --- /dev/null +++ b/docs/en/modules/admin/pages/settings/configuration.adoc @@ -0,0 +1,104 @@ += Configuration + +In this page you can configure general settings from Decidim, such as the name of the instance, the welcome notification, the +general features, the languages available, etc. + +== Configurations available + +image::settings/admin_configuration.png[Decidim Admin Configuration] + +[cols="20h,10h,~,~"] +|=== +|Field |Type |Description |Visibility + +|Name +|Required +|The name of the platform. +|Visible in platform title, emails, notifications, etc. + +|Social +|Required +|Social handlers for different social networks. In the field, only add the necessary slug instead of the whole URL. +|Visible in the footer, in every page. + +|Default locale +|Required +|Default language for the platform. If you want to enable more languages, ask your technical administrator. +|If multiple languages, participants can choose their preferred one in their account settings. + +|Time Zone +|Required +|In which Time Zone is your organization. +|Used in multiple places, like meetings calendar. + +|Reference prefix +|Required +|Reference prefix used to publicly identify all the instance resources. +|Visible in every resource page, like an assembly, meeting, proposal, etc. + +|Enable badges +|Checkbox +|Whether you want or not that your participants have badges as a gamification mechanism when participating. +|If enabled, badges are visible in the participants profiles, and participation triggers badges level completion. + +|Enable groups +|Checkbox +|Whether you want or not that your participants have the possibility to create xref:participants/groups.adoc[user groups]. +|If enabled, groups are visible in the participants profiles and accounts, and they can create user groups. + +|Enable participatory space filters +|Checkbox +|Whether you want or not to display filters in the participatory spaces index pages. +|If enabled, participants are able to filter spaces, like assemblies, by different filters on the space index. + +|Comments max length +|Required +|Whether you want or not to limit the number of character in comments. Leave 0 for default value (1000). +|Limit visible if you enable comments in a participatory component. + +|Enable rich text editor for participants +|Checkbox +|Whether you want or not to enable participants to have a https://en.wikipedia.org/wiki/WYSIWYG[WYSIWYG editor]. +|In some text areas, like proposal creation, participants are able to insert some HTML tags by using the rich text editor. + +|Send welcome notification +|Checkbox +|Whether you want or not that participants receive a notification when they first create their account. +|If you just enable this, participants receive the default notification. + +|Customize welcome notification +|Checkbox +|Enable you to customize the notification sent to participant when they create an account. +|If enabled you can customize the welcome notification in the fields below. + +|Welcome notification subject +|Required +|Enable you to customize the welcome notification subject. You can add variables, such as {{name}} or {{organization}}. +|Field visible if you enable the "Customize welcome notification" checkbox. + +|Welcome notification body +|Required +|Enable you to customize the welcome notification body. You can add variables, such as {{name}} or {{organization}}. +|Field visible if you enable the "Customize welcome notification" checkbox. + +|Body for the administrator terms of service +|Required +|Which message an administrator sees when accessing for the first time to the Administration panel. +|Message displayed when an administrator access the administration panel for the first time. + +|=== + +== Examples + +=== Social networks + +If you enter a value for each social network, their icons are displayed in the footer with a link to your account page. +Check that all the links are working well. + +image::settings/settings_configuration_social.png[Social networks configuration in Decidim] + +=== Welcome notification + +Participants receive welcome notification when they finalize the creation of their account, on their notification panel and by email. + +image::settings/settings_configuration_welcome.png[Welcome notification configuration in Decidim] \ No newline at end of file diff --git a/docs/en/modules/admin/pages/settings/help_sections.adoc b/docs/en/modules/admin/pages/settings/help_sections.adoc new file mode 100644 index 0000000000..ca57fd68b2 --- /dev/null +++ b/docs/en/modules/admin/pages/settings/help_sections.adoc @@ -0,0 +1,19 @@ += Help sections + +On each participatory space index and landing page, you can see a "Help" button on the right border of the page. + +image::settings/help_sections_frontend_hide.png[Help sections: hide] + +By clicking on it, a visitor or a participant can see a pop up message to understand what the participatory space is about. + +image::settings/help_sections_frontend.png[Help sections: frontend] + +Administrators can customize these *help sections* to adapt them to the instance specificity. + +image::settings/help_sections_backend.png[Help sections: backend] + +== Disable + +You can hide these information boxes by leaving the contents all empty for every language. + +image::settings/help_sections_disable_backend.png[Disable help section in administration] diff --git a/docs/en/modules/admin/pages/settings/homepage.adoc b/docs/en/modules/admin/pages/settings/homepage.adoc new file mode 100644 index 0000000000..92352ce49c --- /dev/null +++ b/docs/en/modules/admin/pages/settings/homepage.adoc @@ -0,0 +1,161 @@ += Homepage + +In this page you can configure your instance homepage, by enabling different content blocks, that you can organize as you want +by dragging and dropping them in the two columns. + +. Add different content blocks by clicking the "Add content block" button, and choose the one you want to add. +. Configure the content block (if configurable) while it's in the inactive content blocks columns +. Finally, move the content block in the active content blocks column to make it appear on the homepage + +image::settings/admin_homepage.png[Decidim Admin Homepage] + +NOTE: In your installation you could have other content blocks, as this depends on which modules you have active. +Please contact your system administrator if you see something different here, like a missing content block. + +Below, you'll find all the content blocks configuration guides and screenshots of how there are displayed on the homepage. + +== Homepage content blocks + +These are the different content blocks enabled with the official Decidim modules. + +=== Hero image and CTA + +The hero image and CTA content block allows to display: + +* *a welcome text*: to welcome the participants, or to advertise a new process for example. +* *a call to action button*: by default, a "Participate" button redirecting to the participatory processes index. +Can be customized in xref:admin:appearance.adoc#_edit_homepage_appearance[Appearance] thanks to the Call To Action button fields. +* *an image*: the downloaded image is displayed with an opacity filter, to make sure the welcome text is readable. + +image::settings/homepage_hero_image_back.png[Hero image in Homepage backend content block] + +In the screenshot below, the CTA button has been personalized in the in xref:admin:appearance.adoc#_edit_homepage_appearance[Appearance] section. + +image::settings/homepage_hero_image_front.png[Hero image in Homepage frontend content block] + +=== Global menu + +The global menu content block displays a navigation menu on the homepage with all the participatory spaces types that you +created on your instance. + +image::settings/homepage_global_menu.png[Global menu in Homepage frontend content block] + +=== Sub hero banner + +The sub hero banner content block displays the description text of the instance +configured in xref:admin:appearance.adoc#_edit_homepage_appearance[Appearance]. + +image::settings/homepage_sub_hero_banner.png[Sub hero banner in Homepage content block] + +=== Highlighted content banner + +The highlighted content banner content block displays the banner configured in +xref:admin:settings/appearance.adoc#_highlighted_content_banner[Appearance]. + +image::settings/homepage_highlighted_content_banner.png[Highlighted content banner in Homepage content block] + +=== Footer sub hero banner + +The footer sub hero banner content block displays a default text that can't be configured. +Move it to inactive or delete it if you don't want it to be displayed on the homepage. + +image::settings/homepage_footer_sub_hero_banner.png[Hero image in Homepage content block] + +=== How to participate + +The how to participate content block displays a default text that can't be configured, and a button redirecting participants to +the help xref:admin:pages.adoc[pages]. + +image::settings/homepage_how_to_participate.png[How to participate in Homepage content block] + +=== Upcoming meetings + +The upcoming meetings content block displays: + +* a list of upcoming meetings: published and visible incoming meetings appear as a list. +* a map: upcoming meetings are displayed as pins on the map when they have an address. +* a calendar: the calendar shows in grey the current date, and in the secondary color the date of the next meeting of the month. +* a link to see all meetings: this link redirects to the instance meeting page, also accessible via the "Meetings" button in the header. + +image::settings/homepage_upcoming_meetings.png[Upcoming meetings in Homepage content block] + +=== Last activity + +The last activity content block displays a list of the contents participants and administrators published in the last days. +Participants can see: + +* the publication date +* the content title +* the content type: comment, meeting, proposal, blog post, etc. +* the space or content where it was published +* the user who published it + +image::settings/homepage_last_activity.png[Last activity in Homepage content block] + +=== Highlighted processes + +The highlighted processes content block displays a grid of participatory processes on the homepage. +You can configure the maximum of processes to display by clicking the "Edit" button on the content block (6, 9, or 10). + +image::settings/homepage_highlighted_processes.png[Highlighted processes in Homepage content block] + +=== Highlighted assemblies + +The highlighted assemblies content block displays a grid of assemblies on the homepage. +You can configure the maximum of assemblies to display by clicking the "Edit" button on the content block (6, 9, or 10). + +image::settings/homepage_highlighted_assemblies.png[Highlighted assemblies in Homepage content block] + +=== Highlighted conferences + +The highlighted conferences content block displays a grid of conferences on the homepage. +You can configure the maximum of conferences to display by clicking the "Edit" button on the content block (6, 9, or 10). + +image::settings/homepage_highlighted_conferences.png[Highlighted conferences in Homepage content block] + +=== Highlighted initiatives + +The highlighted processes content block displays a grid of participatory processes on the homepage. +You can configure the maximum of processes to display by clicking the "Edit" button on the content block (6, 9, or 10). +You can also choose if you want to display initiatives by least or more recent ones. + +image::settings/homepage_highlighted_initiatives.png[Highlighted initiatives in Homepage content block] + +=== Organization statistics + +The organization statistics content block displays statistics about the participation on your instance, such as the number of +participants, proposals, meetings, etc. + +image::settings/homepage_organization_statistics.png[Organizations statistics in Homepage content block] + +=== Organization metrics + +The organization metrics content block displays the evolution of the participation on your instance. + +NOTE: Looking for how to enable this feature technically? Go to xref:develop:metrics.adoc[Metrics in Developers guide] + +image::settings/homepage_organization_metrics.png[Organization metrics in Homepage content block] + +=== HTML block + +The HTML block content block allows to add an editable HTML block on the homepage, and therefore to create a personalized section. + +image::settings/homepage_html_block.png[HTML block in Homepage content block] + +Here are some examples of how some organizations personalize their homepage with this content block. + +image::settings/homepage_html_block_barcelona.png[HTML block in Homepage content block Barcelona example] + +Homepage HTML block of the platform of the city of Barcelona in Spain (www.decidim.barcelona). + +image::settings/homepage_html_block_nyc.png[HTML block in Homepage content block NYC example] + +Homepage HTML block of the platform of New York City in USA (www.participate.nyc.gov). + +image::settings/homepage_html_block_kakogawa.png[HTML block in Homepage content block Kakogawa example] + +Homepage HTML block of the platform of the city of Kakogawa in Japan (kakogawa.diycities.jp). + +image::settings/homepage_html_block_lausanne.png[HTML block in Homepage content block Lausanne example] + +Homepage HTML block of the platform of the city of Lausanne in Switzerland (participer.lausanne.ch). \ No newline at end of file diff --git a/docs/en/modules/admin/pages/settings/scopes.adoc b/docs/en/modules/admin/pages/settings/scopes.adoc new file mode 100644 index 0000000000..e147b8f7a0 --- /dev/null +++ b/docs/en/modules/admin/pages/settings/scopes.adoc @@ -0,0 +1,108 @@ += Scopes + +Scopes are the set of territories or subjects that an Organization has. A scope may have child scopes. + +For instance, in the case of the city of Barcelona the scopes correspond to its districts, and the children of a +district are its neighborhoods. +They can also have types, so it can be configured, for example, by thematic and also territorial scopes. + +Most of the components and spaces in Decidim allow you to configure Scopes in one way or another. + +image::settings/scopes_list.png[Scopes list] + +== Create a scope type + +To create a scope type, click the "Add" button in the Scope types tab. + +image::settings/scopes_types_new_form.png[New scope type form] + +.Admin new scope type form +|=== +|Field |Type |Description + +|Name +|Required +|Name of the scope type in singular. + +|Plural +|Required +|Name of the scope type in plural. + +|=== + +== Create a scope + +To create a scope, click the "Add" button in the Scope tab. + +image::settings/scopes_new_form.png[New scope form] + +.Admin new scope form +|=== +|Field |Type |Description + +|Name +|Required +|Name of the scope. + +|Code +|Required +|Internal identifier of the scope. + +|Scope type +|Optional +|Which type of scope it's related to. It can be blank. + +|=== + +== Actions + +|=== +|Icon |Name |Definition + +|image:icons/action_browse.png[Browse icon] +|Browse +|See and configure the children scopes for this Scope. + +|image:icons/action_edit.png[Edit icon] +|Edit +|Edit form for a Scope. + +|image:icons/action_delete.png[Delete icon] +|Delete +|To delete this scope. + +|=== + +== Features +The main features related with scopes are: + +. Filtering +. User interests and Newsletters + +=== Filtering + +Most of the spaces and components allows an administrator or a participant to associate them to a scope. +This allows to filter by scopes when exploring them. + +image::settings/scopes_filter_assemblies.png[Assemblies scopes filtering] + +image::settings/scopes_filter_processes.png[Processes scopes filtering] + +Some examples: + +* With Accountability module, so it's possible to filter Results +* Assemblies and Processes can have Scopes. It's used for filtering multiple assemblies in the main listing page (/assemblies or /processes). These can be hidden with the "Enable participatory space filters" in the xref:admin:settings/configuration.adoc[configuration]. +* Filtering in the sidebar is also available in some components, where you can control if these filters are shown with the "Scopes enabled" checkbox in the settings. It also enables the scope selector in the resource creation form. + +You can also configure a participatory space so the filtering only concerns one scope and its children scopes. For example, let's imagine your organization have 3 different scopes for 3 cities, each of them having children scopes for the cities neighbourhoods. +On a participatory space which concerns only one of the cities, you are able to select only this scope and its children so that users do not see the scopes of other cities in the filter options. + +=== User interests and newsletters + +A participant can choose which scopes they want to follow in its account. + +image::settings/account_my_interests.png[Account: my interests] + +This is used in the xref:admin:newsletters.adoc[Newsletters], in the "Select recipients to deliver" step. + +image::newsletter_select_recipients.png[Newsletter: select recipients] diff --git a/docs/en/modules/admin/pages/spaces.adoc b/docs/en/modules/admin/pages/spaces.adoc index b935b16390..c55051affd 100644 --- a/docs/en/modules/admin/pages/spaces.adoc +++ b/docs/en/modules/admin/pages/spaces.adoc @@ -1,12 +1,41 @@ = Spaces -The participatory spaces are the channels that citizens can participate through when public decisions are being taken. By default -the platform is provided with participatory processes, initiatives, consultations, conferences, votings and assemblies, but -any organization can develop its own mechanisms through xref:develop:modules.adoc[Modules]. +== Understand the basics -They are accessible through the main sidebar in the administration panel, and also through the main navigation menu in the -public interface. +Participatory spaces are the channels through which citizens can take part in public decision-making. +By default, an instance is provided with those different spaces: -image:spaces_admin.png[Spaces in admin sidebar] +.Participatory spaces +|=== +|Name |Description |Use cases -image:spaces_visitor.png[Spaces visible in the public interface] +|*xref:admin:spaces/processes.adoc[Participatory Processes]* +|A participatory process allows administrators to configure different participatory components, which evolve over different participatory phases. +|Participatory budgeting, Proposal recollection, Voting or debate process, etc. + +|*xref:admin:spaces/assemblies.adoc[Assemblies]* +|An assembly allows administrator to configure participatory components in a continued space, with the possibility to define members. +|Committee organization space, citizen assembly, etc. + +|*xref:admin:spaces/initiatives.adoc[Initiatives]* +|Initiatives space allows administrators to open a bottom-up space, with different initiatives types. +|Petitions, Hearing requests, Participatory process requests, etc. + +|*xref:admin:spaces/conferences.adoc[Conferences]* +|A conference allows administrators to organize and publicize events, deal with registrations, program , speakers and venues. +|Participatory event, Citizen assembly, Association festival, etc. + +|=== + +NOTE: Any organization can develop its own spaces by creating xref:develop:modules.adoc[Modules]. + +== Configuration + +Spaces are accessible through the administration navigation bar. + +image::spaces_admin.png[Spaces in administrator sidebar] + +Once you start publishing spaces, participants see links to the different spaces indexes appear in the homepage global menu, +the instance navigation bar and the footer. + +image::spaces_visitor.png[Spaces visible in the public interface] diff --git a/docs/en/modules/admin/pages/spaces/assemblies.adoc b/docs/en/modules/admin/pages/spaces/assemblies.adoc index 6d1e1a6f02..b2af45102e 100644 --- a/docs/en/modules/admin/pages/spaces/assemblies.adoc +++ b/docs/en/modules/admin/pages/spaces/assemblies.adoc @@ -1,308 +1,115 @@ = Assemblies +== Understand the basics + An assembly is a group of members of an organization who meet periodically to make decisions about a specific area or scope of the organization. -Assemblies hold meetings, some are private and some are open. If they are open, it is possible to participate in them -(for example: attending if the capacity allows it, adding points to the agenda, or commenting on the proposals and decisions taken by this organ). +Assemblies can hold meetings, consult their members, can be private or open to everyone. -Examples: A general assembly (which meets once a year to define the organisation's main lines of action as well as its -executive bodies by vote), an equality advisory council (which meets every two months to make proposals on how to improve -gender relations in the organisation), an evaluation commission (which meets every month to monitor a process) or a guarantee -body (which collects incidents, abuses or proposals to improve decision-making procedures) are all examples of assemblies. +Examples of assemblies are: a general assembly meeting once a year to define the organisation's main lines of action as well as its +executive bodies by vote, an equality advisory council meeting regularly to make proposals on how to improve +gender relations in the organisation, an evaluation commission meeting every month to monitor a process, or a guarantee +body collecting incidents, abuses, or proposals to improve decision-making procedures. -The main difference between xref:admin:spaces/processes.adoc[participatory processes] and assemblies is that assemblies don't +NOTE: The main difference between xref:admin:spaces/processes.adoc[participatory processes] and assemblies is that assemblies don't have phases, meaning that they don't have timelines. -You can see a real world usage of assemblies in https://www.decidim.barcelona/assemblies[Decidim Barcelona], where you -can see the different Participation Organs, that are the regular spaces where the City Council meets with citizens and organizations -to get feedback. - -In this section, we'll explain how we can configure an Assembly in Decidim. - -== List - -To configure assemblies on the Decidim platform, click on btn:[Assemblies] in the admin sidebar menu. A list -will appear with the existing assemblies if there are any: - -image:assemblies_list.png[Assemblies list] - -You can filter by the ones that are: - -* Published / Unpublished -* Public / Private - -image:assemblies_list_filter.png[Assemblies list filtered] - -You can also search by title and control how many elements are in the list. +In this documentation section, you can find how to configure and manage all of those items: -You have 4 possible actions in this list after an Assembly is created: +* xref:admin:spaces/assemblies/types.adoc[Assembly types] +* xref:admin:spaces/assemblies/assembly_creation.adoc[Assembly creation] +* xref:admin:spaces/assemblies/components.adoc[Components] +* xref:admin:spaces/assemblies/categories.adoc[Categories] +* xref:admin:spaces/assemblies/attachments.adoc[Attachments] +* xref:admin:spaces/assemblies/members.adoc[Members] +* xref:admin:spaces/assemblies/admins.adoc[Assembly admins] +* xref:admin:spaces/assemblies/private_participants.adoc[Private participants] +* xref:admin:spaces/assemblies/moderations.adoc[Moderations] -. Export: send by email the configuration for a given assembly. Can be imported in other Decidim installation. -. Duplicate: to duplicate this assembly. -. Configure: to edit the metadata and configuration for a assembly. -. Assemblies: to manage all the children assemblies for a assembly. -. Preview: how it will look once published. +== How to find it? -== New assembly form +To access the Assemblies panel, go in the administration panel and click the "Assemblies" item in the administration +navigation bar. -image:assemblies_new_form.png[New assembly form] +image::spaces/assemblies/assemblies_menu.png[Pages: Access assemblies panel] -.New assembly form: General information -|=== -|Field |Type |Description - -|Title -|Required -|Title of the assembly. For instance, "General Committee". - -|Subtitle -|Required -|Subtitle. For instance, "Let's decide our priorities together" - -|Order position -|Required -|Which order will it have in relation with the other assemblies. Having a lower number means a higher priority. For instance, -if you have two assemblies, "Assembly a" with weight "10" and "Assembly b" with weight "0", then "Assembly b" will be first when ordering. - -|URL slug -|Required -|URL slugs are used to generate the URLs that point to this assembly. Only accepts letters, numbers and dashes, and must -start with a letter. Example: if your domain is 'example.org' and your slug 'general-committee' then your URL will -be https://example.org/assemblies/general-committee +There, you are able to manage assemblies and assemblies types. -|Hashtag -|Optional -|Hashtag for Twitter +== Manage assemblies -|Short description -|Required -|A short explanation of what's your participatory process about. +image::spaces/assemblies/assemblies_list.png[Assemblies list] -|Description -|Required -|A long explanation of what's your assembly about. +On this page, you are able to manage assemblies and xref:admin:spaces/processes/groups.adoc[assemblies types]. +You can find all the assemblies on the list in the administration panel, with: -|Purpose of action -|Optional -|Internal field that doesn't get shown publicly. To be removed in a future version. +* *Title*: title of the assembly. +* *Created at*: date of creation of the assembly. +* *Private*: if the assembly is opened to all participants or to only certain participants. +* *Published*: if the assembly is published or no. -|Composition -|Optional -|Internal field that doesn't get shown publicly. To be removed in a future version. +You can filter and sort this list by clicking the "Filter" button and the columns headers. +You can also search for assemblies by their title in the search bar. -|Internal organisation -|Optional -|Internal field that doesn't get shown publicly. To be removed in a future version. +image::spaces/assemblies/assemblies_list_filter.png[Assemblies list filtered] -|Announcement -|Optional -|The text you enter here will be shown to the user right below the assembly information. +== Actions |=== +|Icon |Name |Definition -.New assembly form: Duration -|=== -|Field |Type |Description +|image:icons/action_edit.png[Configure assembly icon] +|Configure +|To edit the configuration and components for an assembly. -|Date created -|Optional -|Information that's displayed in the assembly metadata sidebar. Expected format: dd/mm/yyyy +|image:icons/action_assemblies.png[Children assemblies icon] +|Assemblies +|To manage all the children assemblies for an assembly. -|Included at -|Optional -|Information that's displayed in the assembly metadata sidebar. The date when this assembly was added to Decidim. It does -not necessarily have to be the same as the creation date. Expected format: dd/mm/yyyy +|image:icons/action_duplicate.png[Duplicate assembly icon] +|Duplicate +|To duplicate this assembly. -|Duration -|Optional -|Information that's displayed in the assembly metadata sidebar. If the duration of this assembly is limited, select the -end date. Otherwise, it will appear as indefinite. Expected format: dd/mm/yyyy +|image:icons/action_export.png[Export assembly icon] +|Export all +|Send the assembly configuration JSON file by email. Then it can be imported in other Decidim installation. -|Closing date -|Optional -|Information that's displayed in the assembly metadata sidebar. When this assembly closed. Expected format: dd/mm/yyyy +|image:icons/action_preview.png[Preview assembly icon] +|Preview +|Preview of how the assembly looks in the user interface. -|Closing date reason -|Optional -|Information that's displayed in the assembly metadata sidebar. Why this assembly closed. +|image:icons/action_moderate.png[Moderate assembly icon] +|Moderate +|To access the assembly moderation panel. |=== -.New assembly form: Images -|=== -|Field |Type |Description +You can also click the "Manage" button at the top right of the page, to be able to import a process or +configure Assemblies Types. -|Home image -|Optional -|Image that will be used in presentation cards of this assembly. Guidance for file: Has to be an image or a document. -For images, use preferably landscape images that does not have any text, the service crops the image. Maximum file size: 10MB -Allowed file extensions: jpeg jpg png +=== Import an assembly -|Banner image -|Optional -|Image that will be used inside of the assembly. Guidance for file: Has to be an image or a document. -For images, use preferably landscape images that does not have any text, the service crops the image. Maximum file size: 10MB -Allowed file extensions: jpeg jpg png +To import an assembly, click the "Manage" button at the top right of the page. -|=== +image::spaces/assemblies/import_menu.png[Assemblies import menu] -.New assembly form: Filters -|=== -|Field |Type |Description - -|Scopes enabled -|Optional -|Check if you want to have Scopes filtering in this assembly. - -|Scope -|Optional -|Which xref:admin:scopes.adoc[Scope] does this assembly belongs to. - -|Area -|Optional -|Which xref:admin:areas.adoc[Area] does this assembly belongs to. - -|=== - -.New assembly form: Metadata -|=== -|Field |Type |Description - -|What is decided -|Optional -|Information that's displayed in the assembly metadata sidebar. - -|How is it decided -|Optional -|Information that's displayed in the assembly metadata sidebar. - -|Scope metadata -|Optional -|Information that's displayed in the assembly metadata sidebar. - -|Promoter group -|Optional -|Information that's displayed in the assembly metadata sidebar. - -|Organization area -|Optional -|Information that's displayed in the assembly metadata sidebar. - -|Who participates -|Optional -|Information that's displayed in the assembly metadata sidebar. - -|=== - -.New assembly form: Visibility -|=== -|Field |Type |Description +You are redirected to the import page, where you need to fill in those fields: -|Parent assembly -|Optional -|What is the assembly that this assembly belongs to. For instance in Metadecidim, the https://meta.decidim.org/assemblies/coordination-committee[Coordination Committee] -has the parent assembly of the https://meta.decidim.org/assemblies/general-assembly-association[General%20Assembly%20of%20the%20Decidim%20Association]. +* Title : The title you wish to give to the assembly. +* URL identifier: The ‘slug’ for the assembly. +* Add a document: Here you need to load the assembly JSON file obtained by email when exporting. -|Highlighted -|Optional -|Check if you want the assembly to have more visibility in the Assemblies public list. It'll also be visible in the -Assembly Content Block in the xref:admin:homepage.adoc[Homepage] configuration. - -|Private space -|Optional -|Check if this assembly should only be accessible by xref:admin:spaces/assemblies/private_participants.adoc[Private Participants] - -|Is transparent -|Optional -|Check if this assembly is private but should be visible to all the rest of participants. This means that other participants -or visitors will see it but they won't be able to interact with it. - -|=== - -.New assembly form: Other -|=== -|Field |Type |Description - -|Created by -|Optional -|Choose one of "City Council", "Public" or "Other". If it's Other, you can specify the name of the organization that created -this assembly. - -|Assembly type -|Optional -|Which xref:_assemblies_types[assembly type] is this assembly. - -|Related processes -|Optional -|Select other participatory processes that are related to this assembly. - -|Social -|Optional -|Which social networks profile does this assembly has. Can be Twitter, Facebook, Instagram, YouTube and/or GitHub. It's -displayed in the assembly metadata sidebar. - -|Show statistics -|Optional -|Check if you want to show the Statistics section. - -|=== - -After you've initially created your assembly you have a submenu where you need to keep configuring more information -about your assembly. - -image:assembly_submenu.png[Assembly submenu in admin] - -Here you can keep configuring your process: - -. Info: the same form that we explained in this page. -. xref:admin:spaces/assemblies/components.adoc[Components] -. xref:admin:spaces/assemblies/categories.adoc[Categories] -. xref:admin:spaces/assemblies/attachments.adoc[Attachments] -. xref:admin:spaces/assemblies/members.adoc[Members] -. xref:admin:spaces/assemblies/admins.adoc[Assembly admins] -. xref:admin:spaces/assemblies/private_participants.adoc[Private participants] -. xref:admin:spaces/assemblies/moderations.adoc[Moderations] - -== Assemblies types - -For clasyfing the assemblies in different kinds, you can define Assembly types. These types can be filtered in the public -assemblies page. - -image:assemblies_type_filters.png[Filter by assembly type] - -image:assemblies_new_type_form.png[New assembly type form] - -.New assembly type form -|=== -|Field |Type |Description - -|Title -|Required -|Title of the this assembly type. For instance, "Consultative". - -|=== - -== Settings - -At the moment there's only a setting for configuring the general behaviour of assemblies. - -image:assemblies_settings.png[Assemblies settings] - -.Settings for assemblies form -|=== -|Field |Type |Description - -|Enable organization chart -|Checkbox -|Whether you want to show the organization chart in the assemblies list. - -|=== +You can then select the type of data you want to import from the file. -The organization chart is shown in the bottotm of the assemblies page. +* Import categories: Imports all the categories present in the original file. +* Import attachments : Import attachments of the original assembly. +* Import components : Imports all the components and their configuration from the original file, without importing their content. -image:assemblies_organization_chart.png[Assemblies organization chart] +== Examples -It allows a navigation in the assemblies tree, with the possibility to see the sub-assemblies that belongs to a parent assembly. +Below, you can find some links to example assemblies: -image:assemblies_organization_chart_filtered.png[Assemblies organization chart filtered] +* https://www.decidim.barcelona/assemblies[Decidim Barcelona neighborhood assemblies] +* https://meta.decidim.org/assemblies/general-assembly-association[Decidim association general assembly] +* https://jeparticipe.metropole.toulouse.fr/assemblies/capitole-arnaud-bernard-carmes[Toulouse neighborhood assembly] +* https://community.mautic.org/assemblies/ux-ui-tiger-team[Mautic open source project working group] diff --git a/docs/en/modules/admin/pages/spaces/assemblies/assembly_creation.adoc b/docs/en/modules/admin/pages/spaces/assemblies/assembly_creation.adoc new file mode 100644 index 0000000000..98ce105083 --- /dev/null +++ b/docs/en/modules/admin/pages/spaces/assemblies/assembly_creation.adoc @@ -0,0 +1,269 @@ += Assembly creation + +== 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. + +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: + +* 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] +* xref:admin:spaces/assemblies/attachments.adoc[Attachments] +* xref:admin:spaces/assemblies/members.adoc[Members] +* xref:admin:spaces/assemblies/admins.adoc[Assembly admins] +* xref:admin:spaces/assemblies/private_participants.adoc[Private participants] +* xref:admin:spaces/assemblies/moderations.adoc[Moderations] + +== General information + +This section allows to provide a general description about the assembly, mainly a title, URL, and description. + +image::spaces/assemblies/assemblies_new_form_general_info.png[New assembly form general info section] + +.New assembly form: General information +[cols="20h,10h,~,~"] +|=== +|Field |Type |Description |Visibility + +|Title +|Required +|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 +|Required +|Subtitle of the assembly. +|Visible in the "Hero image and CTA" landing page block. + +|Order position +|Required +|Determines the order of the assembly when displayed in the processes index or homepage. +|N/A + +|URL slug +|Required +|URL slugs are used to generate the URLs that point to this process. Only accepts letters, numbers and dashes, and must +start with a letter. +|Visible in the URL of the assembly, for example https://example.org/assemblies/city_coucil. + +|Hashtag +|Optional +|Hashtag redirecting to the X social network. +|Visible in the "Hero image and CTA" landing page block. + +|Short description +|Required +|A short explanation of what's your participatory process about. +|Visible in the "Main data" landing page block. + +|Description +|Required +|A long explanation of what's your assembly about. +|Visible in the "Main data" landing page block. + +|Purpose of action +|Optional +|The explanation of the assembly's goals. +|Visible in the "Main data" landing page block. + +|Composition +|Optional +|Who composes the assembly. +|Visible in the "Main data" landing page block. + +|Internal organisation +|Optional +|How the assembly is organized. +|Visible in the "Main data" landing page block. + +|Announcement +|Optional +|The text you enter here is shown to the user right below the process information. +|Visible in the "Announcement" landing page block. + +|=== + +== Duration + +This section allows to provide information about the assembly important dates. + +image::spaces/assemblies/assemblies_new_form_duration.png[New assembly form duration section] + +.New assembly form: Duration +[cols="20h,10h,~,~"] +|=== +|Field |Type |Description |Visibility + +|Date created +|Optional +|When this assembly was created. You have a calendar widget to choose the day. Expected format: dd/mm/yyyy. +|Visible in the "Dates metadata" landing page block. + +|Included at +|Optional +|The date when this assembly was added to the instance. It does not necessarily have to be the same as the creation date. Expected format: dd/mm/yyyy. +|Visible in the "Dates metadata" landing page block. + +|Duration +|Optional +|If the duration of this assembly is limited, select the end date. Otherwise, it appears as indefinite. Expected format: dd/mm/yyyy. +|Visible in the "Type and duration" landing page block. + +|Closing date +|Optional +|When this assembly closed. Expected format: dd/mm/yyyy. +|Visible in the "Dates metadata" landing page block. + +|Closing date reason +|Optional +|Why this assembly closed. +|Not displayed on the landing page. + +|=== + +== Images + +image::spaces/assemblies/assemblies_new_form_images.png[New assembly form images section] + +.New assembly form: Images +[cols="20h,10h,~"] +|=== +|Field |Type |Description + +|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 + +|Banner image +|Optional +|Deprecated, isn't used anywhere. Use "Hero image and CTA" content block on the landing page instead. + +|=== + +== Filters + +This section determines the filters available in the assembly, in the different components. +Filters can then be enabled and configured in each components. + +image::spaces/assemblies/assemblies_new_form_filters.png[New assembly form filters section] + +.New assembly form: Filters +[cols="20h,10h,~"] +|=== +|Field |Type |Description + +|Scopes enabled +|Optional +|Check if you want to have Scopes filtering in this assembly. + +|Scope +|Optional +|Which xref:admin:scopes.adoc[Scope] does this assembly belongs to. + +|Area +|Optional +|Which xref:admin:areas.adoc[Area] does this assembly belongs to. + +|=== + +== Metadata + +This section allows to provide meta information about the assembly. + +image::spaces/assemblies/assemblies_new_form_metadata.png[New assembly form metadata section] + +.New assembly form: Metadata +[cols="20h,10h,~"] +|=== +|Field |Type |Description + +|What is decided +|Optional +|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. + +|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. + +|Who participates +|Optional +|Who are the authorized participants, who can participate to the assembly. + +|=== + +== Visibility + +This section allows administrators to configure the process placement in the different pages and its publicity or no. + +image::spaces/assemblies/assemblies_new_form_visibility.png[New assembly form visibility section] + +.New assembly form: Visibility +[cols="20h,10h,~"] +|=== +|Field |Type |Description + +|Parent assembly +|Optional +|To what other assemblies this assembly belongs. Assemblies can be nested inside one another. + +|Highlighted +|Optional +|Check if you want the assembly to have more visibility in the Assemblies public list. It's also visible in the "Highlighted +Assemblies" Content Block in the xref:admin:homepage.adoc[Homepage] configuration. + +|Private space +|Optional +|Check if this assembly should only be accessible by xref:admin:spaces/assemblies/private_participants.adoc[Private Participants]. + +|Is transparent +|Optional +|Check if this assembly is private but should be visible to all the participants. This means that other participants +or visitors can see it but they can't participate in it. + +|=== + +== Other + +image::spaces/assemblies/assemblies_new_form_other.png[New assembly form other section] + +.New assembly form: Other +[cols="20h,10h,~"] +|=== +|Field |Type |Description + +|Created by +|Optional +|Choose "City Council" "Public" or "Other" in case you want to specify the name of the organization that created +this assembly. + +|Assembly type +|Optional +|Which xref:admin:spaces/assemblies/types.adoc[Assembly type] is related to this assembly. + +|Related participatory processes +|Optional +|Select other participatory processes related to this assembly. + +|Social +|Optional +|Which social networks profile does this assembly has. Can be X, Facebook, Instagram, YouTube, and/or GitHub. + +|=== diff --git a/docs/en/modules/admin/pages/spaces/assemblies/members.adoc b/docs/en/modules/admin/pages/spaces/assemblies/members.adoc index b64508b465..3041758272 100644 --- a/docs/en/modules/admin/pages/spaces/assemblies/members.adoc +++ b/docs/en/modules/admin/pages/spaces/assemblies/members.adoc @@ -1,25 +1,38 @@ = Assembly members -Assembly members allow showing all the people or groups that belong to a given assembly. It's useful for being transparent. +== Understand the basics -You can see an example in https://meta.decidim.org/assemblies/coordination-committee/members[Decidim Coordination Commitee Assembly in Metadecidim]. +Assembly members allow showing all the participants that belong to a given assembly, whether individuals or groups. +This is a feature specific to the assemblies space, made for improving transparency of the organization assemblies. -image:assembly_members.png[Assembly members of the Coordination Committee] +image::spaces/assemblies/assembly_members.png[Assembly members] -== New assembly member form +== Manage assembly members -image:assembly_members_list.png[Assembly members admin list] +To access the assembly members list, click in the secondary navigation panel on the "Members" item. -For creating a new phase of a participatory process: +image::spaces/assemblies/assembly_members_list.png[Assembly members administration list] -. Sign in as administrator -. Go to the assemblies section in the sidebar -. Click on the assembly Edit action -. Click on the Members link in the sidebar -. Click on the "New member" button -. Fill the form +== Actions -image:assembly_members_new_form.png[Assembly members new form] +|=== +|Icon |Name |Definition + +|image:icons/action_edit.png[Edit icon] +|Edit +|To edit this member fields. + +|image:icons/action_delete.png[Delete icon] +|Delete +|To delete this member. + +|=== + +== Create an assembly member + +To create a new assembly member, click the "New assembly member" button in the top right of the page. + +image::spaces/assemblies/assembly_members_new_form.png[Assembly members new form] .New assembly member form |=== @@ -27,35 +40,36 @@ image:assembly_members_new_form.png[Assembly members new form] |Participant type |Required -|Wheter this assembly member is non-participant or existing participant. Do they already have an account created on the platform? +|Wether this assembly member already has an account on the instance or not. |Full name -|Required if it's non-participant. -| +|Required. +|Field displayed if "non participant" was selected. + +|Avatar +|Optional. +|Field displayed if "non participant" was selected. |User or group |Required if it's an existing participant. -|Type at least three characters to search. +|Type at least three characters to search for the participant account. |Position |Required |Choose one of President, Vice president, Secretary, or Other. In case it's other, you can fill in the position title. -|Weight +|Order position |Optional -|Which order will it have in relation to the other members. Having a lower number means a higher priority. For instance, if you have two members, "Member a" with weight "10" and "Member b" with weight "0", then "Member b" will be first when ordering. +|Which order the members has in relation to the other members. Having a lower number means a higher priority. +For instance, if you have two members, "Member a" with weight "10" and "Member b" with weight "0" then "Member b" is first when ordering. |Designation date |Required -|When was this person or group assigned as a member of this assembly. Expected format: dd/mm/yyyy - -|Designation mode -|Optional -|How was this person designed. +|When this person or group was assigned as a member of this assembly. Expected format: dd/mm/yyyy. |Ceased date |Optional -|When was this person or group ceased to be a member of this assembly. Expected format: dd/mm/yyyy +|When this person or group ceased to be a member of this assembly. Expected format: dd/mm/yyyy. |Gender |Optional @@ -63,7 +77,7 @@ image:assembly_members_new_form.png[Assembly members new form] |Birthday |Optional -|When was this person born. Expected format: dd/mm/yyyy +|When was this person born. Expected format: dd/mm/yyyy. |Birthplace |Optional diff --git a/docs/en/modules/admin/pages/spaces/assemblies/types.adoc b/docs/en/modules/admin/pages/spaces/assemblies/types.adoc new file mode 100644 index 0000000000..54e433f791 --- /dev/null +++ b/docs/en/modules/admin/pages/spaces/assemblies/types.adoc @@ -0,0 +1,45 @@ += Assemblies types + +== Understand the basics + +In some cases it is necessary to organize assemblies by more than just children and sub-assemblies. +This is where assemblies types can be useful, and add a layer of categorization. +Participants are then able to filter assemblies by the assembly types you created. + +NOTE: Assembly types work similarly to xref:admin:spaces/processes/types.adoc[Process types]. + +== Manage assemblies types + +To access the assembly types list, click the "Manage" button on the top right of the page, and click the "Assemblies type" menu item. + +image::spaces/assemblies/assemblies_types_list.png[Backend assemblies types menu item] + +== Create an assembly type + +Click the "New assembly type" button on the top right of the page. + +image::spaces/assemblies/assemblies_types_form.png[Process type creation form] + +.New assembly type form: General information +[cols="20h,10h,~"] +|=== +|Field |Type |Description + +|Title +|Required +|Title of the assembly type. + +|=== + +== Add assembly type to an assembly + +To relate assemblies to assembly types, in the edition page of an assembly, select the assembly type under the section labelled Other. + +image:spaces/assemblies/assemblies_types_edit_process.png[Choose an assembly type when editing an assembly] + +== Filter by assembly types + +If there is at least one assembly type defined and related to an assembly, a filter is displayed at the left of the assemblies list +in the participant interface, allowing filtering of assemblies. + +image::spaces/assemblies/assemblies_types_filter.png[Assemblies types filter in the assemblies index] \ No newline at end of file diff --git a/docs/en/modules/admin/pages/spaces/processes.adoc b/docs/en/modules/admin/pages/spaces/processes.adoc index 7fe8cbaabe..f251438c59 100644 --- a/docs/en/modules/admin/pages/spaces/processes.adoc +++ b/docs/en/modules/admin/pages/spaces/processes.adoc @@ -1,7 +1,16 @@ -= Processes += Participatory processes -A participatory process is a sequence of participatory activities (e.g. first filling out a survey, then making proposals, -discussing them in face-to-face or virtual meetings, and finally prioritizing them) with the aim of defining and making a decision on a specific topic. +== Understand the basics + +A participatory process is a sequence of participatory activities with the aim of defining and making a decision on a specific topic. +For example, you could have a participatory process like this: + +. First filling out a survey for collect participants opinion; +. Then opening proposals; +. Discussing them in face-to-face or virtual meetings; +. Finally prioritizing them before implementation. + +NOTE: You want to create a participatory process? Check the xref:admin:spaces/processes/process_creation.adoc[process creation] article. Examples of participatory processes are: a process of electing committee members (where candidatures are first presented, then debated and finally a candidacy is chosen), participatory budgets (where proposals are made, valued economically, @@ -13,230 +22,107 @@ in a participatory process in Decidim: image::process_steps_components.png[Relation between Steps and Components in a Process in Decidim] -What this diagram is showing is that for a participatory process you can have 7 phases: - -. Configuration & Presentation -. Diagnostic -. Proposal Creation -. Proposal Selection -. Results -. Evaluation -. Monitoring - -Inside of every one of these Phases, there are some components (like Blog, Meetings, Survey, Debates, Proposals, Results). -Some of these Components allow some features depending on the Phase that we are. - -In this section, we'll explain how we can configure a Participatory Process in Decidim. +What this diagram is showing is that for a participatory process you can configure different phases, and enable and configure +the components for each phase as you need it for your process. -== List +Inside of every one of these Phases, you can enable the xref:admin:components.adoc[Components] you need. -To configure participatory processes on the Decidim platform, click on btn:[Processes] in the admin sidebar menu. A list -will appear with the existing processes if there are any: +In this documentation section, you can find how to configure and manage all of those items: -image::processes_list.png[Participatory processes list] +* xref:admin:spaces/processes/groups.adoc[Process Groups] +* xref:admin:spaces/processes/types.adoc[Process Types] +** xref:admin:spaces/processes/process_creation.adoc[Process creation] +** xref:admin:spaces/processes/landing_page.adoc[Landing page] +** xref:admin:spaces/processes/phases.adoc[Phases] +** xref:admin:spaces/processes/components.adoc[Components] +** xref:admin:spaces/processes/categories.adoc[Categories] +** xref:admin:spaces/processes/attachments.adoc[Attachments] +** xref:admin:spaces/processes/admins.adoc[Process admins] +** xref:admin:spaces/processes/private_participants.adoc[Private participants] +** xref:admin:spaces/processes/moderations.adoc[Moderations] -You can filter by the ones that are: +== How to find it? -* Published / Unpublished -* Public / Private +To access the Participatory processes panel, go in the administration panel and click the "Processes" item in the administration +navigation bar. -image::processes_list_filter.png[Participatory processes list filtered] +image::spaces/processes/processes_menu.png[Pages: Access processes panel] -You can also search by title and control how many elements are in the list. - -You have 4 possible actions in this list after a Participatory Process is created: - -1. Export: send by email the configuration for a given process. Can be imported in other Decidim installation. -2. Duplicate: to duplicate this process. -3. Configure: to edit the metadata and configuration for a process. -4. Preview: how it will look once published. - -== New process form - -image::processes_new_form.png[New participatory process form] - -.New participatory process form: General information -|=== -|Field |Type |Description +There, you are able to manage participatory processes and processes groups. -|Title -|Required -|Title of the participatory process. For instance, "Participatory Budgeting 2020". +== Manage processes -|Subtitle -|Required -|Subtitle. For instance, "Let's decide our priorities together" +image::spaces/processes/processes_list.png[Participatory processes list] -|URL slug -|Required -|URL slugs are used to generate the URLs that point to this process. Only accepts letters, numbers and dashes, and must -start with a letter. Example: if your domain is 'example.org' and your slug 'participatory-budget-2020' then your URL will -be https://example.org/processes/participatory-budget-2020 +On this page, you are able to manage processes and xref:admin:spaces/processes/groups.adoc[process groups]. -|Hashtag -|Optional -|Hashtag for Twitter +You can find all the processes on the list in the administration panel, with: -|Short description -|Required -|A short explanation of what's your participatory process about. +* *Title*: title of the process. +* *Created at*: date of creation of the process. +* *Private*: if the process is opened to all participants or to only certain participants. +* *Published*: if the process is published or no. -|Description -|Required -|A long explanation of what's your participatory process about. +You can filter and sort this list by clicking the "Filter" button and the columns headers. +You can also search for processes by their title in the search bar. -|Announcement -|Optional -|The text you enter here will be shown to the user right below the process information. +image::spaces/processes/processes_list_filter.png[Participatory processes list filtered] -|=== +== Actions -.New participatory process form: Duration |=== -|Field |Type |Description - -|Start date -|Optional -|When this process start. You have a calendar widget to choose the day. Expected format: dd/mm/yyyy - -|End date -|Optional -|When this process start. You have a calendar widget to choose the day. Expected format: dd/mm/yyyy +|Icon |Name |Definition -|=== +|image:icons/action_edit.png[Configure process icon] +|Configure +|To edit the configuration and components for a process. -.New participatory process form: Images -|=== -|Field |Type |Description +|image:icons/action_export.png[Export process icon] +|Export all +|Send the process configuration JSON file by email. Then it can be imported in other Decidim installation. -|Home image -|Optional -|Image that will be 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: 10MB +|image:icons/action_duplicate.png[Duplicate process icon] +|Duplicate +|To duplicate this process. -|Banner image -|Optional -|Image that will be used inside of the 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: 10MB +|image:icons/action_preview.png[Preview process icon] +|Preview +|Preview of how the process looks in the user interface. -|=== +|image:icons/action_moderate.png[Moderate process icon] +|Moderate +|To access the process moderation panel. -.New participatory process form: Metadata |=== -|Field |Type |Description -|Promoter group -|Optional -|Information that's displayed in the process metadata sidebar. +You can also click the "Manage" button at the top right of the page, to be able to import a process or +configure xref:admin:spaces/processes/types.adoc[Process Types]. -|Organization area -|Optional -|Information that's displayed in the process metadata sidebar. +=== Import a process -|Scope metadata -|Optional -|Information that's displayed in the process metadata sidebar. +To import a process, click the "Manage" button at the top right of the page. -|Who participates -|Optional -|Information that's displayed in the process metadata sidebar. +image::spaces/processes/import_menu.png[Participatory processes import menu] -|What is decided -|Optional -|Information that's displayed in the process metadata sidebar. +You are redirected to the import page, where you need to fill in those fields: -|How is it decided -|Optional -|Information that's displayed in the process metadata sidebar. - -|=== - -image::process_frontend_metadata.png[Process frontend metadata] - -image::process_backend_metadata.png[Process backend metadata] - -.New participatory process form: Filters -|=== -|Field |Type |Description +* Title : The title you wish to give to the process. +* URL identifier: The ‘slug’ for the process. +* Add a document: Here you need to load the process JSON file obtained by email when exporting. -|Scopes enabled -|Optional -|Check if you want to have Scopes filtering in this process. - -|Scope -|Optional -|Which xref:admin:scopes.adoc[Scope] does this process belongs to. - -|Scope filter depth -|Optional -|Restrict the scope filter depth; The filter will show from general to the selected scope type. This is only relevant if -you have complex relations in Scopes children (like a Russian Doll). For instance if you have a Grandmother -> Mother -> -Child, this setting allows you to choose the Mother, so the participants can only choose the Child. This would be the -case for instance if you have Provinces -> Cities -> Districts, and the process is about a particular City. - -|Area -|Optional -|Which xref:admin:areas.adoc[Area] does this process belongs to. - -|=== - -.New participatory process form: Visibility -|=== -|Field |Type |Description - -|Processes group -|Optional -|Enables to make groups of multiple participatory processes. Ideally for processes that are related between them, for -instance multiple squares in a City or multiple documents using the same participatory rules. - -|Private space -|Optional -|Check if this process should only be accessible by xref:admin:spaces/processes/private_participants.adoc[Private Participants] - -|Promoted -|Optional -|Check if you want the process to have more visibility in the Process public list. It'll also be visible in the -Participatory Process Content Block in the xref:admin:homepage.adoc[Homepage] configuration. This is accessible in the -btn:[Edit] action in a Process. - -|=== - -.New participatory process form: Filters -|=== -|Field |Type |Description - -|Related processes -|Optional -|Select other participatory processes that are related to this one. - -|=== - -.New participatory process form: Filters -|=== -|Field |Type |Description - -|Show statistics -|Optional -|Check if you want to show the Statistics section. - -|Show metrics -|Optional -|Check if you want to show the Metrics section. - -|=== +You can then select the type of data you want to import from the file. -After you've initially created your process you have a submenu where you need to keep configuring more information -about your participatory process. +* Import steps: Imports all the phases present in the original file. +* Import categories: Imports all the categories present in the original file. +* Import attachments : Import attachments of the original process. +* Import components : Imports all the components and their configuration from the original file, without importing their content. -image::process_submenu.png[Process submenu in admin] +== Examples -Here you can keep configuring your process: +Below, you can find some links to examples participatory processes: -. Info: the same form that we explained in this page. -. xref:admin:spaces/processes/phases.adoc[Phases] -. xref:admin:spaces/processes/components.adoc[Components] -. xref:admin:spaces/processes/categories.adoc[Categories] -. xref:admin:spaces/processes/attachments.adoc[Attachments] -. xref:admin:spaces/processes/admins.adoc[Process admins] -. xref:admin:spaces/processes/private_participants.adoc[Private participants] -. xref:admin:spaces/processes/moderations.adoc[Moderations] +* https://www.decidim.barcelona/processes/PAM2020[Procés participatiu del Programa d'Actuació Municipal (PAM) 2020-2023, Barcelona] +* https://www.participate.nyc.gov/processes/Citywidepb2024[The People's Money (2024-2025), New York city participatory budget] +* https://brasilparticipativo.presidencia.gov.br/processes/planoclima/[Plano Clima, Brazilian government] +* https://omastadi.hel.fi/processes/osbu-2023/[Helsinki city participatory budget] +* https://ecrivons.angers.fr/processes/BP24-25[Angers city participatory budget] diff --git a/docs/en/modules/admin/pages/spaces/processes/groups.adoc b/docs/en/modules/admin/pages/spaces/processes/groups.adoc index 9d8101fd66..ac2c7d383c 100644 --- a/docs/en/modules/admin/pages/spaces/processes/groups.adoc +++ b/docs/en/modules/admin/pages/spaces/processes/groups.adoc @@ -1,113 +1,232 @@ = Process groups -A group of processes proves useful for subdividing large participatory processes into subprocesses according to a criteria, -for instance the xref:admin:scopes.adoc[scope] of every process. +== Understand the basics -As an example you can see the https://www.decidim.barcelona/processes_groups/4[Barcelona City Council's Neighborhoods Plan, Pla de Barris]. -This is is a 150 million euro shock plan that aims to reduce inequalities within the city. There are 10 related processes, one for each involved neighborhood. +A group of processes can be useful for subdividing large participatory processes into sub-processes according to a criteria. +It can also allow administrators to organize an instance with a lot of processes, to gather together the ones related to a +specific type of process, or a specific scope, like participatory budgeting annual editions, mobility planning processes, etc. -image::processes_group_example.png[Participatory process group example] +== Manage process groups -== New process group form +To access the process group management page, click the "Process groups" tab in the processes index page. +There, you can find the list of process groups. -For creating a new process group: +image::spaces/processes/processes_group_list.png[Participatory process groups list] -. Sign in as administrator -. Go to the Processes section in the sidebar -. Click on the Process groups link in the sidebar -. Click on the "New process group" button -. Fill in the form +=== Actions -image::processes_group_list.png[Participatory process groups list] +|=== +|Icon |Name |Definition + +|image:icons/action_edit.png[Edit process group icon] +|Edit +|To edit the configuration and components for the process group. + +|image:icons/action_preview.png[Preview process group icon] +|Preview +|See a preview of the process group landing page. + +|image:icons/action_delete.png[Delete process group icon] +|Delete +|To delete this process group. + +|=== + +== Create a process group + +To create a new process group, click the "New process group" button in the top right of the page. -image::processes_group_new_form.png[New participatory process group form] +=== About this process + +This section allows to provide a general description about the process group, mainly a title, image, and description, and to +select the existing processes that pertain to the group. + +image::spaces/processes/processes_group_form_about.png[Participatory process groups creation form about this process] .New participatory process group form: General information +[cols="20h,10h,~,~"] |=== -|Field |Type |Description +|Field |Type |Description |Visibility |Title |Required -|Title of the participatory process group. For instance, "Participatory Budgeting". +|Title of the participatory process group. +|Visible in the card of the process groups on the homepage, the processes index, the navigation, the "title and description" +and the "Hero image and CTA" landing page blocks. |Description |Required -|A long explanation of what's your participatory process about. +|A long explanation of what's the process group about. +|Visible in the card of the processes index and the "title and description" landing page block. |Related processes |Optional -|Which are the processes that are related to this one? They will be used for populating -the Content Blocks in the Landing page of this Process group. For selecting multiple you'll -need to use the *ctrl* function. +|The processes that should be grouped inside this process group. To select multiple processes, use the *CTRL* or *CMD* key. +|Visible in the "Participatory processes" landing page block. |Image |Optional |Image that will be used in presentation cards of this process group. Guidance for image: Preferably a landscape image that does not have any text. The service crops the image. -Maximum file size: 10MB. Allowed file extensions: jpeg jpg png +Maximum file size: 10 MB. Allowed file extensions: JPEG JPG PNG +|Visible in the card of the process groups on the homepage and the processes index. |=== +=== Metadata + +This section allows to provide meta information about the process group. +It can be enabled on the landing page with the "Metadata" landing page block. + +image::spaces/processes/processes_group_form_metadata.png[Participatory process groups creation form metadata] + .New participatory process group form: Metadata +[cols="20h,10h,~"] |=== |Field |Type |Description -Hashtag -Website +|Hashtag +|Optional +|Hashtag redirecting to the X social network. + +|Website +|Optional +|Website related to this process group. |Promoter group |Optional -|Information that's displayed in the process metadata content block. +|If a specific group is at the origin of the process, like a city direction, an association committee, etc. |Organization area |Optional -|Information that's displayed in the process metadata content block. +|The organization domain or category, if it's relevant. |Scope metadata |Optional -|Information that's displayed in the process metadata content block. +|Metadata on the process scope, if it's relevant. |Who participates |Optional -|Information that's displayed in the process metadata content block. +|Who are the authorized participants, who can participate to the process. |What is decided |Optional -|Information that's displayed in the process metadata content block. +|The issue of the process, the object of what is decided. |How is it decided |Optional -|Information that's displayed in the process metadata content block. +|The decision making process. |=== +=== Visibility + +This section allows administrators to configure the process group visibility in the homepage and processes index. + +image::spaces/processes/processes_group_form_visibility.png[Participatory process groups creation form visibility] + .New participatory process group form: Visibility +[cols="20h,10h,~"] |=== |Field |Type |Description |Promoted |Optional -|Check if you want the process to have more visibility in the Process public list. It'll also be visible in the -ParticpipatoryProcess Content Block in the xref:admin:homepage.adoc[Homepage] configuration. This is accessible in the btn:[Edit] action in a Process. +|Check if you want the process to have more visibility in the Process public list. It'll also be visible in the "Highlighted processes" +content block in the xref:admin:homepage.adoc[Homepage]. |=== -== Landing page - -One of the main features of a process group is to be able to configure the Landing page, through Content blocks, just like -the general homepage of the platform. This means that you can enable or disable different sections of the landing page and also -configure some fo these sections. - -image::processes_group_landing.png[Participatory process group landing page] - -* Title, description and hashtag -* Metadata -* Image, text and Call to Action button. Configurable. -* Proposals. You can configure how the elements will be sorted: by most recent or random. -* Results. You can configure how the elements will be sorted: by most recent or random. -* Upcoming events -* Statistics -* Participatory processes -* First HTML block -* Second HTML block -* Third HTML block +== Landing page content blocks + +Process groups are mainly landing pages, grouping more complex participatory processes. +This landing page works with different content blocks, just like the general homepage of the platform. +This means that you can enable different sections of the landing page and configure some of these sections. + +To configure a process group landing page, when editing the process group, click the "Manage" button in the top right of the page, +and click the "Landing page" menu item. + +image::spaces/processes/processes_group_landing.png[Participatory process group landing page] + +Below, you'll find all the content blocks configuration guides and screenshots of how there are displayed on the landing page. + +NOTE: If there is no content to display in a content block, or if wasn't configured, it won't be displayed on the landing page. + +=== Title and description + +The Title and description content block allows to display: + +* *Title*: the title of the process group. +* *Description*: the description of the process group. +* *Number of related processes*: the number of published participatory processes related to this process group. +* *Scope*: the scope of the process group. +* *Hashtag*: the hashtag, redirecting to the X social media. +* *Website*: a link to the website. + +image::spaces/processes/processes_group_landing_title.png[Participatory process group landing page title and description block] + +=== Metadata + +image::spaces/processes/processes_group_landing_metadata.png[Participatory process group landing page metadata block] + +=== Hero image and CTA + +The hero image and CTA content block allows to display: + +* *Title*: the title of the process group. +* *an hashtag*: the hashtag, redirecting to the X social media. +* *a call to action button*: enable it by clicking the "Edit" icon on the landing page content block. +* *an image*: download an image for this block by clicking the "Edit" icon on the landing page content block. + +image::spaces/processes/processes_group_landing_hero.png[Participatory process group landing page hero block] + +=== Proposals + +The Proposals content block allows to display a selection of proposals from the different participatory processes of the process group. +You can configure how the proposals are sorted by most recent or random by clicking the "Edit" icon on the landing page content block. + +image::spaces/processes/processes_group_landing_proposals.png[Participatory process group landing page proposals block] + +=== Results + +The Results content block allows to display a selection of results from the different participatory processes. +You can configure how the results are sorted by most recent or random by clicking the "Edit" icon on the landing page content block. + +image::spaces/processes/processes_group_landing_results.png[Participatory process group landing page results block] + +=== Upcoming meetings + +The Upcoming meetings content block allows to display a selection of meetings from the different participatory processes. +You can configure how the results are sorted by most recent or random by clicking the "Edit" icon on the landing page content block. +If there is no upcoming meetings, this block shows the past ones. + +image::spaces/processes/processes_group_landing_events.png[Participatory process group landing page events block] + +=== Statistics + +image::spaces/processes/processes_group_landing_stats.png[Participatory process group landing page statistics block] + +=== Participatory processes + +The participatory processes content block displays a grid of participatory processes on the landing page. +You can configure if only active processes will be displayed by clicking the "Edit" icon on the landing page content block. + +image::spaces/processes/processes_group_landing_processes.png[Participatory process group landing page processes block] + +=== HTML blocks + +The HTML block content block allows to add an editable HTML block on the landing page, and therefore to create a personalized section. + +image::spaces/processes/processes_group_landing_html.png[Participatory process group landing page HTML blocks] + +== Examples + +The https://www.decidim.barcelona/processes_groups/4[Barcelona City Council's Neighborhoods Plan], a 150 million +euro shock plan that aims to reduce inequalities within the city. There are 10 sub-processes, one for each involved neighborhood. + +image::spaces/processes/processes_group__barcelona_example.png[Participatory process group example] + +The https://participer.loire-atlantique.fr/processes_groups/32[Loire-Atlantique participatory budget], with an elaborated HTML block +on the landing page. + +image::spaces/processes/processes_group__cd44_example.png[Participatory process group example] diff --git a/docs/en/modules/admin/pages/spaces/processes/landing_page.adoc b/docs/en/modules/admin/pages/spaces/processes/landing_page.adoc new file mode 100644 index 0000000000..81d1ed5112 --- /dev/null +++ b/docs/en/modules/admin/pages/spaces/processes/landing_page.adoc @@ -0,0 +1,2 @@ + +include::partial$page_landing_page.adoc[] diff --git a/docs/en/modules/admin/pages/spaces/processes/phases.adoc b/docs/en/modules/admin/pages/spaces/processes/phases.adoc index f63c5e4864..da40ad2c6d 100644 --- a/docs/en/modules/admin/pages/spaces/processes/phases.adoc +++ b/docs/en/modules/admin/pages/spaces/processes/phases.adoc @@ -1,12 +1,14 @@ = Phases +== Understand the basics + A participatory process is a sequence of phases ordered in time. Depending on which phase of the process timeline you -are, then you can enable or disable some features. +are, then you can enable and configure the features you need for each phase. Ideally, the Phases of a Participatory Process are always the same and are not changed, so participants can know what are -the rules and timeframe and can organize their lives to know when it'd be best for them to participate in this process. +the rules and time frame and can organize to know when it'd be best for them to participate in this process. -As a guideline, the standard structure of a participatory process may be as follows: +For example, the standard structure of a participatory process could be as follows: . Presentation . Diagnosis @@ -15,76 +17,79 @@ As a guideline, the standard structure of a participatory process may be as foll . Proposals evaluation . Monitoring -Participants can find the link to different phases of a participatory process in the header of the participatory process, -in the link "Process phases". Here they can see the full description and explanation of the phases. The active phase -will be highlighted. +Participants can find the link to different phases of a participatory process in the "Phase and duration" landing page content block, +when it's enabled by an administrator in the process xref:admin:spaces/processes/landing_page.adoc[Landing page]. -image:process_phases_header.png[Header with processes phases link] +image::spaces/processes/process_phases_block.png[Block with processes phases link] -image:process_phases.png[Process phases explanation] +When clicking on the link for the active phase, they can see the full description and explanation of the phases in a pop-up. -== Create a new phase +image::spaces/processes/process_phases.png[Process phases explanation] -image:process_phases_list.png[Phases of a participatory process] +== Manage phases -For creating a new phase of a participatory process: +To access the phases configuration, click in the secondary navigation panel on the "Phases" item. -. Sign in as administrator -. Go to the participatory process section in the sidebar -. Click on the participatory process Edit action -. Click on the Phases link in the sidebar -. Click on the "New phase" button +image::spaces/processes/process_phases_list.png[Phases of a participatory process] -image:process_phases_new_form.png[Create a new participatory process phase form] +=== Actions -.Create meeting +|=== +|Icon |Name |Definition |Condition + +|image:icons/action_edit.png[Edit icon] +|Edit +|To edit this phase. +|Always available + +|image:icons/action_activate.png[Activate icon] +|Activate +|To make this phase the active one. +|Only available for inactive phases. + +|image:icons/action_delete.png[Delete icon] +|Delete +|To delete this phase. +|Always available + +|=== + +== Create a new phase + +To create a new phase, click the "New phase" button in the top right of the page. + +image::spaces/processes/process_phases_new_form.png[Create a new participatory process phase form] + +.Create process phase form +[cols="20h,10h,~"] |=== |Field |Type |Description |Title |Required -|What is the title for this phase. +|The title for this phase, displayed in the phase content block and on the process cards when phase is active. |Description -| +|Optional |A long description explaining what's this phase for. |Start date -| -|Which day this phase will start. Expected format: dd/mm/yyyy +|Optional +|The start date of this process phase. Expected format: dd/mm/yyyy |End date -| -|Which day this phase will end. Expected format: dd/mm/yyyy +|Optional +|The end date of this process phase. Expected format: dd/mm/yyyy |Call to Action path -| -|Where will the button link to. For instance, it could point to the new proposal creation form. Use partial paths, not full -URLs here. Accepts letters, numbers, dashes, and, slashes, and must start with a letter. If not set, the button will not be shown. +|Optional +|Deprecated |Call to Action text -| -|What will the button say. For instance, it could be "Create a proposal". If not set, the button will not be shown. - -|=== - -== Actions - -After a phase was created you have these actions: +|Optional +|Deprecated |=== -|Icon |Name |Definition - -|image:action_activate.png[Activate icon] -|Activate -|To make this phase the active one. - -|image:action_edit.png[Edit icon] -|Edit -|To edit this phase. -|image:action_delete.png[Delete icon] -|Delete -|To delete this phase. - -|=== +CAUTION: Configuring the CTA through the Phase of the participatory process is deprecated with the new design. +Now this is done in the Landing Page, using the Hero and image content block. diff --git a/docs/en/modules/admin/pages/spaces/processes/process_creation.adoc b/docs/en/modules/admin/pages/spaces/processes/process_creation.adoc new file mode 100644 index 0000000000..f26709c074 --- /dev/null +++ b/docs/en/modules/admin/pages/spaces/processes/process_creation.adoc @@ -0,0 +1,237 @@ += Participatory process creation + +== Understand the basics + +Participatory processes allows administrators to configure components in articulation with different participatory phases. +To start creating a process, when on the process list, click the "New process" button at the top right of the page. + +The process creation form is divided into different sections that are detailed in the sections below. + +Once you created a process, in the secondary navigation panel, you can see all the process configuration available: + +* xref:admin:spaces/processes/process_creation.adoc[About this process]: here you can access and edit all the fields from the creation form. +* xref:admin:spaces/processes/landing_page.adoc[Landing page] +* xref:admin:spaces/processes/phases.adoc[Phases] +* xref:admin:spaces/processes/components.adoc[Components] +* xref:admin:spaces/processes/categories.adoc[Categories] +* xref:admin:spaces/processes/attachments.adoc[Attachments] +* xref:admin:spaces/processes/admins.adoc[Process admins] +* xref:admin:spaces/processes/private_participants.adoc[Private participants] +* xref:admin:spaces/processes/moderations.adoc[Moderations] + +== General information + +This section allows to provide a general description about the process, mainly a title, URL, and description. + +image::spaces/processes/processes_new_form_general_info.png[New participatory process form general info section] + +.New participatory process form: General information +[cols="20h,10h,~,~"] +|=== +|Field |Type |Description |Visibility + +|Title +|Required +|Title of the participatory process. For instance, "Participatory Budgeting 2020" +|Visible in the card of the process on the homepage, the processes index, the navigation, and the "Hero image and CTA" landing page block. + +|Subtitle +|Required +|Subtitle. For instance, "Let's decide our priorities together" +|Visible in the "Hero image and CTA" landing page block. + +|Order position +|Required +|Determines the order of the process when displayed in the processes index or homepage. +|N/A + +|URL slug +|Required +|URL slugs are used to generate the URLs that point to this process. Only accepts letters, numbers and dashes, and must +start with a letter. +|Visible in the URL of the participatory process, for example https://example.org/processes/participatory-budget-2020. + +|Hashtag +|Optional +|Hashtag redirecting to the X social network. +|Visible in the "Hero image and CTA" landing page block. + +|Short description +|Required +|A short explanation of what's the participatory process about. +|Visible in the "Main data" landing page block. + +|Description +|Required +|A detailed explanation of what's the participatory process about. +|Visible in the "Main data" landing page block. + +|Announcement +|Optional +|The text you enter here is shown to the user right below the process information. +|Visible in the "Announcement" landing page block. + +|=== + +== Duration + +This section allows to provide information about the process start and end dates. +It can be enabled on the landing page with the "Phase & duration" landing page block. + +image::spaces/processes/processes_new_form_duration.png[New participatory process form duration section] + +.New participatory process form: Duration +[cols="20h,10h,~"] +|=== +|Field |Type |Description + +|Start date +|Optional +|When this process start. You have a calendar widget to choose the day. Expected format: dd/mm/yyyy + +|End date +|Optional +|When this process start. You have a calendar widget to choose the day. Expected format: dd/mm/yyyy + +|=== + +== Images + +image::spaces/processes/processes_new_form_images.png[New participatory process form images section] + +.New participatory process form: Images +[cols="20h,10h,~"] +|=== +|Field |Type |Description + +|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 + +|=== + +== Metadata + +This section allows to provide meta information about the process. +It can be enabled on the landing page with the "Metadata" landing page block. + +image::spaces/processes/processes_new_form_metadata.png[New participatory process form metadata section] + +.New participatory process form: Metadata +[cols="20h,10h,~"] +|=== +|Field |Type |Description + +|Promoter group +|Optional +|If a specific group is at the origin of the process, like a city direction, an association committee, etc. + +|Organization area +|Optional +|The organization domain or category, if it's relevant. + +|Scope metadata +|Optional +|Metadata on the process scope, if it's relevant. + +|Who participates +|Optional +|Who are the authorized participants, who can participate to the process. + +|What is decided +|Optional +|The issue of the process, the object of what is decided. + +|How is it decided +|Optional +|The decision making process. + +|=== + +== Filters + +This section determines the filters available in the process, in the different components. +Filters can then be enabled and configured in each components. + +image::spaces/processes/processes_new_form_filters.png[New participatory process form filters section] + +.New participatory process form: Filters +[cols="20h,10h,~"] +|=== +|Field |Type |Description + +|Scopes enabled +|Optional +|Check if you want to have Scopes filtering in this process. + +|Scope +|Optional +|Which xref:admin:scopes.adoc[Scope] does this process belongs to. + +|Scope filter depth +|Optional +|Restrict the scope filter depth. This is relevant if you have complex relations in Scopes children (like a Russian Doll). +For instance if you have Grandmother -> Mother -> Child nested scopes, this setting allows you to choose the Mother scope, +so the participants can only filter between the Child sub-scopes. This would be the case for instance if you have +Provinces -> Cities -> Districts, and the process is about a particular City. + +|Area +|Optional +|Which xref:admin:areas.adoc[Area] does this process belongs to. + +|=== + +== Visibility + +This section allows administrators to configure the process placement in the different pages and its publicity or no. + +image::spaces/processes/processes_new_form_visibility.png[New participatory process form visibility section] + +.New participatory process form: Visibility +[cols="20h,10h,~"] +|=== +|Field |Type |Description + +|Processes group +|Optional +|Enables to group multiple processes together. Check xref:admin:spaces/processes/groups.adoc[Process Groups] to know more. + +|Private space +|Optional +|Check this if the process should only be accessible by xref:admin:spaces/processes/private_participants.adoc[Private Participants]. + +|Promoted +|Optional +|Check if you want the process to have more visibility in the Process public list and the "Highlighted processes" content block +in the xref:admin:homepage.adoc[Homepage] configuration. + +|=== + +== Related processes + +This section allows to create relations between processes. It's different from processes groups. +It can be enabled on the landing page with the "Related processes" landing page block. + +image::spaces/processes/processes_new_form_related_processes.png[New participatory process form Related processes section] + +.New participatory process form: Related processes +[cols="20h,10h,~"] +|=== +|Field |Type |Description + +|Related processes +|Optional +|Select other participatory processes that are related to this one. + +|=== + +== Other + +This section is empty, unless an administrator already created xref:admin:spaces/processes/types.adoc[Process Types]. +If so, you should be able to select a process type to categorize the process. +Participants are then able to filter processes in the processes index with those types. + +image::spaces/processes/process_types_edit_process.png[Choose a process type when editing a process] + +image::spaces/processes/process_types_filter.png[Process types filter in the processes index] diff --git a/docs/en/modules/admin/pages/spaces/processes/types.adoc b/docs/en/modules/admin/pages/spaces/processes/types.adoc index 785d1c5009..1bae4dd1b3 100644 --- a/docs/en/modules/admin/pages/spaces/processes/types.adoc +++ b/docs/en/modules/admin/pages/spaces/processes/types.adoc @@ -1,40 +1,45 @@ = Process types -In some cases it is necessary to organize participatory processes by more than just xref:spaces/processes/groups.adoc[Process Groups]. This is where Process Types can be useful. +== Understand the basics -Process Types work similarly to xref:admin:spaces/assemblies.adoc#_assemblies_types[Assembly types]. +In some cases it is necessary to organize participatory processes by more than just xref:spaces/processes/groups.adoc[Process Groups]. +This is where process types can be useful, and add a layer of categorization. +Participants are then able to filter processes by the process types you created. -== New process type form +NOTE: Process types work similarly to xref:admin:spaces/assemblies.adoc#_assemblies_types[Assembly types]. -For creating a new process type: +== Manage process types -. Sign in as administrator -. Go to the Processes section in the sidebar -. Click on the Process types link in the sidebar -. Click on the "New process type" button -. Fill in the form +To access the process types list, click the "Manage" button on the top right of the page, and click the "Process type" menu item. -image:spaces/processes/process-types-admin-backend.png[A screenshot of the back-end showing the button to create a new process type,title="Create a new process type in the back-end"] +image::spaces/processes/process_types_list.png[Backend process types menu item] + +== Create a process type + +Click the "New process type" button on the top right of the page. + +image:spaces/processes/process_types_form.png[Process type creation form] .New participatory process type form: General information +[cols="20h,10h,~"] |=== |Field |Type |Description |Title |Required -|Title of the participatory process type. For instance, "Consultative". +|Title of the participatory process type. |=== -== Add process type to existing processes - -It's possible to add a process type to existing processes. Edit the process, and select the process type under the section labelled Other. +== Add process type to a process -image:spaces/processes/process-types-edit-process.png[A screenshot of editing an existing process to add a process type,title="Add process type to an existing process"] +To relate processes to process types, in the edition page of a process, select the process type under the section labelled Other. -== Process type filter +image:spaces/processes/process_types_edit_process.png[Choose a process type when editing a process] -In the front-end if there is at least one Process Type defined, a filter shows, allowing filtering of Processes. +== Filter by process types -image:spaces/processes/process-types-front-end.png[A screenshot of the front-end showing a filter for Process types,title="Front-end filter for Process Types"] +If there is at least one process type defined and related to a process, a filter is displayed at the left of the processes list +in the participant interface, allowing filtering of Processes. +image::spaces/processes/process_types_filter.png[Process types filter in the processes index]