Propose new functionalities for Decidim software
#DecidimRoadmap Designing Decidim together
Is your feature request related to a problem? Please describe.
When visiting a meetings component it is not clear whether an event has already taken place or is in the future. Furthermore, the order of events is always the same, sorted by start_date from in reverse order (this change has been done recently), meaning the further in time an event happens, the sooner appears in the list.
Describe the solution you'd like
We propose 3 improvements to the meetings components:
Divide the default sorting of proposals into 2 categories:
- if it's in the past, order them by start_date in ascendant mode (user sees first what happened more recently).
- If it's in the future, order them in descendent mode (user sees first the next coming event first).
This casuistic raises the question on what happens when the user want's to see all events, past and future. In this case I'd maintain the described order and put the future events in top ordered ASC and then the past ones ordered DESC (technically, this would mean to merge to queries to sort them differently).
In addition, we would like to also improve the visualization these two types of events (past and future) by adding the success and muted classes to the card--meeting so the user has quick visual clue on what's more relevant.
This would look like this:
Describe alternatives you've considered
Instead of using colors to differenciate the past and future meetings, use a separator element between them (for instance a bar or an hr html element).
Additional context
The third improvement is to add images to the meeting card (as already happens in proposals). This just uses the current system of attachments and, if one of them is a photo, uses it as a card-image:
Does this issue could impact on users private data?
NO
Funded by
Yes, Som Energia & Platoniq
Related images
Report inappropriate content
Is this content inappropriate?
6 comments
As a note, this proposal also includes these two in order to summarize all our desired improvements:
Add image to meetings
Add image to blog post cards in the list view
Conversation with Arnau
There is another solution which is to come back to radio buttons and show past OR future events but never together, This facilitates the navigation and the comprehension of the event list.
True, but that would break the overall design consistency with other component visualization? We might eve just get rid of the "show all" button to achieve the same thing.
Personally I don't mind having a "all" view, as long as it is not the default.
Conversation with Carol Romero
Hi there! We' ve been evaluating this and from our point of view the most usable solution is to add a sorting selector, as in other components. The parameters of this selector would be: newest and oldest. The participant then has full control over the combination of filters and display order. See https://imgur.com/9waO5W3
That said, we will have an opportunity to rethink the filter system as we saw in the redesign proposal. The current system does not satisfy all use cases.
Thanks for the answer but I think I have more doubts now.
First, you've said nothing about the code color for passed or future events, would you agree on having that?
Second, it seems a little confusing your solution to me. IE: the most important sort for the end user is to see the next coming meeting first (at least is what I think), in your proposal, would this means that we should show by default only the "future events" ordered by "oldest"? then if the user checks the "all" meetings, suddenly all meetings shown will be starting from the beginning of time, which seems like a weird user journey experience.
In your mockup you show a default "most recent" events, what that means? if we have one event per month during a whole year, should we order them starting at the one happening next year?
We are proposing here to have a "natural order" where you see events ordered according how close are to the current day. And as you say, we have an opportunity to rethink the filter system here, but precisely "oldest" and "newer" does not seem very helpful (to me).
Add your comment
Sign in with your account or sign up to add your comment.
Loading comments ...