docs: rename rich text section to text editor #9954
+24
−24
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GermanJablo
commented
Dec 16, 2024
| @@ -86,7 +86,7 @@ The Blocks Field inherits all of the default options from the base [Field Admin | |||
|
|
|||
| #### Customizing the way your block is rendered in Lexical | |||
|
|
|||
| If you're using this block within the [Lexical editor](/docs/lexical/overview), you can also customize how the block is rendered in the Lexical editor itself by specifying custom components. | |||
GermanJablo
commented
Dec 16, 2024
| @@ -1102,7 +1102,7 @@ plugins: [ | |||
|
|
|||
| ## `@payloadcms/richtext-lexical` | |||
|
|
|||
| If you have custom features for `@payloadcms/richtext-lexical` you will need to migrate your code to the new API. Read more about the new API in the [documentation](https://payloadcms.com/docs/lexical/building-custom-features). | |||
GermanJablo
commented
Dec 16, 2024
| @@ -79,7 +79,7 @@ This allows you to add i18n translations scoped to your feature. This specific e | |||
|
|
|||
| ### Markdown Transformers#server-feature-markdown-transformers | |||
|
|
|||
| The Server Feature, just like the Client Feature, allows you to add markdown transformers. Markdown transformers on the server are used when [converting the editor from or to markdown](/docs/lexical/converters#markdown-lexical). | |||
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sorry for one more change in the structure. Maybe this one is not as important as the previous one, but I think it gives clarity since “Rich text” is the field, “Text Editor” is a property of the field. So, this PR corrects the semantics of the sections.
Since there are some more redirects to do, I took the opportunity to shorten the building custom features slug.
Required redirects:
/docs/rich-text/overviewto/docs/text-editor/overview./docs/rich-text/convertersto/docs/text-editor/converters./docs/rich-text/building-custom-featuresto/docs/text-editor/custom-features/docs/rich-text/migrationto/docs/text-editor/migration/docs/rich-text/slateto/docs/text-editor/slate