Navigation editable "Per Site" or ability to provide dynamic "Site Parameter"

[svonlanthen]

What are you trying to do?

When i have a Project with three languages, I want the CpNav stay in the currently active Site.
Otherwise it's very bad UX for editors because they always fall back to the default site, mix up the translations and so on.

Manual CpNav Item:
/admin/entries/section_pages (when i would add ?site=de here, it would always be the same site)

Plugin Navigation Item -> Works fine and adds the site-Parameter fine, based on current active Site:
/admin/navigation?site=de
/admin/navigation?site=fr
/admin/navigation?site=en

What's your proposed solution?

Best solution:
Ability to set a placeholder variable {current_site}, so that i can create Manual Nav-Links like /admin/entries/section_pages?site={current_site}

Other solution:
Make the CpNav editable "per site", as it is the default behavior in Craft

Additional context

Maybe I don't get how it works in a multi-site-environment.
For many people the USP of CraftCMS is it's core multilanguage functionality - So for the clients/editors it's super important that the CpNav also works "per Site"

[engram-design]

Yeah, it's a good point we probably need to make either the navs or the layout per-site!

[engram-design]

So, diving into this one - I think we're at odds of addressing things properly, as you're asking for two slightly different things.

The CP sidebar is install-global. "Site" in the CP is almost always page-local:

• Entries / Categories / etc. have a site menu or ?site=
• That choice affects that screen’s element queries, not a control-panel-wide mode
• There is no durable “I am in German CP now” that the whole chrome (including #nav) is built around

So we're asking for two similar but different things here.

Click-through context — “I was on ?site=de, I click a sidebar link, I land on primary again and mix up translations.”
Different nav per site — English shows X, German shows Y / different labels / different manuals. That's probably not something we're going to implement.

So as of 6.0.0-beta.1 using the placeholders like {site} (Current Site ID) or {siteHandle} (Current Site Handle) in manual links is supported, and hopefully that'll help your case here.