[UX] MVC - Introduce users to verify via SAST Entrypoints
User Experience Goal
As a core user, I need a way to better understand what SAST is, how to use it, and the value it can bring to my work.
Problems to Be Solved
Understand if our users are interested in SAST. We'll want to know if interacting with the entry point and the documentation increases adoption of SAST, which we think may be a nice entry point into learning more about pipelines and adopting aspects of Verify.
Secondly we will want to understand which entry points are more likely to drive traffic towards a certain feature, as we don't have a lot of data to back which one performs the best. Data from this can be used in future experiments to help understand which entry points we should be using in general.
Hypothesis
By crafting an experience that tests different entry-points into the SAST workflow, we will better be able to understand if our users are interested in finding out more about SAST (which will answer the question on whether to proceed with building the feature), where in the application our users interact with this from, who (their role) interacts with this. In addition we may be able to better understand which entry-points are worth exploring more in future experiments.
By crafting different entry points that link into a SAST doc, we will better be able to understand both the interest our users have in SAST as well as which entry points perform the best for future experiments.
Proposed Solution
Provide users entry into SAST from a banner on the projects page and as well as a popup. This banner would then lead users into a wiki that explains to them how to set up SAST in their pipeline.
Option 3 - New Popover Variant
CTA Destination https://docs.gitlab.com/ee/user/application_security/sast
Measures of Success
In order to track the success of this experiment, we will enroll new signups (namespaces) into either the control or experiment group, tracked in the experiments_users table with a unique experiment_id. We will enroll 33% of traffic into the control, 33% into candidate 1, 33% into candidate 2.
In the experiment cohorts, we'll also want to add events for:
- Interacting with the entry point
- Successfully setting up SAST
And ideally we'll be able to also track:
- Free:paid conversion in candidate vs.control
- Ultimate conversion in the candidate vs. control