Add breadcrumb to the admin site pages

[hishamco]

We need to add breadcrumb to the admin site pages, because I find it only in OrchardCore.Settings/Admin/Culture.

Breadcrumb is very handy in the navigation between hierarchy of pages

[hishamco]

It could be before the page title

or in the nabar

[hishamco]

I like the 2nd one 👍

[matiasmolleja]

I like the idea of a breacrumb. I would prefer the first one. The top bar could be a zone where modules could add buttons or dropdowns. Examples: The tenants module could add a list of tenants to quicky switch to one of them, the users module could add a list of recently edited content items etc...

[deanmarcussen]

Looks great, I like the idea of a breadcrumb as well.

What does it look like when editing content?

Would really like to have navigation back to the parent content items when editing lists, especially when they are recursive.

I'm with @matiasmolleja on the first one, top bar should be free and should be a zone to put buttons and dropdowns into.

I assume it's a zone? Below top bar and above Messages

[hishamco]

What does it look like when editing content?

This is not related to the content, so nothing show up on editing content. It could be static or dynamic.

I'm with @matiasmolleja on the first one, top bar should be free and should be a zone to put buttons and dropdowns into.

No problem .. I love the community folks opinions unless it's incorrect 😄, your thoughts @sebastienros to finish this and start working on it

[EternityTeam]

This is a good improvement, or we can provide tabbed style management to improve efficiency

[hishamco]

My idea at the beginning is basically to make the breadcrumn static but moving this to dynamic may not in plan of Orchard Core 1 RTM, so the decisions to the PM 😊

[sebastienros]

My only comment is that we need a well defined location in the template where to place them. And each page is responsible for building the hierarachy.

[hishamco]

My only comment is that we need a well defined location in the template where to place them. And each page is responsible for building the hierarachy.

That's why I preferred the navigation bar on because we already have a section on TheAdmin theme layout

[hishamco]

@sebastienros if it goes to the backlog, I think we need to remove the breadcrumb from the culture settings page for now

[sebastienros]

This is how it looks like in CraftCMS. They have it in the header, like your second suggestion. And the title is also move in the header. We can do it easily, and provide named zones for these. Including the side actions.

The only thing we'd change from Craft is to be able to show/hide the sidebar. And the account information is moved on the left of the header. The sidebar goes at the bottom when the screen size is small. The login information is accessible when you expand the menu. The logo is part of the menu, so only visible if the menu is expanded.

I'll setup some contest for all of you to show some mockups with sidebar/header. The prize is my eternal respect.

[hishamco]

If we agreed to do it above, we can make of use the nav section that's already there in TheAdmin layout, but my concern now is to remove the breadcrumb from the cultures page now

[agriffard]

Breadcrumbs are useful when there are multiple levels of hierarchy.

Ex:

• When you edit a content item, display a parent link to go the content items of the content type.
• When you edit a content item with a type that has a ListPart, display a parent link to go to the page that lists all the items contained by this ListPart.
• More generally, when you edit any object (DeploymentStep, Index, Query, Role, User, Widget), display a parent link to list that allows to manage all of them.

See what is already done for Workflows.

[agriffard]

Currently, it looks like this:

We could wrap every breadcrumbs by a <zone name="Breadcrumbs"></zone> and then decide where we want to place it in the admin Layout: Leave it above the content like it is right now or put it next to the title.

Here is how it would look like in the top navbar if we remove the grey background:

[hishamco]

I like the first option because it will not overlap with the login status. One thing you can add if we expose the Separator as a property on tag helper, so anyone can customize it

Great work @agriffard