Improve the usability of the editor
See original GitHub issueThe current Matterwiki editor (in the refactor
branch) uses draft-js
as its core editor. While this is good, there are wiggles, focus issues and other small issues that all add up to making the experience of using it sub-par. We could switch to a new editor or make the editor we have better. Any thoughts and suggestions would be helpful!
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
5 Ways to Improve the Usability of the Drupal Content Editor ...
For content editors, seeing a lot of options that don't relate to content editing is intimidating. From our usability testing, we can see...
Read more >Usability Improvements - Ex Libris Knowledge Center
... a usability improvement initiative to facilitate an enhanced user experience across Alma navigation and in the Metadata Editor.
Read more >Usability Testing From an Editor's Perspective
Usability testing is when designers ask users to complete a task on a website and take notes about what happens. The notes are...
Read more >Improving Usability of Math Editors | Request PDF
This paper presents data gleaned from textbooks that shows that if the subject area is known, the number of buttons needed for special...
Read more >Improve Editor Access & Usability for Designers
Here are the 3 top places that the Editor can be made much more powerful to Designers. MAINTAIN THE PAGE AND CMS-ITEM CONTEXT...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m leaning towards using slatejs on this one because
it seems to allow a little more customization through “plugins”… This is fantastic, because in the future, things could be easily made into its own package, if we started using lerna or yarn workspaces…
it just uses the DOM tree to represent the editor state, instead of its own structure (which fb/draft does), which is more intuitive and easy to reason about…
Easy moving around between HTML, MD and more! This is especially useful for us, because we need to support all these modes. Using draft would force us to re-invent the wheel on this one (Im sure it’s possible, but we could be working on something else instead of this for now)
@nshntarora I think I’ll start working on this next…