Context Navigation

Changes between Initial Version and Version 1 of Ticket #64596, comment 7

initial	v1
2	2	I'll revert [61602] before beta1 so we don't have this landing under time pressure.
3	3
4		I also want to walk back my comment #5 a bit, I didn't mean to jump ahead and suggest we should lock in flat single-namespace names like core/get-post right away either. @justlevine is right that we should have a real conversation about what good naming looks like holistically before committing to any pattern in core.
	4	I also want to walk back my comment https://core.trac.wordpress.org/ticket/64596#comment:5 a bit, I didn't mean to jump ahead and suggest we should lock in flat single-namespace names like core/get-post right away either. @justlevine is right that we should have a real conversation about what good naming looks like holistically before committing to any pattern in core.
5	5	I think @justlevine raised some really compelling examples of existing WordPress APIs that already use nested slug fragments (hierarchical post types, REST subroutes like revisions, the Rewrite API, hooks, etc.), and those are worth weighing alongside @jorbin's consistency concerns. Both perspectives have a lot of merit here.
6	6	I love the idea of @justlevine and @jorbin syncing up to share context on the prior discussions, and would love to participate. I think that could save us a lot of back-and-forth and help us land on something we're all happy with.