User Stories Evolutius 2023/24
===

:::spoiler Template

Ref. DDP01 / DIT01

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

**Does this issue could impact on users private data?**
Ex. issues related with user's sign up/sign in process, verifications, invitations, sensitive data like email, IP addresses, etc.

**Acceptance criteria**
:::

# Lot 1 DDP
**Adjudicatària: Pokecode**

## Use page image as meta image for links preseeding
Ref. DDP07

**Is your feature request related to a problem? Please describe.**
When sharing a link from a Decidim platform on social media or a messaging app, a preview is generated. These previews are generated with pieces of information loaded from the page's source and called meta tags.

The code that generates these meta tags in Decidim is now quite old, it was written over 5 years ago. And as of now, the image that is used for a preview for any page within a space (a proposal, a meeting, a blog post, a budget project...) is the main image of the space itself.

**Describe the solution you'd like**
Make the image reflect the content a bit more, with fallbacks when images are lacking.

Here's a suggestion of which image to display for different types of content:

a meeting –> its card image
a blog post –> its card image
a budget project –> its card image
and since each of the above now support inline images in their description fields (as well as pages and accountability results), the first inline image could be used if there are no card images.

For user-generated content:

an initiative –> its first image
a proposal –> its first image
a meeting –> its first image
a user profile -> its profile picture (right now, showing the hero image)

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
[Metadecidim proposal](https://meta.decidim.org/processes/roadmap/f/122/proposals/16960)

**Does this issue could impact on users private data?**
No

**Acceptance criteria**

- [ ] Update the code responsible for generating meta tags to reflect the content accurately when sharing links on social media or messaging apps.
- [ ] Implement logic to use the card image associated with proposals, meetings, blog posts, and budget projects for the respective content type when generating the preview.
- [ ] Develop a mechanism to use the first inline image in the description field of pages when no card image is available for the preview.
- [ ] Configure the system to utilize the first image for initiatives, proposals, and user profiles when generating the preview for the respective content types.
- [ ] Handle cases where no card image or inline image is available by implementing a fallback image strategy to prevent confusion in the generated previews.
- [ ] Ensure backward compatibility of the solution to maintain consistency across the platform, especially for older content.

# Lot DIT

## Enhance the signature export system and PDF generation in Initiatives

Ref. DIT15

**Is your feature request related to a problem? Please describe.**
As an administrator, when I export the signatures file of an initiative, I encounter a format that is not useful to me, as there are columns that are unnecessarily repetitive or columns that appear with no information.

**Describe the solution you'd like**
When exporting the PDF with signatures, I want the file to, by default, display the following columns: Signature count, Nickname, Date and time. If additional personal data (Name and surname, Document number, Date of birth, Postal code) is collected, I also want it to be displayed.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**

Current PDF structure:

Desired PDF structure:
:::warning
todo
:::
**Does this issue could impact on users private data?**
It could, in the case that the collection of personal data is enabled.

**Acceptance criteria**
- [ ] When exporting the signature file for an initiative as an administrator, the default PDF format should display the following columns:

* Initiative title
* Initiative ID
* Initiative type
* Scope
* Start date
* End date
* Number of signatures
* Signature count
* Nickname
* Date and time

- [ ] If additional personal data fields are collected for signatures (Name and surname, Document number, Date of birth, Postal code), they should also be displayed in the exported PDF.
- [ ] The exported PDF should not include any unnecessary or empty columns.
- [ ] The exported PDF should have a clear and organized layout for easy readability.

## Allow the author/s of an initiative to manage meetings and blog posts from the frontend

Ref. DIT16

**Is your feature request related to a problem? Please describe.**
As an author or member of an initiative I want to be able to create meetings and blog posts in order

**Describe the solution you'd like**
Bring the management of the meetings component and the blog component to the frontend, allowing the author/s of an initiative to manage meetings without accessing the admin panel.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

**Does this issue could impact on users private data?**
Ex. issues related with user's sign up/sign in process, verifications, invitations, sensitive data like email, IP addresses, etc.

**Acceptance criteria**

## Enable the signing of an initiative without registration, solely through direct verification

Ref. DIT17

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

**Does this issue could impact on users private data?**
Ex. issues related with user's sign up/sign in process, verifications, invitations, sensitive data like email, IP addresses, etc.

**Acceptance criteria**

## Improve the usability of the digital signature process and reduce the number of steps for signing

Ref. DIT18

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
Improve the usability of the digital signature process and reduce the number of steps to two for signing. For registered users, only request additional data in a single step. For unregistered users, allow signature with direct verification in a maximum of two steps.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

**Does this issue could impact on users private data?**
Ex. issues related with user's sign up/sign in process, verifications, invitations, sensitive data like email, IP addresses, etc.

**Acceptance criteria**

## Enhance information flow in navigation and initiative creation

Ref. DIT19

**Is your feature request related to a problem? Please describe.**
Enhance information flow in navigation and initiative creation, ensuring participants understand what initiatives are and what they entail by providing preliminary informational layers or a navigation landing page for initiatives with highlights, recent submissions, or initiatives with pending signature collection deadlines.

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

**Does this issue could impact on users private data?**
Ex. issues related with user's sign up/sign in process, verifications, invitations, sensitive data like email, IP addresses, etc.

**Acceptance criteria**

## EV 01: Utilitzar la imatge del recurs com a meta imatge per a la previsualització d'enllaços
**La proposta està relacionada amb algún problema? Descriu el problema**
Degut a alguns canvis recents, com la possibilitat d'afegir imatges a reunions i entrades de bloc, o la possibilitat d'incrustar imatges en qualsevol camp de text des de la versió 0.26, podem esperar que cada vegada més recursos de la plataforma tinguin les seves pròpies imatges.

Al compartir un enllaç des d'una plataforma Decidim a les xarxes socials o en una app de missatgeria, es genera una vista prèvia. Aquestes vistes prèvies es generen amb peces d'informació carregades des de la pàgina i anomenades metatags.

Actualment, la imatge que es fa servir per a una vista prèvia de qualsevol pàgina dins d'un espai (una proposta, una reunió, una entrada de bloc, un projecte de pressupost...) és la imatge principal del mateix espai.

**Descriu la solució que t'agradaria**
Que quan hi hagi una imatge a un recurs (proposta, trobada, projecte, etc.) es mostri aquella imatge. Per exemple, si una proposta té una imatge adjuntada, es mostri aquella imatge a la previsualització.

Quan faltin imatges al recurs, s'hauria d'agafar la imatge superior a nivell jeràrquic. Per exemple, si una proposta no té imatge s'hauria d'agafar la imatge de portada del procés.

**Descriu les alternatives que has considerat**

**Aquesta proposta podria tenir algún impacte en les dades de les usuàries?**
No.

## EV 02: Unificar Scopes i àrees i poder definir tipus de scopes

**La proposta està relacionada amb algún problema? Descriu el problema**
Actualment el funcionament de Scopes i Areas es redundant i pot portar a confussió.

**Describe the solution you'd like**
Cal tenir en compte el legacy per evitar que es trenquin els sistemes de clasificació que s'han fet servir fins ara. (Veure aquest [comentari a GitHub](https://github.com/decidim/decidim/issues/3540#issuecomment-874637981))

Unificar arees i àmbits en un únic sistema de clasificació de contingut que mantingui la flexibilitat. La solució passaria per tenir un sistema de clasificació que permeti:
- Tenir diferents tipologies d'àmbits
- Dins d'un espai de participació, poder activar més d'un àmbit de difernt tipus alhora.
- Dins d'un component, poder

**Describe alternatives you've considered**

**Additional context**

**Does this issue could impact on users private data?**