Iterations on Nudge Copy for MR with No Pipeline Experiment
Problem
The MR with no pipeline / suggest pipeline experiment is active on GitLab.com. This issue makes additional copy and design changes to the existing 'nudges'.
Implement changes defined (1 to 4) in the designs tab - popover and modal images.
Background info
Active experiment - MR No pipe update - Looks like about 5.5% of users who are show the first nudge are engaging and then converting around 9.5%. We are about 5.5% away from our success criteria of 15%. Let's iterate on the workflow copy/designs!
Artifacts:
Dashboard | Clickable Prototype | Main Epic
Initial discussions in this issue:
cc: @gitlab-org/growth/expansion
Copy updates
Popover designs with updated copy
Nudge 1:
Title: unchanged
Paragraph: Use CI pipelines to test your code, simply add a GitLab CI configuration file to your project. It only takes a minute to make your code more secure and robust.
CI pipelines to test your code links to the blog post: https://about.gitlab.com/blog/2019/07/12/guide-to-ci-cd-pipelines/
CTA: Show me how to add a pipeline
Dismiss button: No thanks
Nudge 2
Paragraph 1: We’re adding a GitLab CI configuration file to add a pipeline to the project. You could create it manually, but we recommend that you start with a GitLab template that works out of the box.
Paragraph 2: Choose Code Quality to add a pipeline that tests the quality of your code.
"Code Quality" in paragraph 2 is set in bold.
Nudge 3
Paragraph: The template is ready! You can now commit it to create your first pipeline.
Success Modal
Modal designs with updated copy
Paragraph 1: The pipeline will test your code on every commit. A code quality report will appear in your merge requests to warn you about potential code degradations.
Paragraph 2: Take a look at our Beginner’s Guide to Continuous Integration and our examples of GitLab CI/CD to learn more.
code quality report in paragraph 1 links to https://docs.gitlab.com/ee/user/project/merge_requests/code_quality.html
Beginner’s Guide to Continuous Integration link destination in paragraph 2 remains unchanged.
examples of GitLab CI/CD link destination in paragraph 2 remains unchanged.