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

Table of contents for Boto3 API docs #4448

Open
2 tasks
chamal-perera-19 opened this issue Feb 24, 2025 · 5 comments
Open
2 tasks

Table of contents for Boto3 API docs #4448

chamal-perera-19 opened this issue Feb 24, 2025 · 5 comments
Labels
documentation This is a problem with documentation. feature-request This issue requests a feature. p3 This is a minor priority issue

Comments

@chamal-perera-19
Copy link

Describe the feature

Hi Team,

I have a small feedback on the AWS Boto3 documentation.

It will be great if you can make the documentation more readable by making the improvements to the UI.

As an example,
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/dynamodb/client/delete_item.html

In the above documentation page, it shows you all the details of the dynamo db delete item, which is great, but you have scroll up and down many many times to see the request structure, to see the description of each attribute item or to see the example.

If you can make some improvement so that users like us, does not have to scroll through a large content by making some UI improvements to all the documentation pages.

Use Case

I am always frustrated when I have go scroll many times to see and understand the documentation.

Proposed Solution

Please include as an example accordion or other UI improvements to make the documentation more easy navigate and readable.

Other Information

No response

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change

SDK version used

AWS Boto3 1.36.26

Environment details (OS name and version, etc.)

Windows

@chamal-perera-19 chamal-perera-19 added feature-request This issue requests a feature. needs-triage This issue or PR still needs to be triaged. labels Feb 24, 2025
@khushail khushail added p3 This is a minor priority issue documentation This is a problem with documentation. and removed needs-triage This issue or PR still needs to be triaged. labels Feb 24, 2025
@khushail khushail self-assigned this Feb 24, 2025
@khushail
Copy link

Hi @chamal-perera-19 , thanks for reaching out. For now, this is what has been adopted by team and would not be possible to change anytime soon. But I understand your concerns and it would be great if you could share your ideas in more detailed format reg the restructuring of documentation or page structure in mind. I could pitch that to team for their insights

@khushail khushail added the response-requested Waiting on additional information or feedback. label Feb 24, 2025
@chamal-perera-19
Copy link
Author

One thing is you can make page break into headings and then add those links to the right side bar where user clicks on a particular links, the page auto scrolls to that location.

You can add accordian to group the content so and make it by default closed, so the page scroll is smaller.

These are the things that I could think of, but definitley your team can think of more ways to improve the content quality.

@github-actions github-actions bot removed the response-requested Waiting on additional information or feedback. label Mar 3, 2025
@RyanFitzSimmonsAK
Copy link
Contributor

I definitely see the value in a heading table of contents, similar to what the AWS CLI documentation has. I'll bring that to the team for their review, and let you know when I have any updates.

Image

@chamal-perera-19
Copy link
Author

Yes, definitely some kind of UI improvements are needed. Especially if you a newbie, and getting to know about the API, it is very hard, scrolling up and down.

@RyanFitzSimmonsAK
Copy link
Contributor

Thanks for your patience. After talking with the team, a table of contents for Boto3 documentation is definitely something we see value in. I don't have a timeline for implementation at this time, but I'll be leaving this feature request open for tracking purposes, and will let you know if I have any updates. I'm going to adjust the title of this issue to reflect what the issue is tracking now. Thanks again for this feature request.

@RyanFitzSimmonsAK RyanFitzSimmonsAK changed the title Making the Documentation Easy to Read Table of contents for Boto3 API docs Mar 10, 2025
@RyanFitzSimmonsAK RyanFitzSimmonsAK removed their assignment Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation This is a problem with documentation. feature-request This issue requests a feature. p3 This is a minor priority issue
Projects
None yet
Development

No branches or pull requests

3 participants