We are now actively working on the WordPress Directives Plugin Tracking issue instead ➡️

This issue aims to list and keep track of the tasks related to the Directives Hydration experiment.

• Wrapperless hydration alternative: Directives hydration #60

For the Custom Elements Hydration experiment, please check the Tracking Issue: Custom Elements Hydration 🧩.

The main branch of this experiment is main-directives-hydration. Make sure you select it when opening a pull request if it is related to this experiment.

Please, proactively comment on this issue whenever you start working on a new task, get blocked, or finish a task, sharing as much detail and information as possible. Thanks!!

Experiments

• Experiment: Client-side navigation of the Query Loop block using directives gutenberg#44034
• Experiment: Client side navigations in the Product Query block woocommerce/woocommerce-blocks#7187
• Experiment: Replicate Navigation block using directives gutenberg#44509
• Benchmark for WP directives DAreRodz/js-framework-benchmark#1

Done

• ⚛️ Restructure the project folder and files to make it ready for the Directives Hydration #65
• ⚛️ Hydrate the blocks with Directives Hydration (using wp-block and wp-inner-blocks) #66
• ⚛️ Add directives to handle providesContext and usesContext #68
• ⚛️ Add Suspense and ErrorBoundary examples #70
• ⚛️ Fix hydration when there are scripts in the top of the body #71
• ⚛️ Get rid of the <wp-block> wrapper #72
• ⚛️ Use a wp-inner-block attribute for each inner block #77
• ⚛️ Refactor directives and make them work inside client components #74
• ⚛️ Use Suspense and lazy to Hydrate views that were not registered before calling hydrate() #78

Next

On hold

• Add lazy hydration techniques: idle and view #75