Rich Text Editor in Single-file Editor

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

Currently, you must know Markdown in order to edit text within the single-file editor on Merge Requests. This is a barrier to contributions for non-technical users. Leveraging the Web IDE to contribute instead can be even more daunting for non-technical users, and also requires knowledge of Markdown.

Current User Experience:

• Users editing files directly in merge requests must write raw Markdown syntax
• Non-technical contributors (designers, content creators, project managers, etc.) find this intimidating
• Common formatting like bold, italic, links, and lists require memorizing Markdown syntax
• Mistakes in Markdown syntax result in poorly formatted content
• Users may abandon contributions due to the technical barrier

Problem Impact

• Reduced contribution rates from non-technical team members
• Increased time spent by technical users helping others with Markdown syntax
• Inconsistent formatting in documentation and content files
• Barriers to inclusive collaboration across different skill levels

Proposal

Add the Rich Text Editor to the Single-file Editor on Merge Requests.

Expected Benefits:

• Improved accessibility: Non-technical users can contribute without learning Markdown
• Faster editing: WYSIWYG editing reduces time spent on formatting
• Better consistency: Rich Text Editor enforces proper formatting standards
• Increased participation: Lower barrier to entry encourages more contributions