Document high-level architecture decisions for extensions API
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3514033. -->
Reported by: [bnjmnm](https://www.drupal.org/user/2369194)
Related to !900 !182
>>>
<h3 id="overview">Overview</h3>
<p>We validated the ability to extend Drupal Canvas with the <code>canvas_test_extension</code> module, but this was achieved with proof of concept in mind and not necessarily how we intend to make these capabilities available long-term.</p>
<p>We should probably figure out what functionality should be offered, how to implement it, how to ensure it remains stable + provide good docs so the community can take advantage of these capabilities.</p>
<h3 id="proposed-resolution">Proposed resolution</h3>
<p>In <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/canvas/issues/3550161" title="Status: Closed (fixed)">#3550161: Extension plugins, UI, and initial browser APIs</a></span> we implemented the infra and updated the test extension for how this will work.<br>
This issue is for writing an ADR documenting those changes.</p>
<h3 id="ui-changes">User interface changes</h3>
<p>None.</p>
issue