[CUSTOMER FEEDBACK ISSUE](https://gitlab.com/gitlab-org/gitlab/-/issues/379045) **What is this Epic about and why does it exist?** * Epic to organize conversations and items for the GA of GitLab's new rich text editor. * Place to provide a more cohesive view of GA of the rich text editor. * To provide visibility into [all items in GA](https://gitlab.com/gitlab-org/gitlab/-/issues/?sort=created_date&state=opened&label_name%5B%5D=Content%20Editor%3A%3AGA&first_page_size=20). **What is our desired release date and why?** * Milestone %16.2 as Milestone 16.0 introduces major navigational changes. Milestone %"16.1" will allow more contributions beyond capacity to resolved additional Issues added to the GA scope. * This allows the editor to not be hidden amongst big changes in %"16.0". As discussed in the following [thread](https://gitlab.com/gitlab-org/plan/-/issues/898#note_1348658228 "Plan:Knowledge | 16.0 Release Planning"). **What do we need to do to release?** * (1) Define what's included in GA * (2) Resolve Bugs * (3) Resolve UX inconsistencies * (4) Come to a conclusion on the rollout plan * (5) Define criteria for success of rollout * (6) Out of GA * (7) MRs to Keep Track Of **(1) What's included in GA** Editor locations in GitLab. For GA we aim to have it available in all locations, but at the minimum the top usage areas. Must have * [x] Issues and Issue comments * [x]   https://gitlab.com/gitlab-org/gitlab/-/issues/407497+s * [x] Wiki * [x] Merge Request description and comments * [x]   https://gitlab.com/gitlab-org/gitlab/-/issues/406726+s * [x]   https://gitlab.com/gitlab-org/gitlab/-/issues/407507+s * [x]   https://gitlab.com/gitlab-org/gitlab/-/issues/407503+s Can be follow-up work * [ ]   https://gitlab.com/gitlab-org/gitlab/-/issues/407489+s * [ ]   https://gitlab.com/gitlab-org/gitlab/-/issues/407505+s * [ ]   https://gitlab.com/gitlab-org/gitlab/-/issues/407510+s * [x]   https://gitlab.com/gitlab-org/gitlab/-/issues/407495+s * [ ]   https://gitlab.com/gitlab-org/gitlab/-/issues/407496+s * [ ]   https://gitlab.com/gitlab-org/gitlab/-/issues/407504+s * [ ]   https://gitlab.com/gitlab-org/gitlab/-/issues/407494+s * [ ]   https://gitlab.com/gitlab-org/gitlab/-/issues/407491+s * [ ]   https://gitlab.com/gitlab-org/gitlab/-/issues/407490+s * [ ]   https://gitlab.com/gitlab-org/gitlab/-/issues/407506+s * [x]   https://gitlab.com/gitlab-org/gitlab/-/issues/407492+s * [ ]   https://gitlab.com/gitlab-org/gitlab/-/issues/407493+s Additional Items * [x] \[Suggest Changes Availability in CE\]( https://gitlab.com/gitlab-org/gitlab/-/issues/406726 '"Suggest changes" not available in content editor' * [x] All surfaced and known Bugs resolved (detailed below in 2) * [x] All primary UX priorities resolved (detailed below in 3) * [x] [Ensure stripping of quick actions is resolved](https://gitlab.com/gitlab-org/gitlab/-/issues/406720 "Quick actions data is lost when switching from markdown to rich text") **(2) Bugs** * DONE Himanshu To-do: * Create Bug Issues based on feedback in https://gitlab.com/gitlab-org/gitlab/-/issues/379045+ * DONE Himanshu To-do: * Label Bugs and [bucket](https://gitlab.com/gitlab-org/gitlab/-/issues/?sort=created_date&state=opened&label_name%5B%5D=Content%20Editor&milestone_title=16.0&first_page_size=20) into objective Milestone * DONE Matthew To-do: * Review/authenticate needed bugs GA in Build Board * DONE Himanshu To-do: * Rank importance of Bugs in Build board https://gitlab.com/gitlab-org/plan/-/issues/898+ * DONE Himanshu To-do: * Resolve needed Bugs for GA **(3) UX** * [x] Note on UX Involvement: Primary UX counterpart for this will be @mvanremmerden. Marcel is working in conjunction with Himanshu in implementation of the new layout. Making a special note of Marcel's involvement as Knowledge Group does not have an assigned UX counterpart per recent restructure. * [x] Create a New Layout for Editor for GA * [x] Release Iteration 1, 2023-05-04 * [x] Release Iteration 2, TBD * [x] [MR for Iteration 2](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/120850 "Moves editor mode switcher into bottom row") * [x] [Feedback Issue on new Editor Layout](https://gitlab.com/gitlab-org/gitlab/-/issues/409976 "Feedback: New layout for Markdown and Rich Text editor") * [x] [MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/117734 "New layout for editors") for Iteration 1 of new Editor Layout * [x] [Discussion](https://gitlab.com/gitlab-org/gitlab/-/issues/409976#note_1382087396 "Feedback: New layout for Markdown and Rich Text editor") for Iteration 2 of new Editor Layout **(4) Rollout Plan** * Primary Plan * Release to all customers in %"16.2" * Risk: More customer potentially exposed to unknown Bugs, Value: Customer benefit from elevated editing experience. * Requirements * [Popup similar to Web IDE to notify users of capabilities.](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/125189 "Add a callout for rich text editor") [Discussion around this](https://gitlab.com/gitlab-org/plan/-/issues/898#note_1354127800 "Plan:Knowledge | 16.0 Release Planning"). * Announcement in What's Happening GitLab Channel * Blog Post * Markdown is default of existing users while Rich Text Editor is default of new users. * Updated documentation * [Release Process for Major Features](https://about.gitlab.com/handbook/product/product-processes/#major-feature-rollout) **(5) Define criteria for the success of the rollout** * What we plan on tracking * 1 Measuring % of users using content editor vs classic editor (this is specific to when they submit a comment), filtered by category: issue/comment/reply/MR/epic etc * [Issue](https://gitlab.com/gitlab-org/gitlab/-/issues/412699 "Data Tracking for Content Editor GA: % of users using content editor vs classic editor") * 2 Which operations are used the most in the editors (this is already enabled for content editor but needs to be enabled for classic editor) * [Issue](https://gitlab.com/gitlab-org/gitlab/-/issues/412700 "Data Tracking for Content Editor GA: Which operations are used the most in the editors") * Steps for this process * Himanshu to enable tracking for 1 and 2 above * Matthew M to communicate this to Matthew Petersen * Matthew P to create graphs and Matthew M to communicate logic back to Himanshu **(6) Out of Scope for GA** * [Issue Board of All Items Out of Scope for GA](https://gitlab.com/gitlab-org/gitlab/-/issues/?label_name%5B%5D=Content%20Editor%3A%3APost%20GA) **(7) MRs to Keep Track Of** * Primary Release Post Item MR * https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/126855#ec5328d883a8d56f0e029fa5d7c5d2bfb9a520f9 :white_check_mark: * [Rich Text Documentation](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/126630 "Create docs for the rich text editor") :white_check_mark: * Secondary Release Post Item MR * https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/126856/diffs\\+ :white_check_mark: * [Suggest Changes Documentation Update MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/126361 "Update Suggest Changes Documentation") :white_check_mark: * Data Tracking MR * https://gitlab.com/gitlab-org/gitlab/-/merge_requests/125979 :white_check_mark: * https://gitlab.com/gitlab-org/gitlab/-/issues/412700+ * Rich text editor popup MR * https://gitlab.com/gitlab-org/gitlab/-/merge_requests/125189 :white_check_mark: * [Incident Related to Popup](https://gitlab.com/gitlab-com/gl-infra/production/-/issues/16040 "2023-07-14: Rich text editor popup is not getting dismissed") :white_check_mark: * [Incident Resolution](https://mail.google.com/mail/u/0/#inbox/FMfcgzGtwCxvQQgZsgdgFVrgxnqhmQrQ) :white_check_mark: * New rich text editor layout MR * [1st iteration](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/117734 "New layout for editors") :white_check_mark: * [2nd iteration](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/120850 "Moves editor mode switcher into bottom row") :white_check_mark: * Additional * Inclusion in GitLab What's Happening News Letter July 2023 :white_check_mark: * Slack Company Wide Notification in Whats Happening Channel :white_check_mark: * Notification after 1st iteration :white_check_mark: * Notification after 2nd iteration :white_check_mark: