Propose new features

Fingerprint

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

Value: 869293af5c8cb3ac69631a0a0446848fb5af1199bf9d3e6bf15c38d247c035c0

Source: {"body":{"en":"<p><strong>Is your feature request related to a problem? Please describe.</strong><br>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.</p><p><strong>Describe the solution you'd like</strong><br>We propose 3 improvements to the meetings components:</p><p>Divide the default sorting of proposals into 2 categories:</p><ol><li>if it's in the past, order them by start_date in ascendant mode (user sees first what happened more recently).</li><li>If it's in the future, order them in descendent mode (user sees first the next coming event first).</li></ol><p>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).</p><p>In addition, we would like to also improve the visualization these two types of events (past and future) by adding the <em>success</em> and <em>muted</em> classes to the <em>card--meeting</em> so the user has quick visual clue on what's more relevant.</p><p>This would look like this:</p><p><img src=\"https://user-images.githubusercontent.com/1401520/115354661-2adc4600-a1ba-11eb-8b29-af37874b706f.png\"></p><p><strong>Describe alternatives you've considered</strong><br>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).</p><p><strong>Additional context</strong></p><p>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:</p><p><img src=\"https://user-images.githubusercontent.com/8806781/110646272-081c4200-81b7-11eb-9a19-ae3ed862941b.png\"></p><p><strong>Does this issue could impact on users private data?</strong></p><p>NO</p><p><strong>Funded by</strong><br></p><p>Yes, Som Energia &amp; Platoniq</p>"},"title":{"en":"Order and visualization of meetings"}}

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. ×