## Problem to solve The Content Editor needs to know how to read and write the basic Markdown formatting syntaxes. The Content Editor supports the full [CommonMark spec](https://commonmark.org/) so we need to be able to render and edit all these elements. ## Proposal Support rendering and editing the full CommonMark spec. "Support" can be defined in a few ways. First of all, we need to be able to accurately render the content in the editor. Some content types (like Bold and Horizontal Rule) will be straightforward to implement in the UI through a toolbar icon. Other content, like Links or Tables, will require custom UI to create and edit the content in the editor. | Content type | Rendered | Editable | | ------ | ------ | ------ | | Bold | :white_check_mark: | :white_check_mark: | | Italics | :white_check_mark: | :white_check_mark: | | Headings 1-6 | :white_check_mark: | :white_check_mark: | | Horizontal rule | :white_check_mark: | :white_check_mark: | | Unordered list | :white_check_mark: | :white_check_mark: | | Ordered list | :white_check_mark: | :white_check_mark: | | Blockquote | :white_check_mark: | :white_check_mark: | | Inline code | :white_check_mark: | :white_check_mark: | | Code block | :white_check_mark: | :white_check_mark: | | Links | :white_check_mark: | :white_check_mark: | | Reference-style links | :white_check_mark: | :x: | | Images | :white_check_mark: | :white_check_mark: | ## Details For each content type, we need to define: 1. Input rule(s) 1. Paste rule(s) 1. Keyboard shortcut(s) 1. An icon for the toolbar 1. GitLab Flavored Markdown endpoint 1. Instrumentation 1. Documentation