Edit inline content in a table cell in the Content Editor
Problem to solve
In order to support the full GitLab Flavored Markdown spec, the Content Editor must be support rendering and editing all the elements of the standard implementation.
Working with tables in Markdown is one of the hardest things in the entire world. No contest. No one should have to do it. If you ask me to update text in a Markdown table that's more than 3x3, I'm just going to recreate it in Google Sheets, make my edits, then run it through a Markdown parser before pasting over the entire table.
It should be easier to edit content within a table cell and that's what we're focused on here.
Intended users
- Parker (Product Manager)
- Presley (Product Designer)
- Sasha (Software Developer)
- Eddie (Content Editor)
User experience goal
The user should be able to edit contents of an existing table cell in the Content Editor.
Proposal
Create an extension for the Content Editor that supports editing text within a table cell.
We're not creating new tables, so there is no toolbar UI necessary. We're not adding rows or columns, so we don't need any contextual UI either. This should be as simple as clicking within a cell and typing.
Details
Extensions to the Content Editor require a few specific details:
| Input Rule | N/A |
| Paste Rule | [paste_rule] |
| Toolbar Button | N/A |
| Keyboard Shortcut | N/A |
| Instrumentation | [event_name] |
Documentation
Availability & Testing
Available Tier
This feature, as with the content editor itself, is available on both SaaS and Self-managed Free tiers
What does success look like, and how can we measure that?
As this is just editing text, we probably don't want to track individual instances of editing within a table. Success is just a general sense of relief among anyone asked to edit the contents of a table.
What is the type of buyer?
Is this a cross-stage feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.