>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3545815. --> Reported by: [catia_penas](https://www.drupal.org/user/3725216) >>> <p>--- AI TRACKER METADATA ---<br> <strong>Update Summary: </strong>Enable Site and Page Specific Design System Metadata Overrides and Additions<br> <strong>Check-in Date: </strong>MM/DD/YYYY (US format) [When we should see progress/get an update]<br> <strong>Due Date:</strong> MM/DD/YYYY (US format) [When the issue should be fully completed]<br> <strong>Blocked by:</strong> [#XXXXXX] (New issues on new lines)<br> <strong>Additional Collaborators:</strong> @username1, @username2<br> AI Tracker found here: <a href="https://www.drupalstarforge.ai/" title="AI Tracker">https://www.drupalstarforge.ai/</a><br> --- END METADATA ---</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Make sure the design system can be overridden or added to by a specific theme. Needs to be done in a structured manner so that with overrides, its still possible to update the underlying design system metadata without conflicts. We will need 3 levels. Core metadata, Custom Code Overrides, Site Config Overrides. We need AI to know to priorities higher level (config overrides) which the user has used. There will need to be permissions so that people who can use the overrides aren't the same people who can edit them.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <h3 id="summary-remaining-tasks">Remaining tasks</h3>