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

Please provide a "porting" guide for plugin developers #1894

Closed
dmccan opened this issue Jul 14, 2017 · 4 comments
Closed

Please provide a "porting" guide for plugin developers #1894

dmccan opened this issue Jul 14, 2017 · 4 comments
Labels
[Type] Developer Documentation Documentation for developers [Type] Help Request Help with setup, implementation, or "How do I?" questions.

Comments

@dmccan
Copy link

dmccan commented Jul 14, 2017

Gutenberg 0.4.0 - version as of this issue.

I have a plugin that adds editor buttons to TinyMCE that has a popup with inputs and provides shortcodes. I'm down to port this to Gutenberg blocks or whatever but would like a guide. I imagine there are a lot of people in the same boat as I am, who are ready to get with the program and have things ready for testing and launch.

Some information that would be useful for me is:

  • A way to know that this page is being edited in Gutenberg so that I can switch behavior.

  • A guide to creating a block to replace the TinyMCE button. My plugin provides a popup that gives a UI for entering the values that will go into the shortcode. It also does an AJAX type-ahead lookup based on the input. The shortcode is providing a wiki style link, so it goes in line with the paragraph content. I'm not sure if it should be a separate block or something else?

  • Understanding if / how I can render the shortcode in the block to preview the content for a better experience.

  • Is there anything needed for permissions or is that handled on the page level?

  • Are there any changes to revisions?

  • In general, a "best practices" and style guide would also be good. Also, if there are security best practices / nouces etc, then now is the time to beat them into our heads.

Thanks!

@karmatosed karmatosed added the [Type] Developer Documentation Documentation for developers label Sep 4, 2017
@StephenAtty
Copy link

I am facing similar problems - I have a custom meta box which does Ajax lookups and inserts a short code at the current cursor location in the post - although the meta box is working without me doing anything (apart from changing 'advanced' to 'normal') the rest of it doesn't work for obvious reasons and I seem to be unable to find out how I'd do the equivalent in Gutenberg. I imagine there must be a lot of developers facing the same issue - as well as potentially learn React at the same time.

@danielbachhuber danielbachhuber added the [Type] Help Request Help with setup, implementation, or "How do I?" questions. label Jan 23, 2018
@danielbachhuber
Copy link
Member

Related #4151

@mtias
Copy link
Member

mtias commented Mar 6, 2018

Closing this as there are/will be multiple docs for various integration points. Keep an eye on https://wordpress.org/gutenberg/handbook/extensibility/ and its sub-pages.

@mtias mtias closed this as completed Mar 6, 2018
@danielbachhuber
Copy link
Member

@dmccan @StephenAtty Just a heads up that I'm working on a more specific migration guide and welcome your input.

Tug pushed a commit that referenced this issue Feb 28, 2020
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 [Type] Help Request Help with setup, implementation, or "How do I?" questions.
Projects
None yet
Development

No branches or pull requests

5 participants