You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The page should showcase a visual example highlighting the drawbacks of the imperative approach and promoting the declarative one. This is necessary because WordPress has historically been heavily related to PHP, and many experienced, old-school WP developers may not have any reactive background at all.
The outline can be:
Introduction - Terms description
Drawbacks of the Imperative approach
Benefits of the Declarative approach
Declarative iAPI Playground example
We already have a similar chapter in our WPLake blog article, so it can be used as a base and amended to match the wp.org writing style guides.
The text was updated successfully, but these errors were encountered:
We suggest including a "Declarative vs. Imperative Approaches" page in the Core Concepts section for the iAPI.
The page should showcase a visual example highlighting the drawbacks of the imperative approach and promoting the declarative one. This is necessary because WordPress has historically been heavily related to PHP, and many experienced, old-school WP developers may not have any reactive background at all.
The outline can be:
We already have a similar chapter in our WPLake blog article, so it can be used as a base and amended to match the wp.org writing style guides.
The text was updated successfully, but these errors were encountered: