Support a Lexical Editing Experience on the Front-End

[mgionas]

First off, I truly appreciate all the work you’ve done on Payload and its seamless Lexical integration in the Admin panel. It’s remarkably robust, giving developers a fantastic content-editing experience

However, I’d love to see an officially supported solution for embedding (or otherwise integrating) Payload’s Lexical editor into the front end. Many scenarios extend beyond the Admin panel itself, such as allowing public editing for end users or non-admin contributors who want to create or modify content on the live site.

Right now, I’m encountering version conflicts when trying to use the latest Lexical packages in my front end, since Payload’s Admin panel currently relies on Lexical 0.20.x. This mismatch can cause build or runtime errors, and resolving them manually is often tedious.

An official, well-documented approach for front-end integration—one that stays in sync with Payload’s own Lexical configuration—would be a huge help, especially for those of us building front-facing editing experiences.

Thank you for considering this request! I’m happy to discuss further or help with testing if needed.

[tyteen4a03]

All things aside, you can also just pin the version of Lexical you use to the same one Payload uses.

[mgionas]

You’re absolutely right that pinning Lexical version to match Payload’s can avoid some immediate conflicts. However, it’s more of a workaround than an ideal, long-term solution.

[tyteen4a03]

Lexical is currently in beta (0.x.x), and there can be breaking changes you / Payload need to account for even between minor releases.