Introduce parser for dynamic token system #42015
Draft
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
|
Size Change: -72 B (0%) Total Size: 1.25 MB
ℹ️ View Unchanged
|
gziolo
added
[Feature] Block API
|
yep, somehow related: #51373 (comment) |
This was referenced Jun 6, 2024
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.
Status
What?
Introduces a system to replace dynamic tokens with rendered values, a.k.a. "Shortcodes 2.0"
Discussion in #39831
"Tokens" are like shortcodes; they exist independent from blocks. They may be found inside of blocks, but they exist at the lexical level. Tokens have an identity unto themselves, such as "the URL of the featured image of the current post." On page renders they are replaced by the server. During edit sessions they appear in inputs as visual tokens. While previewing blocks in the editor they are replaced by JavaScript inside the editor.
Tokens provide a more restricted way of replacing basic text content with values provided from external sources. They cannot nest and they should limit themselves to plaintext replacements (though it's possible to provide anything from the server when rendering them).
Check out the README for more information on syntax forms and use. Development of those things is happening there too.
Why?
Blocks are heavy abstractions representing rich content types. While blocks fulfill many things that shortcodes were never able to fulfill well, they leave a gap in providing simple inline content from external sources - for example, the title of the current post.
How?
Testing Instructions
Example post:
Screenshots or screencast