Feature in-app marketing and configuration status

[codecovdesign]

Problem to Solve

• Currently, users need to navigate through documentation, the marketing website, or through emails to discover new feature offerings. This process can lead to users overlooking useful features that could otherwise benefit their repositories. related: https://github.com/codecov/engineering-team/issues/1386
• As new features continue to be introduced (pre-release), there's a growing need to assist users in understanding how their repositories are configured and which features are active. This understanding helps 1) eliminate the guesswork and the need to manually search through YAML configurations and 2) broadcast new features as they become available.
• Lastly, we need to better differentiate the team and oss/pro plan, there has been consistent confusion here: https://github.com/codecov/engineering-team/issues/1444
• @rohan-at-sentry with project opt in, they may be unaware of the availability and/or how to add it
  • https://github.com/codecov/engineering-team/issues/1058

Exploration

A configuration page at the org > repo level that displays available features and the current configuration status (active/inactive) of each feature for a given repository. This page would serve several purposes:

1. feature discovery: users can easily see all the features available to them, making it easier to take advantage of new tools and integrations

2. configuration overview: provides a snapshot understanding of which features are currently active or inactive, supports: https://github.com/codecov/engineering-team/issues/1386

3. simplifying activation: actionable / for inactive features link the relevant documentation

4. education and guidance: include brief descriptions of each feature and what plan it's related to (helps: https://github.com/codecov/engineering-team/issues/1444)

view designs

previous designs / ideation

`settings` => `configuration` > repo Manager | repo configuration w/ configured features | Upgrade to pro | | --- | --- | --- | | | | | https://github.com/codecov/engineering-team/assets/87861036/862f7f36-6226-4947-ab7e-dd7478993c8a Later versions this page can support 1) new features, 2) upgrades, 3) [configuring with PR](https://github.com/codecov/engineering-team/issues/153)

### Tasks
- [ ] https://github.com/codecov/engineering-team/issues/1991
- [ ] https://github.com/codecov/engineering-team/issues/2031
- [ ] https://github.com/codecov/engineering-team/issues/2104
- [ ] https://github.com/codecov/engineering-team/issues/2105
- [ ] https://github.com/codecov/engineering-team/issues/2106
- [ ] https://github.com/codecov/engineering-team/issues/2108
- [ ] https://github.com/codecov/engineering-team/issues/2109
- [ ] https://github.com/codecov/engineering-team/issues/2111
- [ ] https://github.com/codecov/engineering-team/issues/2141
- [ ] https://github.com/codecov/engineering-team/issues/2112

[codecovdesign]

consider recent change for project coverage opt-in (section in "configuration")

[spalmurray-codecov]

@codecovdesign design looks great! The one thing I need to verify is that we can determine whether each of these are configured. Currently all but the Slack integration we definitely can do. Need to double check Slack though, will follow up.

One design comment, in the video for Slack, IMO it would be better to have the in-app link take you directly to install and skip the extra click to the marketing site.

[codecovdesign]

@spalmurray-codecov

Need to double check Slack thoug

@RulaKhaled may be able to help you on that one

@spalmurray-codecov also sent over a sync for tommmorrow to do a quick review and discuss this issue a bit more

[codecovdesign]

review on 6/16

• spencer: we have a solution that can resolve the slack status ✅
• todo: ideation on displaying not-yet-configured state + generally finalizing designs for dev ready
• other question: is outside of the features listed in the designs, are there are other that we want to display
  • ex tests
  • other non features: browser extension, vscode plugin, (?)
• otherwise no blocker to move forward