---
# System prepended metadata

title: 'Project: Finish up `MenuButton` and `SplitButton` integration in Office Online UI - Part 2'
tags: [pitch]

---

---
robots: noindex, nofollow
tags: pitch
---

# Project: Finish up `MenuButton` and `SplitButton` integration in Office Online UI - Part 2

_Follow up from [this previous project](https://hackmd.io/C6xtN-N7QFyPGvFiSSBnCw)_

### Problem

We have started integrating some of our vNext components in Office Online UI, specifically `Button` and `ToggleButton`. By integrating `MenuButton` and `SplitButton` we will have replaced ~90% of the front-loading components for the Ribbon and we can get a better measure of the performance improvements we are getting on an existing scenario.

### Appetite

Effort III: Weeks.
Milestone: November Project Cycle Q4 2021.

### Solution

The tasks to be done in order to get this ready are: 
- [ ] Create vNext versions of `RibbonFlyoutAnchor` and `RibbonSplitButton` and integrate them as feature gates in the Ribbon 
    - Partially done, version created for `RibbonFlyoutAnchor` but not for `SplitButton` 
- [ ] Get both flamegrill and puppy-run measures of performance before and after the changes
- [ ] Get a PR out and reviewed to be able to start staging the consumption of the change

Kelsey from the WISE team is taking point on the work with me and Jeremy being there for support.

### Risks (Rabbit holes)

- Kelsey is still relatively new to the convergence effort so her taking point on it
- Me having less time to answer questions/dive deep within the code due to being on Shield.

### Out of scope (No-gos)

- Integrating other components is out of scope.
- The actual staging of the change will be controlled by our OOUI partner's priorities so that is out of scope for this change.

---
