---
# System prepended metadata

title: Convergence component plan
tags: [convergence, ' RFC']

---

---
robots: nofollow, noindex
tags: convergence, RFC
---

# Convergence component plan

- Dont share internals, why should we use v8 hooks in v0 if we are moving away from it anyway
- Need documentation for react-* packages even if they aren't in @fluentui/react
    - Need docs and list of our "converged components"
    - Track status of components on doc site, track open RFC on components
- Where to put react-* docs? Formerly fabric docs? Fork of northstar docs?
    - Can we leverage the new docsite Alice's team is working on
- Repo in a box docsite?
    - Storybook's doc plugin?
- react-* packages cannot depend on react-internal or react-northstar
- reexports of another package are sticky
    - Menu exporting ButtonProps
    - We need to be careful when developing our react-* components to avoid circular dependencies as much as we can
- These are the ones that support tokens, these are the ones that don't
- Encode in the name the fact that things might be unstable
- Having smaller packages, how will we do major releases for the individual releases of these packages later? Do we drop lockstep in them? Do we major bump everything? What branches do packages live in?
- Risk: it will take ages to update all the components
- react-button has a version in v8, this might be messy, we should mitigate risk by adding a very clear "in-preview" message in react-button README, docs site and v8 release notes
- We should expect ThemeProvider changes, especially after we start dealing with how to consume it in TMP


# Component Convergence RFC
- Moved to GitHub: https://github.com/microsoft/fluentui/issues/15929