Designing better text editor

Making better text editor for


Snob, it's not only a news website but also a center of interesting discussions. There is a blog or community part of the website, where can write articles and comment not only our editors, columnists but also our subscribers.

In this case, I tell about an entry point for new subscriber-made content - our editor.

One day you find yourself overwhelmed. Figma loading slow, your searching for ten minutes for a screen or page that someone designed like a year ago.


It's important to keep our documentation, ideas, and solutions tidy and easy to reach out to. So made a page in Notion where we keep all our ideas and resources. We also made a sitemap with features.

We write down competitors or websites in which we like an editor the most. It's important to look at big websites to make our design also familiar to other editors so that as many people as possible can handle our editor.

Preview modal

To make user-generated content look good, we need to motivate our users to add photos and create a more brief and nicer heading, we need to add constraints for them, but gently.

So after you try to publish an article, you see that modal, where you can write your heading, subheading, and picture for your preview card on other parts of the website.

We autoload the maximum of the data from the actual article to minimize user cognitive load. Users will see if their heading will be abrupt or trimmed which is leading them to change and improve their headings

Mobile version

It's important to make our designs functional even on mobile. Of course, we can't create a full word processor on the mobile web, but we should make it possible to quickly change the article on the go.

Small interactions

Small interactions are also important, like if a user deletes preloaded text, how to preload it again? And we made a different state for that too. A small button appears and you can easily get it back.


We made a test version for users to get to know some big problems to fix. So we get them the text version, ask them to do their usual things, and give them a questionnaire.

We find out some drawbacks of our design when users tried to re-edit their articles. And of course, some bugs to fix.

Constantly improving

Then, we create another state which is needed to be improved, I always improving the management of all states then the page has to easily find a state that you need, about managing Figma files I wrote another article that is more practical for designers.