-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Improve the most popular API references #13236
Comments
|
Fwiw there's still probably plenty that can be done on those two, but if we're prioritising, it might make sense to pull up other things first. |
yeah its quite a long list so i haven't looked through them yet to find specific improvements that could be made, if we think there are any that are already at their best we can just cross them off the list. also @abbycross and Becky might want to take a look through just for a copy edit even if theres no major updates to be made |
is this issue still available? |
From #13297 (comment): It'd be good to look at all off the gates in Fwiw, when we do get to that, it's probably good for a tech person and a docs person to work together on a single example gate as the first example, so we can align on everything, then the docs person can work on getting all the gates updated to the style. I have several technical concerns with the gates API pages (mostly concerning tensor-product notation which is at best highly confusing as written), and we'd want to have that agreed before somebody goes through all of the several pages. |
@DisantHoridnt: this issue is primarily intended as tracking for the IBM Quantum documentation team, but if there's any subissues that might be helpful for an external contributor to look at, one of them might comment. |
got it, thanks for the reply |
(I suggest this issue be addressed in multiple PRs by the docs team)
We've gotten feedback that the API reference content could be better. This is also reflected in the data we collect on 👍 / 👎 , where the API reference consistently gets a worse ratio of negative to positive votes compared to the other docs. Specifically things like adding more code examples and return types could make this content better.
The following list includes (in order) the most visited API references (more than 200 views in the last 3 months). I recommend starting by going through this list in order, reviewing them and making any possible improvements.
The text was updated successfully, but these errors were encountered: