New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contextual Help System MVP #3973
Comments
Regarding the admin part of things, should we create a new section "Help" under settings? In this page, we would have different blocks: "Welcome notification", "Help: XXX space" - etc Regarding the redesign of (current) banner and discarding it, I'm thinking about it but not getting to any conclusion. I understand that this element was a quick solution and we may feel that we need to improve it but - does it have any problem? ;) About discarding it, I think it would be good to allow for it, but I can't come up with any simple solution to provide access to it once you have closed. I don't like what I think of (ie. creating a help button near the top, or a closed tab fixed to the bottom...) because I feel will be too hidden. And since I don't think the current banner does not imply any design/UX problem, and experience (people using it) tells us that it is working, should we just don't touch it? Do we want this announcements for spaces as something different from the current banners? (probably the idea is yes - but I refer again to the consistency issue: would it be recommendable to have two different but mostly similar systems?) What maybe can be thought of is to provide more flexibility to where banners can be shown? Sorry to open the debate again! |
Hi @furilo, I've updated the issue as agreed yesterday during the meeting, Let's start by designing the admin interface so @decidim/lot-core can move forward. |
Questions:
|
yes, you convinced me the other day that is better in terms of usability if we keep the same design across the platform ;-)
ok, what we have in mind is managing the contextual help at 2 different levels:
cc/ @decidim/product |
@carolromero about the sections in the full help page, we'll have one for participatory space and one more to other content? Should the admins be able to create more sections? |
At #4136 it seems that it only applies to processes, is this also for assemblies or just processes? |
Hi @oriolgual, ok I'm picturing something like this (this is only a quick mockup): Therefore, I'd say that by default you will have a set of preloaded sections, and depending of the participation spaces you are using, you can publish/unpublish them. So, admins should be able to create, edit, publish, unpublish more sections. Note in the example I've posted that we want also to display the intro text of each participation space as banner/announcement in the general index. |
Ok, let's recap to be on the same page. We won't finally use the Process Intro proposal with the three content blocks since we are rethinking the whole "header/phases/menu/announcements" combo in this issue #4230. #4136 was an exploration that has been finally discarded, so to avoid confusion, I will close and remove this issue from the Contextual Help System EPIC. cc/ @decidim/lot-px @decidim/lot-core @decidim/product |
This is a proposal for the admin screen to manage the new help system to offer banner-like announcements in main sections (as noted by @carolromero, announcements for specific spaces remain where they are now).
Comments? |
Hi @furilo, |
Just to double-check, in the help page we will show the intro text + the extended text, correct?
Yes, I'd start with that.
|
Btw, designing #4304 I just realized that we could have subsections in this new menu option: Help system |
|
@josepjaume regarding your proposal of improving static pages #4338 , take into account that we need also the design that @furilo has been working on. |
@decidim/lot-core do you need markup for this? |
I consider this closed since #4470, but without predefined content, as it hasn't been provided to us (except for the welcome notification). Contextual help content applies to the whole of a participatory space and the same text is visible on the individual participatory space, as well as the index page. |
This is an MVP for the EPIC #3712
Tasks
instancename
?The text was updated successfully, but these errors were encountered: