[RPP insight] Update the README file

Bug: none
Change-Id: I00d71e91f89fd735ccd4abd7d50313abc64f8342
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6316673
Reviewed-by: Jack Franklin <[email protected]>
Auto-Submit: Nancy Li <[email protected]>
Commit-Queue: Jack Franklin <[email protected]>

Author: Nancy Li

front_end/panels/timeline/components/insights/README.md

@@ -1,9 +1,13 @@
 # Building performance insights UI
 
-**Last updated: Jan 2025**
+**Last updated: Mar 2025**
 
 If you want to add an insight to the Performance panel sidebar, you need to create and render an HTML component that follows certain conventions which will mean it integrates nicely into the rest of the performance panel, and all its overlays/active state/etc is managed for you.
 
+## 0. (Optional) Add your insight to `EXPERIMENTAL_INSIGHTS`
+
+The insights often require multiple CLs to implement. If you want your WIP insight only be visible when the 'enable experimental performance insights' experiment is active, you can add it to the insight to `EXPERIMENTAL_INSIGHTS`.
+
 ## 1. Extend `BaseInsightComponent`
 
 When creating your component, extend the `BaseInsightComponent` class (defined in `components/insights/BaseInsightComponent.ts`). This class will set up some of the setters and data you need. Your component will then have access to a `this.data` object which will have on it:
@@ -65,4 +69,11 @@ override connectedCallback(): void {
 
 ## 5. Render!
 
-Add your insight to the UI in `SidebarSingleInsightSet.ts` in the `INSIGHT_NAME_TO_COMPONENT` variable.
+Add your insight to the UI in `SidebarSingleInsightSet.ts` in the `INSIGHT_NAME_TO_COMPONENT` method.
+
+
+## 6. Before you submit your CL
+
+- Add your related VE loggine context values in the `KnownContextValues.ts`
+- Update the tests in `SidebarSingleInsightSet.test.ts`
+- WHen you want to ship the insight, make sure it is not in the experiments: `EXPERIMENTAL_INSIGHTS`.