The Interactivity API proposal was published a few months ago. This API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. aims to create a new standard for WordPress that simplifies and empowers building rich interactive web applications with WordPress using declarative and reactive programming principles.
Since the proposal was published, a dedicated group of contributors has been focused on incorporating the Interactivity API into the Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ project, albeit in an experimental capacity. Fresh documentation resources have also been prepared to guide you through this API’s exciting possibilities.
While the Interactivity API is experimental, you can already start exploring its potential, testing its features, and exploring what’s to come.
This update shares the current state of the Interactivity API, the avenues to track its progress, the learning resources available, and how you can contribute.
Table of Contents
Current Status and RoadMap
Wondering about the current state of affairs and how to stay in the loop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop.? Let’s dive right in.
What’s its current status?
The Interactivity API was added to Gutenberg 16.2 as the interactivity package. It’s worth noting that this package is only accessible within Gutenberg, as it is still very experimental and prone to changes.
Some core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks are already embracing the Interactivity API’s potential, but its integration is still very limited.
Contributors are still working on the experimental Interactivity API in Gutenberg. This work is being tracked at Tracking Issue: Expose the full Interactivity API in @wordpress/interactivity.
What lies ahead in the roadmap?
The list of tasks planned for the Interactivity API is available in the Roadmap – Current list of tasks discussion. This roadmap evolves and adapts as contributors learn more about the needs of this initiative.
Keeping Tabs on Progress
The ongoing work on the Interactivity API is held at the Gutenberg repository:
A good way to keep track of the development of the Interactivity API is to subscribe to Roadmap – Current list of tasks, as this discussion will be updated whenever new Tracking Issues are introduced or fresh plans emerge for this proposal’s future.
Given its experimental state, rapid iterations and occasional disruptions are expected. The Changelog – Tracking Breaking Changes in the Interactivity API discussion ensures you’re properly informed about any breaking change on new Gutenberg releases.
Learning Resources
Ready to expand your knowledge about the Interactivity API? Here’s where to start.
Where can I find technical documentation?
Technical documentation for the Interactivity API can be located within the docs folder of the interactivity package. This documentation currently hosts the following resources:
Bear in mind that this documentation is still a work in progress, so don’t hesitate to open a new discussion to ask any questions. If you want to contribute to documentation efforts, join the Coordinating our documentation efforts discussion.
The Getting Started – and other learning resources discussion is your go-to source for updates on new learning materials about the Interactivity API.
How can I get started?
To get started with the Interactivity API, you can follow this Quick Start Guide taking into account the current requirements of the Interactivity API. This guide will show you how to create your first interactive block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. with the Interactivity API that you can test in your WordPress projects.
Once your interactive block is up and running, you can learn more from the Interactivity API Reference to continue adding interactivity to your blocks with this API.
Where can I ask questions?
The Interactivity API Discussions is the best place to ask questions about the Interactivity API.
Contribute to the project.
Eager to contribute to the Interactivity API’s evolution? Your input is invaluable.
How can I contribute?
The best way to contribute to the Interactivity API is to share your ideas or suggestions in the Interactivity API discussions.
If you’re interested in helping with specific issues related to the Interactivity API feel free to comment on them to offer your help or add your insights.
Where can I share my feedback?
The Interactivity API Discussions is the best place to share your feedback about the Interactivity API.
Summary
As WordPress advances toward more powerful interactive experiences, seize the opportunity to engage. Your insights and contributions will help shape this proposal.
Props to @poliuk, @luisherranz, @czapla, and @greenshady for the review and help to shape this post.
#block-api, #block-developer-experience, #gutenberg, #interactivity-api
