You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/rich-text/overview.mdx
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,21 +7,21 @@ title: Rich Text Editor
7
7
---
8
8
9
9
<Bannertype="success">
10
-
The Payload editor is based on Lexical, Meta's rich text editor. The previous default editor was based on Slate and is still supported. You can read [its documentation](../rich-text/slate), or the optional [migration guide](../rich-text/migration) to migrate from Slate to Lexical (recommended).
11
-
</Banner>
12
10
13
-
One of Payload's goals is to build the best rich text editor experience that we possibly can. We want to combine the beauty and polish of the Medium editing experience with the strength and features of the Notion editor - all in one place.
11
+
This documentation is about our new editor, based on Lexical (Meta's rich text editor). The previous default
12
+
editor was based on Slate and is still supported. You can read [its documentation](/docs/rich-text/slate),
13
+
or the optional [migration guide](/docs/rich-text/migration) to migrate from Slate to Lexical (recommended).
14
+
15
+
</Banner>
14
16
15
-
Classically, we've used SlateJS to work toward this goal, but building custom elements into Slate has proven to be more difficult than we'd like, and we've been keeping our options open.
17
+
The editor is the most important property of the [rich text field](/docs/fields/rich-text).
16
18
17
-
Lexical is extremely impressive and trivializes a lot of the hard parts of building new elements into a rich text editor. It has a few distinct advantages over Slate, including the following:
19
+
As a key part of Payload, we are proud to offer you the best editing experience you can imagine. With healthy
20
+
defaults out of the box, but also with the flexibility to customize every detail: from the “/” menu
21
+
and toolbars (whether inline or fixed) to inserting any component or subfield you can imagine.
18
22
19
-
1. A "/" menu, which allows editors to easily add new elements while never leaving their keyboard
20
-
2. A "hover" toolbar that pops up if you select text
21
-
3. It supports Payload blocks natively, directly within your rich text editor
22
-
4. Custom elements, called "features", are much easier to build in Lexical vs. Slate
23
23
24
-
To use the Lexical editor, first you need to install it:
24
+
To use the rich text editor, first you need to install it:
The Slate editor has been supported by Payload since we released our initial beta. It's battle-tested and will continue to be supported into the future.
9
+
<Bannertype="warning">
10
10
11
-
If you are migrating a Payload project from 1.x or earlier, you can continue to use the Slate editor as long as you'd like.
11
+
The [default Payload editor](/docs/rich-text/overview) is currently based on Lexical. This documentation
12
+
is about our old Slate-based editor. You can continue using it because it is still supported, or you can
13
+
see the optional [migration guide](/docs/rich-text/migration) to migrate from Slate to Lexical (recommended).
14
+
15
+
</Banner>
12
16
13
17
To use the Slate editor, first you need to install it:
0 commit comments