Context Navigation

Changes between Initial Version and Version 1 of Ticket #61040, comment 74

initial	v1
12	12	Plugin authors wouldn't have to be doorway experts. They could rely on core to provide an accessible and predictable doorway to all users. Plugin authors could decide what sign goes on the door ("Open", "Get Started", "Configure", etc.) and what happens once you pass through the door (jump straight into using the plugin, start an onboarding wizard, configure a settings page, etc.).
13	13
14		And if the plugin author is unaware or chooses not to take advantage of the doorway provided by core, then the door remains locked with a simple "Activ~~ated~~" sign on the door, just like it does today.
	14	And if the plugin author is unaware or chooses not to take advantage of the doorway provided by core, then the door remains locked with a simple "Active" sign on the door, just like it does today.
15	15
16	16	In this sense, the doorway is a progressive enhancement offered to plugins, but not forced upon them. Through documentation and developer outreach, we can provide a recommended workflow that can be adopted over time, gradually replacing the unpredictable teleporters with predictable doorways that restore user choice.