Skip to content
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

Create guide in the Block Editor Handbook on how to enqueue assets in the Editor #53402

Closed
ndiego opened this issue Aug 7, 2023 · 2 comments · Fixed by #53828
Closed

Create guide in the Block Editor Handbook on how to enqueue assets in the Editor #53402

ndiego opened this issue Aug 7, 2023 · 2 comments · Fixed by #53828
Assignees
Labels
[Type] Developer Documentation Documentation for developers

Comments

@ndiego
Copy link
Member

ndiego commented Aug 7, 2023

What problem does this address?

As the WordPress Editor has evolved, we have developed numerous methods to enqueue assets. There are different methods for individual blocks, themes, and feature plugins. And with WordPress 6.3, we are getting the enqueue_block_assets method and the Post Editor will be iframed by default (there are some caveats here).

The lack of a definitive resource has led to misinformation and confusion on how to properly interact with the Editor, especially the iframed Editor.

What is your proposed solution?

We need a definitive guide/resource for developers that details all the recommended ways to enqueue assets (scripts and styles) and the best practices for each. This guide also needs to identify any limitations and caveats.

@ndiego ndiego added the [Type] Developer Documentation Documentation for developers label Aug 7, 2023
@ndiego ndiego self-assigned this Aug 7, 2023
@skorasaurus
Copy link
Member

skorasaurus commented Aug 7, 2023

#33212 may be helpful with common issues of enqueueing in the editor.

@tresorama
Copy link

Related

#48497

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Developer Documentation Documentation for developers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants