-
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
Plugin: Let's get Gutenberg in the plugin repository 🎉 #953
Comments
Creating a new #meta ticket to have it added as a featured plugin regularly sync'd has would be ideal: |
One thing we need to do first is make sure our vendor scripts are bundled with the plugin and not re-downloaded every day, or on each page load. |
I don't think the featured plugin sync will work with Gutenberg as-is because it creates plugins from |
I was planning on just pushing the build manually on a weekly basis or so to the directory. Not sure if setting up something more complex is worth the time. |
@nylen do you think you can handle the bundling tasks? |
Can part of this be to also exclude |
They shouldn't be bundled. They're referenced as externals to their respective globals enqueued server-side. |
We should be ready to do this now. See #1147 for other considerations for each release, such as git tagging. |
Closing this as fixed. HOORAAAY! Great job everyone 🌟 |
It's time we get this baby out into the wider world. Let's look at what's required for us to ship this plugin in the repository.
This would essentially fix #655 through other means.
The text was updated successfully, but these errors were encountered: