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: Interactivity API - Move docs from "Reference Guides > Package Reference > @wordpress/interactivity" to "Reference Guides > Interactivity API Reference" #60781

Closed
juanmaguitar opened this issue Apr 16, 2024 · 4 comments
Assignees
Labels
[Feature] Interactivity API API to add frontend interactivity to blocks. [Type] Developer Documentation Documentation for developers [Type] Enhancement A suggestion for improvement.

Comments

@juanmaguitar
Copy link
Contributor

juanmaguitar commented Apr 16, 2024

What problem does this address?

In order to escalate the docs around the Interactivity API we need a better location that makes more sense for developers using the docs. I think it would make perfect sense to put the "Interactivity API" at the same level than "SlotFills" or "Data Module" for example

What is your proposed solution?

Move docs from "Reference Guides > Package Reference > @wordpress/interactivity" to "Reference Guides > Interactivity API Reference". From there it will be easier to add a proper structure for further explanations and sections related to the Interactivity API (like these ones for example)

@ndiego @ryanwelcher @luisherranz @gziolo any thoughts?

@juanmaguitar juanmaguitar added the [Type] Enhancement A suggestion for improvement. label Apr 16, 2024
@juanmaguitar juanmaguitar self-assigned this Apr 16, 2024
@juanmaguitar juanmaguitar added [Feature] Interactivity API API to add frontend interactivity to blocks. [Type] Developer Documentation Documentation for developers labels Apr 16, 2024
@ndiego
Copy link
Member

ndiego commented Apr 16, 2024

I definitely think it could use a more visible location, but what about other APIs? My only other reservation is how this move might impact the npm deployment.

Another option could be to build out all the docs under Reference Guides > Package Reference > @wordpress/interactivity and just make this more discoverable. For example, we could rewrite the Reference Guides page (which is horrible) to highlight some featured APIs and reference info. I also think we need a How-to Guide on the IAPI.

@juanmaguitar
Copy link
Contributor Author

My only other reservation is how this move might impact the npm deployment.

Could you explain this a bit more? The README of the package could just provide an introduction to the package with links to where the documentation is

Another option could be to build out all the docs under Reference Guides > Package Reference > @wordpress/interactivity and just make this more discoverable. For example, we could rewrite the Reference Guides page (which is horrible) to highlight some featured APIs and reference info.

Not 100% convinced, but it doesn't sound like a bad approach 😃 Yes, we need a plan for the "Reference Guides" secition!

@ndiego
Copy link
Member

ndiego commented Apr 16, 2024

Could you explain this a bit more? The README of the package could just provide an introduction to the package with links to where the documentation is

Ah gotcha, I thought you meant move the entire folder to Reference Guides > Interactivity API Reference.

But yeah, I agree that the main docs for the IAPI should be in their own section in Reference Guides > Interactivity API Reference.

@juanmaguitar
Copy link
Contributor Author

I close this issue as per #61143

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Interactivity API API to add frontend interactivity to blocks. [Type] Developer Documentation Documentation for developers [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

No branches or pull requests

2 participants