--- robots: nofollow, noindex tags: meeting-notes --- # FastDNA and Fluent UI Sync ## Agreed Focus Areas for Collaboration **GOAL 1: Enable interop of components and themes** We think Open UI is the place to do this. Components will work together side by side by aligning on: 1. JSON schemas for describing components - Components from different authors work in the same design and doc tools. 3. Interaction Models - End users cannot tell the difference between component frameworks from usage. 5. Design Tokens - Feature devs, app devs, and designers can customize components from multiple frameworks and authors using a single single set of standardize components. 7. Taxonomy and Anatomy - Components use the same names and anatomies between frameworks and design guides. **GOAL 2: Tooling interop** Components can be used interchangeably in tools, this is largely achieved by Goal number 1, specifically, the aligned JSON Schemas. This will mean that internal or external developers can use the same tools to work with our various web component stacks (React and Web Components). **GOAL 3: Integration** Can FAST-DNA become the official solution to build Fluent UI Web Components? FAST-DNA is available as a stand alone framework but can also be consumed via Fluent UI where additional M365 and MS Graph experiences will be available. - GraphToolkit is using FastElement - Can GraphToolkit use FastButton also? Caveat here is there would be an expectation that the "official" Fluent UI live under the Fluent UI brand. **Messaging** From a customer developer perspective, we want to communicate Fluent Design == Fluent UI. Similar to Material or other Design systems, there are platform and tech specific implementations of the Fluent Design System. Fluent UI for Webcomponents will be based on FAST-DNA and extends it to align with the control set expected from libaries within the Fluent UI family.