#Wordpress 5.9 full site editing code#

However, different persisted queries will usually require the same set of rules, and if the set changes, then all persisted queries would need to be updated. Selecting what rules must be applied could be done within the persisted-query CPT itself, via some custom block. Persisted queries can be configured according to rules, involving access control and HTTP caching. The CPT uses the standard WordPress editor, powered by blocks: Persisted query CPT. To retrieve data for a persisted query in the WordPress site, I decided to create a new CPT called persisted-query, and retrieve its data simply by requesting its. My plugin installs a GraphQL server that supports persisted queries. I’ll first give an overview of what’s the objective: what functionality I’ve planned for my plugin to support. In this write-up, I will describe my implementation (fully available in the the leoloso/PoP repo), which aims to leverage the WordPress editor to provide a great user experience for configuring our themes and plugins. This is the strategy I employed for my WordPress plugin. We must also be careful: the CPT content is of private use to the plugin, not intended for public consumption, so we must make sure it cannot be loaded on the public-facing website. In this scenario, we must limit which blocks are available when editing the CPT and, quite likely, lock them using a predefined template. This is not difficult: because the WordPress editor can power custom post types (CPTs), we can then create a specific CPT that models the required configuration, and have the plugin retrieve the stored data from within the custom post content. However, we would then be reinventing the wheel, to produce a GUI of lower quality than the one from the WordPress editor.Ī better approach is to still use the WordPress editor, but altering its objective: instead of creating content for a blog post, we can produce the configuration required for our plugin. We may eventually be able to create a page in the wp-admin that directly renders - and allows to interact with - the needed blocks, as I recently described in my recent article, “ Implications Of WordPress Joining The Block Protocol,” but that’s currently only under consideration - nowhere near of it becoming a reality (if it ever does).Ī related approach that is doable already today, is to create a standard page in the wp-admin that loads React and reuses the components powering our blocks (that is, the components making up the blocks, but not the blocks themselves). If we want to implement custom settings pages powered by blocks, for the time being, we will need to implement a custom solution. WooCommerce provides a slider block to filter prices. Through it, we could allow our users to input configuration values using components tailored to that type of value, such as calendars to input dates, interactive maps to input location coordinates, sliders to pick a number from within a range (such as WooCommerce’s slider block to filter prices, displayed below), and so on. Providing a settings page for our themes and plugins that is fully powered by blocks would provide a compelling user experience. While it already does provide global settings via theme.json, that’s mainly for configuring the theme’s visual options, such as fonts, colors and paddings for a theme or plugin’s invisible settings, usually defined as some entry in the wp_options table, FSE offers no support (yet). However, FSE does not fully help us configure WordPress sites. Slowly but surely, blocks are becoming the main user interface for creating WordPress sites. WordPress 5.9 was released recently shipping with Full Site Editing (FSE), which enables using blocks to create the layout for any page in the website (as was already possible to write posts via the WordPress editor). In this article, we will learn how we can do it.

#Wordpress 5.9 full site editing code#

If we want our WordPress plugins to offer a settings page that is fully powered by blocks, how can we do it? Since Full Site Editing doesn’t support this feature yet, we need to code a custom solution.