-
Notifications
You must be signed in to change notification settings - Fork 745
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
New Quick Add Module option from the edit bar #4305
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this nice and clean approach. WOuld "QuickAddModule" be a better name than AddModuleNow ?
I tweaked the wording a bit. In the end there is not much wording people see. But what they see should be clear. Maybe the icon should reflect the "quick part" by having a lightning bolt in it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, this looks great
Dnn.AdminExperience/EditBar/Dnn.EditBar.UI/Items/AddModuleNowMenu.cs
Outdated
Show resolved
Hide resolved
Dnn.AdminExperience/EditBar/Dnn.EditBar.UI/Items/AddModuleNowMenu.cs
Outdated
Show resolved
Hide resolved
Dnn.AdminExperience/EditBar/Dnn.EditBar.UI/Items/AddModuleNowMenu.cs
Outdated
Show resolved
Hide resolved
Dnn.AdminExperience/EditBar/Dnn.EditBar.UI/Items/AddModuleNowMenu.cs
Outdated
Show resolved
Hide resolved
Dnn.AdminExperience/EditBar/Dnn.EditBar.UI/Items/AddModuleNowMenu.cs
Outdated
Show resolved
Hide resolved
Dnn.AdminExperience/EditBar/Dnn.EditBar.UI/Items/AddModuleNowMenu.cs
Outdated
Show resolved
Hide resolved
Should we convert the EditBar into a PersonalBar menu too? It is cumbersome to have 2 bars occupy the entire screen |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, but like discussed, would be nice to move the buttons around to better isolate this new feature from the existing buttons and maybe adding a separator for clarity.
Aside from some of my number of clicks required concerns_ this is a nice proposal to avoid the floaty thingy. This also uses a lot of real estate in the Edit Bar and I have concerns about long module names and content names. |
What is the strategy for tablet/mobile view? While I would argue very few administrators do or should be editing their site on mobile (let alone adding a module) we should make sure that it still displays well. The current UI doesn't respond very well on mobile as it is and the new controls shown above looks to double the amount of content being displayed. I'm also concerned for a long list, maybe limit the size and use scrolling instead. Or have it so only 'favorite' modules display. From a style perspective I'd like a little extra padding in each list-item, both horizontally and vertically. I almost like the idea of starting with a lightning bolt icon using the same square icon button styles, and once clicked it expands to show the list of modules and current selected module. It then also reveals the pane you want to assign the module to and the confirm action button. |
Yeah it currently uses floats to make the close button right and the rest left. Maybe at the base minimum we make this display: flex; and overflow-x: scroll so it's at least usable. I tried it for a little bit and there was other issues with it... |
Is this going to be an opt-in or opt-out feature? I think this is a great idea, but think it should be turned off by default until it is a little bit more refined. I've seen a couple good questions in this thread that don't appear to be addressed yet.
Not sure if any of these concerns should hold the PR, which is why I think it should start as an opt-in feature for a couple release cycles. |
Well, getting to the actual edit bar now is not really accessible 😄 For accessibility the other offering of bringing back the insert buttons in the panes would be accessible (you can tab to them and activate them and the popup has focus on the search field) however from there it is again not accessible because you can actually select your module by keyboard. That being said, I think we can improve that and it should not hold this PR. I would personally prefer if this is an opt-in feature rather than an opt-out feature. |
Great idea! 1- the list of modules could be in "autocomplete" mode so that it is possible to type also a part of the module name and filter the list 2- there could be a second list (or alternatively a part of the single list, with a divider in between) that shows the saved module templates: in practice, adding a module from a template, the effect would be to add that type of module and then launch the import via IPortable (provided that the module supports it, but if there is a template for that module is obviously so). As a corollary of this suggestion in the Export action of the module you would add a request "[ x ] add to templates list". 3- from admin, have the possibility to show or not a module or a template according to the user role. Obviously admin "sees all", while some users editors could for example only add templates pre organized by admin, or only certain types of modules. |
The current experience to add a module to the page is (1) cumbersome and (2) brittle. It's cumbersome because you need to wait for the popup and search for the module and then drag it to the place you want. This takes quite some time. It's brittle because any error in JS from the module or skin and the user can't add the module at all.
This PR adds a quick module add option right in the edit bar not unlike we had back before the Personabar.
The addition is almost instantaneous reducing time to add a module to a page. It is also less brittle as it doesn't require popups or dragging.