You're in good company

By default you have access to your own personal site - use it as a blog or portfolio site.

Free forever

Customize branding of your site - your own custom domain, colours, layout, and more.

Tailor your branding.

Home

Over the years I have built severals web apps where I needed a rich text editor to support the core features. 

To say the least, it has never been a clear or straight forward path. Choosing from Vanilla 

 and others. Then there is sourcing the data, hydration, styling, syntax highlighting, custom snippets, custom shortcuts and so on - some of them always proving to be a roadblock.

At last, the latest edition to the ecosystem surfacing early this year - 

 from (whether you like the company or not) 

Up until now, my efforts yielded solutions to 

 of the requirements, but not all, moreover all have come at a great time cost.

Documentation is not always amazing, examples are outdated, support is limited to GitHub issues that in some cases are overseen and in some are not, and an array of cross-feature compatibility issues.

My favourite so far for full-fledged Rich Text editing functionality has been Slate.js. This package is great in that it is fully customizable as in its core it handles JSON object that you can manipulate as you please (

, the biggest problem with community packages is that they often lack the resources or consistency in either documentation, support, bug patches, or all of the above.

Come Lexical. Since Lexical comes from the scandalous company Facebook, which has lots of resources and many incredibly talented people, regardless of the politics, one can be quite confident in that products that come from them will at the very least be actively maintained, especially, the ones that they use themselves. From what I know so far, Lexical is one such product.

If you're looking for a rich text editor for a React-based project - I say - give Lexical a go!

The only thing to note - currently the latest version from Lexical is 0.6.0, which means that it hasn't crossed a stable release checkpoint yet, which in turn means you can expect core API changes, which will likely require some refactoring work when it does, and it also means that there may be bugs or inconsistencies. That said - as I wrote above - Facebook is a serious company with talented people working on these products, so it will likely have major bugs or issues, and if they do, you can expect those to be addressed comparatively fast.

 If you need any help getting started or are interested in a video-course, feel free to reach out on 

@lexical/react

@lexical/rich-text

Rich text with custom components for React with Lexical may be the answer to your Rich Text editing needs in React-based apps.

Is Lexical the new Rich Editor standard for React?

Comments