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 a document to track Gutenberg compatibility with major third-party services #4646

Closed
2 tasks
danielbachhuber opened this issue Jan 23, 2018 · 4 comments
Closed
2 tasks
Assignees
Labels
[Type] Developer Documentation Documentation for developers

Comments

@danielbachhuber
Copy link
Member

danielbachhuber commented Jan 23, 2018

For issues like (#1698) which aren't immediately actionable by Gutenberg, it would be helpful to have a document tracking Gutenberg's compatibility with major third-party services.

These services include:

@danielbachhuber danielbachhuber added the [Type] Developer Documentation Documentation for developers label Jan 23, 2018
@danielbachhuber danielbachhuber self-assigned this Jan 23, 2018
@danielbachhuber danielbachhuber added this to the Merge Proposal milestone Apr 11, 2018
@karmatosed
Copy link
Member

Would using a project work? This sounds like a great use of that as we can also close and move issues to a project.

@danielbachhuber
Copy link
Member Author

@karmatosed A GitHub project? Doesn't the issue have to remain open in order to be present in the project?

@karmatosed
Copy link
Member

It doesn't, it can close and be in a project. It's one way we've done for Customization phase two issues.https://github.com/WordPress/gutenberg/projects/13

@danielbachhuber danielbachhuber removed this from the Merge Proposal: Editor milestone Apr 14, 2018
@danielbachhuber
Copy link
Member Author

Cool, sounds good. I've created Third-Party Compatibility.

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

No branches or pull requests

2 participants