Code suggestions: tracking issue - content and copy writing for code suggestions

Background

We will be launching AI assisted code suggestions as a pre-installed extension in the GitLab web IDE in May. This issue is part of an epic for the UX portion of this project.

What's this issue all about

There are a number of issues where we need copywriting and content. I've made rough suggestions in the designs, but the actual content will impact the final design. The content needs to be a collaboration between UX, product, engineering, and legal. The content also needs to be reviewed by a copy writer.

I had been tagging each discipline on each individual issue, but this seems inefficient. Instead, I propose using this issue as a tracking issue for all of the content that needs to be written.

Proposal

• UX, product, engineering, and legal collaborate on content in google docs (links below)
• When we are satisfied, Katie arranges the review of a technical writer
• Designs are updated to final copy / content

Issues needing content & copywriting

Image	Description	Issue	Google doc	Status
	The first time the user enables the feature, they are shown a walkthrough	gitlab-web-ide#128	google doc
	In the Visual Studio marketplace, we have a page explaining the feature.	gitlab-web-ide#127 (moved)	google doc
	A survey to collect feedback from users	gitlab-web-ide#134 (moved)	google doc
	A short blurb in the web IDE onboarding	gitlab-web-ide#126 (moved)	google doc