Feature: Native Block Editor Interface

[fabiankaegy]

Warning

This PR is based on top of #91

Description of the Change

Adds a WordPress Data store to more easily interface with the Content Connect REST API from within the Block Editor.

Closes #45

How to test the Change

1. Ensure you have a test environment with a few connections configured (For example using the demo plugin: https://github.com/fabiankaegy/wp-content-connect-example-data)
2. Use the browser console on a post that has connections (in the editor) to run wp.data.select('wp-content-connect').getRelationships(xxx) where xxx is the current post id
3. This will resolve an empty object at first but if you run it again it will show you the relationships (this is expected since to begin with the relationships are not preloaded. useSelect will smooth this experience)
4. Now that you have the relationship you can get some actually related posts by running: wp.data.select('wp-content-connect').getRelatedPosts(xxx, 'university_city_university_to_city')
5. You can also update the relationships by running: wp.data.dispatch('wp-content-connect').updateRelatedPosts( xxx, 'university_city_university_to_city', [ yyy, zzz ] )

Note

This PR is still very much in progress and subject to change :)

Changelog Entry

Added - WordPress Data API store for interacting with the wp-content-connect plugin
Added - Block editor UI

Credits

Props @fabiankaegy @s3rgiosan

[s3rgiosan]

Hi @fabiankaegy I went ahead and updated the UI to use the new ContentPicker, along with some fixes and improvements for post-to-user relationship support and bi-directional panels in post-to-post relationships. Ready for your review when you can.

[s3rgiosan]

@fabiankaegy latest update on the sorting experience:

Screen.Recording.2025-05-06.at.6.42.59.PM.mp4

[ocean90]

Hi @ocean90,
Can you try again when you have a chance to see if the problem still persists?

I just tested the latest changes and the problem doesn't exist anymore. Good job!

Something to consider: The content picker doesn't work well with longer titles. The component uses <Truncate> with no option (like a tooltip) to view the full title anymore. If you have very similar titles, you will no longer be able to distinguish between them.

[s3rgiosan]

Something to consider: The content picker doesn't work well with longer titles. The component uses <Truncate> with no option (like a tooltip) to view the full title anymore. If you have very similar titles, you will no longer be able to distinguish between them.

Thanks for the suggestion, @ocean90! I'm actually working on a custom picker item for Content Connect here: #99. I'll keep that in mind when I get back to it.

[s3rgiosan]

I added this search parameter mainly to give context to the editor-side search when it reaches the rest_post_search_query hook in PHP. One of my clients uses ElasticPress, and I needed a way to disable EP for these specific queries. This parameter can also be used to filter search results based on client-specific requirements. It might also be worth including the current post ID.

[ocean90]

Noticed an issue with the display of relationships which can't be edited by the user: 10up/block-components#390