-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: add to the related documentation about the API of the edit-site
package
#43107
Conversation
Size Change: 0 B Total Size: 1.27 MB ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look good to me. Just need to address the merge conflicts.
1397123
to
8ded9b0
Compare
@ryanwelcher |
8ded9b0
to
6945bb9
Compare
3257b28
to
cb9d0ed
Compare
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
The
This PR is no longer needed, so it will be closed. |
Fix: #43049
What?
This PR adds content regarding plugin support added to the
edit-site
package by #34460 to the associated documentation.Why?
As mentioned in #43049, this is to remind developers that if we want to use plugin support in the site editor, we need to import from the
edit-site
package instead ofedit-post
.How?
edit-site
package, I added introductory content and tokens for the automatic generation to match theedit-post
packageplugins
package, I added a comment in the sample code that generates itedit-post
package.