We've added this to the admin UI design backlog, but with lower priority since it isn't a Navigation Stable blocker and no core modules need 2nd level items. The first idea was implementing a drop-down, but we are not sure if that's really the best UI pattern based on the problems it should solve. Also in the future we’ll need to evaluate if we want to keep dividing the drop down from the right sidebar on entities as two different things, and if so define clear rules.
Changing the priority to Minor for now.
Closing as duplicated as it turns out there was already an issue for it 📌 Run a set of user interviews to inform Starshot marketing Active . I've moved your updates to the other issue. Thanks @zoocha will!
Updating issue summary with some more info provided by Will on the duplicated issue.
Marking as fixed and adding credits.
The resulting work can bee found here: https://www.drupal.org/node/3469446 → .
Updating a part of the credits. The Acquia work on this still need to be added.
Also marking as fixed since this has been published [#3461868].
Adding latest designs for the Top Bar as a reference.
Adding some screenshots to make it easier for designers to understand the needs and current situation.
Adding 📌 Evaluate if the Top Bar entity title needs to show extra Active as a should to have.
Adding 📌 Evaluate if the Top Bar entity title needs to show extra Active as a nice to have.
> This already sounds like a non-trivial special case.
> My suggestion would be to just focus on regular entity routes here.
If that's going to be complicated, agreed that spinning off another issue is a better approach instead of trying to solve all the things here.
> I guess one question is whether canonical pages and edit/delete pages should both just show the title or something else.
We are now adding helpful info into the Title itself, like prepending the "Edit" to the entity Title. In an ideal world this contextual / extra info should be communicated with UI elements instead of keep pushing things into the only places we had available years back. So this "you are editing" context could be communicated with visual elements assigning to them the appropriate visual relevance. I'd recommend solving as much as we can with new UI elements, even if we have to come up with them. I've created 📌 Evaluate if the Top Bar entity title needs to show extra Active to work on that on a follow-up.
What @amateescu said :)
All the early explorations we did trying to improve the workflow with Workspaces showed that we need to think about several existential interactions and UIs beyond the top dialog. That's why we kept this as "it only triggers the existing dialog" so we can get Navigation to Stable soon and not get into a way longer discussion that will block Navigation.
We just discussed this issue on Slack with @lauriii and @plopesc, and agreed on the following direction about the Title shown:
- If it’s an entity, Top Bar should show the entity’s Title
- If it’s a view, it should show the views's title. But only on the front-end because it needs an edit button (not on the admin People page for example)
I'd try to unblock this issue as much as we can trying to get the title right and then open follow-ups for improvements for the other info like the ones @berdir was suggesting. Since this is still experimental, that can be refactored an improved afterwards.
penyaskito → credited ckrina → .
+1to use experimental if that has an effect. I would assume everything related to XB is experimental until XB is stable
I think it makes sense to hide it given the stability of the Navigation module at this point. Not sure how, though.
Removing old list.
This is ready for implementation.
Adding design issues and prioritize component implementation issues.
Ready for implementation.
Ready for implementation.
Ready for implementation.
Opening again because the designs need to be updated to remove email&phone.
This is ready to implement.
Adding credits and marking as fixed.
I saved without refreshing the issue and lost some data. Adding them back.
I saved without refreshing the issue and lost some data. Adding them back. @balintbrews I can't assign the issue back to you.
I saved without refreshing the issue and lost some data. Adding them back. @boulaffasae I can't assign the issue back to you.
I saved without refreshing the issue and lost some data. Adding them back.
I saved without refreshing the issue and lost some data. @matthieuscarset I can't assign this back to you.
Figma link added.
Figma link added.
Figma link added.
Figma link added.
Adding the first round of issues to create components for Experience Builder.
Adding some more info for the implementation.
Adding credits to @jwitkowski79 and @Alyciamjones for the designs.
ckrina → created an issue. See original summary → .
Adding credits to @jwitkowski79 and @Alyciamjones for the designs.
Tagging with "Experience Builder".
Tagging with "Experience Builder".
Moving to fixed to create the implementation issue.
Moving to fixed to create the implementation issue.
Moving to fixed to create the implementation issue.
Adding some more details for the implementation on bigger screens than 1440px.
Agreed that they perform the same task nowadays and it's confusing. Keeping a Shortcuts menu doesn’t make a lot of sense:
- If clients want an specific project menu, they can create one and place it there. AFAIK even per role.
- If they really want Shortcuts, this menu is confusing because doesn’t behave as users expect.
From ours tests with Navigation, it was clear most users understood “Shortcuts” as “own”(per user) items or customizable per role, but also it’s supported by @pcambra's research in 🌱 Improvements on Shortcut module Active (His research also shows other improvement the Shortcuts module needs and that I would love to get done eventually).
So agreed on having a real “most visited” or “favorites” feature, as a long hanging fruit in the next months. Meanwhile, I’d disable the Shortcuts module.
Moving to RTBC to +1 this, but I think the MR shows a conflict that will need to be resolved.
pameeela → credited ckrina → .
pameeela → credited ckrina → .
Fixed ul markup
Moving to fixed to create the implementation issue.
Adding 📌 Adjust how Help link and Content links are removed from the Administration menu for the Navigation bar RTBC as a should have.
Just to be sure things don't get confuse: the only "hero" is the one in the homepage. The rest are "featured images" that take the full grid.
To be more specific, this is the Featured image:
And this is the Hero:
On a styling/grid perspective you can see they take a completely different number of columns. Not sure for which of them this issue is for, but they should be treated different.
pameeela → credited ckrina → .
This is ready to be worked on since the designs are finished in 📌 Create designs for Project & Case Study content types within Olivero Active .
Marking this as fixed since it's been approved. Adding the Figma link on the summary for an easier implementation.
pameeela → credited ckrina → .
Designs are ready. Updating file and issue status.
Updated what Stable release means.
Removing fixed issues! :D
✨ Provide Config Action to add new blocks to navigation from recipes Active
Adding the "Drupal CMS release target" to see if we could hopefully get to it.
Adding the "Drupal CMS release target" to see if we could hopefully get to it.
Adding the "Drupal CMS release target" to see if we could hopefully get to it.
Adding the "Drupal CMS release target" to see if we could hopefully get to it.
Adding the "Drupal CMS release target" to see if we could hopefully get to it.
Adding the "Drupal CMS release target" to see if we could hopefully get to it.
Also adding Navigation stable blocker
Also adding Navigation stable blocker
Adding the "Drupal CMS release target" to see if we could hopefully get to it.
Adding the "Drupal CMS release target" to see if we could hopefully get to it.
When WASM was the main testing tool, we decided we'd remove the step to set the user email and password to reduce the number of screens, as Adam says. But since that won't be the testing tool and there might be other reasons to ask for the email, I doubt we'll skip this step in the foreseeable future. Assigning to @pameela to validate this issue can be closed.
Added parent 📌 New Toolbar Roadmap: Path to Beta & Stable Active .