Robert J. Lang

Ah, thanks for the very clear explanation. I'd not realized that Layouts can _create_ menu router paths, and indeed, that changes everything (or at least, it changes the basis of...

Layout's path-handling can be confusing (at least, I'm still trying to fully wrap my head around all the scenarios). Beginning with the fact that when a module and a layout...

@herbdool, I've started working on the roadmap for Layout Wildcard, putting some introductory comments and explanation into [this issue](https://github.com/backdrop-contrib/layout_wildcard/issues/19). They might be helpful. The View scenario you're describing is one...

All good points. I just wanted to capture the assertion so it can be addressed in its own issue rather than sidetracking the original issue. Will leave it to @jenlampton,...

> I always considered that a feature: assigning a special layout per path to only one node with something like "node/11". Is it also a feature that if you do...

I think the current situation is not ideal, so yeah, I guess that means "fix." I don't (yet) have a clear idea of what should be done—hence the opening of...

@findlabnet, If you want to override the layout used for path "node/1" but still display the content of node 1, you would: * Create your layout with path `node/%` *...

In looking at this again, I see that there's already some validation in place for this sort of thing. If you enter `node/1` for the path, this warning message appears:...

> I'm in favor of a core integration. Personally, I'd prefer the new feature as an option. I've created a PR that implements it as an option (set on the...

> I'd like it to be the default and only option.... I personally would also lean this way, but we've received at least one other vote for "make it an...