This proposal has been accepted to be implemented in the main repository. Check for updates in the comments

This proposal is affected by the redesign process and will be used as feedback for the design team.

Improve frontend-design of participatory texts

Main repo (accepted)

Romy Grasgruber-Kerl 14/06/2021 11:23

Is your feature request related to a problem? Please describe.
The use of participatory texts is currently not intuitively understandable for participants (necessitiy of mouse-over to see options to interact is confusing for some). UI-Features that increase the motivation to contribute and interact immediately after accessing the participatory texts site are missing.

Describe the solution you'd like
We want to improve the frontend UID as suggested in the following figma: https://www.figma.com/proto/KHwovctNW44WbnVmGWyLin/decidim-%2F-textarbeit-improvements?node-id=225%3A1849&scaling=min-zoom&page-id=225%3A552 (interactive)

By making the possible tasks visible on first level we want to increase the clarity of the platform, in order to make participation easier.
By showing comments/activities/avatars of other participants, we want to increase their motivation to contribute and to interact.

Describe alternatives you've considered Of course various reflections until we came to this proposal, but nothing worth mentioning. Except of one small feature, that we still consider: Showing avatars of participants on first level next to paragraph (up to a certain amount) could give some good first impression of ongoing interaction.

Additional context

Status Quo to compare: https://text.decidim-austria.org/processes/textarbeit/f/12/ (in german)
We are planning to improve backend (import of texts) as well - will keep you posted as soon as we do have concrete suggestions.

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

Funded by

netidee - https://www.netidee.at/ (Foundation that funds open source projects in Austria.)

Filter results for: Funding available

Comment

Liked by Pauline Bessoles and 10 more

Liked by

Pauline Bessoles

Lars Kaiser

Nil Homedes

Anthony Smith

Pau Parals

Olivier Schulbaum

Lucien Langton

Nadja von Ballmoos

Javier Giner

Ruth Cheesley

Platoniq

Comment details

Fingerprint

The piece of text below is a shortened, hashed representation of this content. It is useful to ensure the content has not been tampered with, as a single modification would result in a totally different value.

Value: de1c32f3618956b1f7de9a8267302bb3493e6bee1ad2092bc84a70c0e2506268

Source:

{"body":{"en":"<p><strong>Is your feature request related to a problem? Please describe.</strong><br>The use of participatory texts is currently not intuitively understandable for participants (necessitiy of mouse-over to see options to interact is confusing for some). UI-Features that increase the motivation to contribute and interact immediately after accessing the participatory texts site are missing.</p><p><strong>Describe the solution you'd like</strong><br>We want to improve the frontend UID as suggested in the following figma: <a href=\"https://www.figma.com/proto/KHwovctNW44WbnVmGWyLin/decidim-%2F-textarbeit-improvements?node-id=225%3A1849&amp;scaling=min-zoom&amp;page-id=225%3A552\" target=\"_blank\">https://www.figma.com/proto/KHwovctNW44WbnVmGWyLin/decidim-%2F-textarbeit-improvements?node-id=225%3A1849&amp;scaling=min-zoom&amp;page-id=225%3A552</a> (interactive)</p><ul><li>By making the possible tasks visible on first level we want to increase the clarity of the platform, in order to make participation easier.</li><li>By showing comments/activities/avatars of other participants, we want to increase their motivation to contribute and to interact.</li></ul><p><br></p><p><strong>Describe alternatives you've considered </strong>Of course various reflections until we came to this proposal, but nothing worth mentioning. Except of one small feature, that we still consider: Showing avatars of participants on first level next to paragraph (up to a certain amount) could give some good first impression of ongoing interaction.</p><p><strong>Additional context</strong></p><ul><li>Status Quo to compare:<a href=\"https://text.decidim-austria.org/processes/textarbeit/f/12/\" target=\"_blank\"> https://text.decidim-austria.org/processes/textarbeit/f/12/</a> (in german)</li><li>We are planning to <strong>improve backend </strong>(import of texts) as well - will keep you posted as soon as we do have concrete suggestions.</li></ul><p><br></p><p><strong>Does this issue could impact on users private data?</strong><br>No.</p><p><strong>Funded by</strong><br></p><p><strong>netidee - https://www.netidee.at/ </strong>(Foundation that funds open source projects in Austria.)</p>"},"title":{"en":"Improve frontend-design of participatory texts "}}

This fingerprint is calculated using a SHA256 hashing algorithm. In order to replicate it yourself, you can use an MD5 calculator online and copy-paste the source data.

You are seeing a single comment

View all comments

Pau Parals 18/12/2024 16:05

great proposal!
I have some doubts:
1- i understand that it will not be possible to import a document, but that you will have to copy and paste. this allows flexibility when assembling the structure (something that before we could not and had many problems). although i am afraid that city councils or administrations, with texts of more than 8 pages, should be able to have an automated process (perhaps for a second iteration).
2- i miss a global suggestion. there are types of participatory text processes, where it is allowed to make an ‘amendment to the whole’ and propose a new text. could it be included? we should give the option to upload a document.
3- the management of acceptance/rejection, the whole frontend, not the backend. in the backend, i understand that we would manage the version history. i.e. a moment where we could say ‘publish the document with the accepted and rejected suggestions’, and be associated with a version control to recover the old versions? i think it would be a good solution for this management to be in the backend, while the acceptance/rejection would be in the backend.

Carol Romero 15/01/2025 10:25

@paarals thanks for your comments! Regarding your doubts:

1- i understand that it will not be possible to import a document, but that you will have to copy and paste. this allows flexibility when assembling the structure (something that before we could not and had many problems). although i am afraid that city councils or administrations, with texts of more than 8 pages, should be able to have an automated process (perhaps for a second iteration).

Document import has been a pain point from the beginning. We believe copy-pasting is the simplest solution for now. If importing becomes a real need in the future, we can always implement it later.

2- i miss a global suggestion. there are types of participatory text processes, where it is allowed to make an ‘amendment to the whole’ and propose a new text. could it be included? we should give the option to upload a document.

This is something we’ve considered, but since we need to prioritize, we’d leave it for future iterations.

3- the management of acceptance/rejection, the whole frontend, not the backend. in the backend, i understand that we would manage the version history. i.e. a moment where we could say ‘publish the document with the accepted and rejected suggestions’, and be associated with a version control to recover the old versions? i think it would be a good solution for this management to be in the backend, while the acceptance/rejection would be in the backend.

That’s exactly how it works. Approving/rejecting suggestions will be managed on the frontend, while consolidating text into different versions will happen in the admin panel. We’re starting to draft the user stories, which will specify how this part will function in more detail.

We look forward to discussing the technical details more in depth with you -Pokecode- next week!

Essential

Preferences

Analytics and statistics

Marketing

Improve frontend-design of participatory texts

Liked by

Please log in

Cookie settings

Essential

Preferences

Analytics and statistics

Marketing

Improve frontend-design of participatory texts

Share

Liked by

Confirm

Please log in