Feedback from Content Editor MVC in Wiki
This issue was created to collect feedback related to the Content Editor and its initial implementation in the Wiki. We have gathered the feedback we needed to mature the editor so we'll be closing this issue. If you have additional feedback, please create a new issue and label it with ~"group::editor" and Content Editor
GitLab %14.0 includes the first publicly-available implementation of the new Content Editor, a WYSIWYG editing experience for Markdown. Our first goal is to make the Content Editor the default Markdown editor for the GitLab Wiki, with full support for GitLab Flavored Markdown extensions.
Currently, we have support many of the basic Markdown content types like
- Headers
- Bold and italic text
- Inline code and code blocks
- Blockquotes
- Links
In the coming milestones, we're excited to continue working on more complex content types like Images and Tables.
Direction
The Content Editor was architected as a reusable and extensible component, meant to be consumed by more than just the Wiki. Behind the scenes, the editor reads and writes Markdown. This is an important distinction because it would have been easier to read Markdown and write out a proprietary format. We feel this prohibits collaboration on content from those who don't wish to use the Content Editor and prefer to edit content in the repository directly. If you like writing Markdown in vim, we don't want to stop you.
As we complete support for GitLab Flavored Markdown, we'll be looking to spread the Content Editor around GitLab wherever Markdown content is edited. Our second target is likely going to be issue and epic descriptions, something we're very excited to work on!