>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3480979. --> Reported by: [traviscarden](https://www.drupal.org/user/236758) Related to !371 >>> <p>tl;dr: Add a local task to node paths, e.g., <code>node/1</code>, pointing to the corresponding XB UI path.</p> <p>The <a href="https://www.drupal.org#original-report">original issue report</a> below reflects an inadequate understanding of the intended UX of the Experience Builder UI, rendering it essentially obsolete. One valuable takeaway was identified though, which is the addition of a local task (tab) to node paths to improve discoverability and UX until the ultimate design is implemented.</p> <h3 id="original-report">Original report</h3> <h4 id="overview">Overview</h4> <p>The current Experience Builder node path breaks a clear convention with other node operations by putting <code>xb</code> at the beginning rather than the end:</p> <ul> <li><code>/node/{nid}/edit</code></li> <li><code>/node/{nid}/delete</code></li> <li><code>/node/{nid}/revisions</code></li> <li><code>/xb/node/{nid}</code></li> </ul> <h4 id="proposed-resolution">Proposed resolution</h4> <p>I propose changing the node path to <code>/node/{nid}/xb</code> and possibly adding a local task (tab).</p> <p>Thinking beyond nodes, @longwave suggests this:</p> <blockquote><p> Perhaps this should be up to each entity type to specify the path where XB lives for it. We could probably borrow layout builder's approach of</p> <p> <code>$template = $entity_type-&gt;getLinkTemplate('canonical') . '/layout';</code></p> <p> replacing that with <code>/xb</code> or similar for all entity types that are opted in via some criteria. </p></blockquote> <h4 id="ui-changes">User interface changes</h4> <p>Possibly adding a local task to node paths. Probably nothing for the rest of the proposal.</p>