Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: Core Concepts of Interactivity API - "Declarative vs. Imperative approaches" page #63524

Open
WPLake opened this issue Jul 13, 2024 · 0 comments
Labels
[Type] Enhancement A suggestion for improvement.

Comments

@WPLake
Copy link

WPLake commented Jul 13, 2024

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:

  1. Introduction - Terms description
  2. Drawbacks of the Imperative approach
  3. Benefits of the Declarative approach
  4. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

No branches or pull requests

1 participant