Wireframe spec
Hana's wireframe shows a distinct Schema page under Architecture & Vocabularies, with sections:
The Architecture & Vocabularies dropdown menu lists: Overview → Requirements → Schema → Vocabularies
Current state
We link to the external Metadata Model site instead of hosting schema content on-site. The sidebar shows "Metadata Model" as an external link.
Question for team
Should we:
- Create an on-site Schema page that summarizes Model/Classes/Slots with links to the full external docs?
- Keep the external link but rename it "Schema" in the sidebar to match the wireframe?
- Embed or iframe the external metadata site?
Option 1 gives us editorial control and matches the wireframe. Option 2 is zero effort but loses the wireframe's intent of having on-site content.
Analysis from Figma API scan: wireframe frame [33:1369] Schema with sub-elements [33:1515] Model, [33:1525] Classes, [33:1530] Slots.
Wireframe spec
Hana's wireframe shows a distinct Schema page under Architecture & Vocabularies, with sections:
The Architecture & Vocabularies dropdown menu lists: Overview → Requirements → Schema → Vocabularies
Current state
We link to the external Metadata Model site instead of hosting schema content on-site. The sidebar shows "Metadata Model" as an external link.
Question for team
Should we:
Option 1 gives us editorial control and matches the wireframe. Option 2 is zero effort but loses the wireframe's intent of having on-site content.
Analysis from Figma API scan: wireframe frame
[33:1369] Schemawith sub-elements[33:1515] Model,[33:1525] Classes,[33:1530] Slots.