Aquest lloc web fa servir cookies pròpies i de tercers per millorar l’experiència de navegació, i oferir continguts i serveis d’interès. En continuar la navegació entenem que acceptes la nostra política de cookies. Per a més informació consulta aquí.
DecidimFest 2019. Barcelona, Octubre 29-31 :: Participa al Call4Nodes! - -

Última activitat

Tipus
Resultats per pàgina:
  • 24 de Ago 10:36
  • Antti Hukkanen
    Nova proposta a Proposa noves funcionalitats
    User flow / guidance tool
    We have received lots of feedback about the complex navigational structure in Decidim. E.g. if the city has active budgeting phase in multiple processes, the users would first have to browse to processes => (possibly select a process group) => select a process => switch to the budgeting tab => authorize themselves (if required) => start the budgeting. In this case the users are not really interested in anything else but the budgeting phase and it would be better to guide them through the process with a simple flow. In this particular case the desired user flow would be something like this: - Require the user to login (needed for budgeting) - Require the user to authorize them with 1, many or all selected authorization method (needed for budgeting) - Select the budgeting component from the desired process (only displaying those that the user is authorized in for the budgeting action) - Do the budgeting - Repeat the budgeting for any other components the user is authorized in Also, in the budgeting phase, the user should not be shown the UI overhead links from the participatory space, i.e. the participatory space's header which shows its title, steps and sub-navigation. They are only interested about performing the budgeting in the desired process, so focus the user's attention to the actual budgeting. The same kind of process could be applied to any component out there, e.g. proposals/ideas. The most use cases we've had, there is always one active phase (proposal, budgeting, etc.) that the users are interested in at the given time. They come to the platform for that particular purpose and are confused when they have to browse through multiple different views in order to perform what they came to do. We actually tried to build a general module which would allow just this but quickly noticed it was pretty hard to implement this generally because of the way the internal functionality of the components is tied to the participatory space they are in. Basically we ended up creating a flow tool tied to the budgeting component which has its own routes for the budgeting component served by controllers that override the budgeting component's controllers. The overrides were required to hide the participatory space's navigational structure from the user. Other than that, this component could have been created more generally that would allow attaching it to any component out there.
  • 24 de Ago 10:11
  • Antti Hukkanen
    Nova proposta a Notifica una Bug (Errors o Incidències)
    After the user accepts the TOS, they are redirected back to the TOS page
    If the user has not yet accepted the TOS, they are asked to accept it before they can access any page. After they accept it, they are redirected back to the TOS page. Usability wise this is not ideal. Better would be to redirect the user back to the stored path, i.e. the last page they tried to access before they were asked to log in. The reason for this is that the stored page is overridden on every request, even when the user requests the TOS page where they are redirected to (served through the pages controller). SOLUTION: Skip the `:store_current_location` before action for ALL controllers in case the user is: a) Logged in b) Has not yet accepted the TOS This way the actually desired page would automatically be remembered as the TOS acceptance controller already redirects there.
  • 19 de Ago 20:24
  • Virgile Deville
    Nova proposta a Proposa noves funcionalitats
    UX simplification of initiatives for broader use cases
    Here is a list of small improvements that we are planning to make on Decidim's master : - Enable global scope selection and signature threshold - Admin option to disable promoting committee - Simplify initiative creation wizard when there is only one option available (1 type of initiative, 1 type of signature collection, only global scope signature threshold) Related Github issue here : https://github.com/OpenSourcePolitics/dev/issues/5
  • 19 de Ago 15:21
  • Mijail Rondon Viloria
    Nova proposta a Proposa noves funcionalitats
    Dashboard Comunitario
    Actualmente el dashboard de decidim sólo muestra el log de administración, sería bueno tener además de esa información, lo más reciente de la comunidad decidim así como avisos de seguridad y notificaciones de la disponibilidad de una nueva actualización. Colocar un RSS o alguna fuente de noticias de la comunidad también sería deseable, así como la posibilidad de notificar errores o solicitar soporte. Esta puede estar relacionada a otra petición que realizaba @OPS sobre las estadísticas de los usuarios de manera agregada en el dashboard.
Creative Commons License Web creada amb programari lliure.

Si us plau, inicia sessió

Has oblidat la teva contrasenya?

O