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

Use sphinx.ext.autosummary to create better index for API docs #653

Open
5 tasks done
oruebel opened this issue Jul 21, 2021 · 3 comments
Open
5 tasks done

Use sphinx.ext.autosummary to create better index for API docs #653

oruebel opened this issue Jul 21, 2021 · 3 comments
Assignees
Labels
category: enhancement improvements of code or code behavior help wanted: good first issue request for community contributions that are good for new contributors priority: low alternative solution already working and/or relevant to only specific user(s) topic: docs Issues related to documentation
Milestone

Comments

@oruebel
Copy link
Contributor

oruebel commented Jul 21, 2021

Currently the the index for the API docs is in part defined manually and is not easy to navigate (see https://github.com/hdmf-dev/hdmf/blob/dev/docs/source/api_docs.rst and https://hdmf.readthedocs.io/en/stable/api_docs.html) It would be useful to update the docs to use the sphinx extension sphinx.ext.autosummary for this. See:

Addressing this issue may also require adding missing docstrings for python modules to further enhance the utility of the API docs.

Checklist

  • Have you ensured the feature or change was not already reported ?
  • Have you included a brief and descriptive title?
  • Have you included a clear description of the problem you are trying to solve?
  • Have you included a minimal code snippet that reproduces the issue you are encountering?
  • Have you checked our Contributing document?
@oruebel oruebel added category: enhancement improvements of code or code behavior help wanted: deep dive request for community contributions that will involve many parts of the code base help wanted: good first issue request for community contributions that are good for new contributors topic: docs Issues related to documentation labels Jul 21, 2021
@oruebel
Copy link
Contributor Author

oruebel commented Jul 21, 2021

#654 is a start at this, but there are still a few issues that need to be worked out. E.g., links from the autogenerated tables point to different pages than the links in the navigation bar. The PR is mainly to evaluate sphinx.ext.autosummary and to provide a starting-point for other who want to help with this issue.

@oruebel oruebel removed the help wanted: deep dive request for community contributions that will involve many parts of the code base label Sep 11, 2021
@rly rly added the priority: low alternative solution already working and/or relevant to only specific user(s) label Jan 12, 2024
@mavaylon1
Copy link
Contributor

@stephprince Thought this would be a good fit as a "first issue" ticket.

@mavaylon1 mavaylon1 added this to the Next Major Release - 4.0 milestone Apr 16, 2024
@oruebel
Copy link
Contributor Author

oruebel commented Apr 16, 2024

#654 was a first attempt at this several years ago, but the PR wasn't pushed over the finish line. This comment in the PR #654 lists the items that still needed to be finished in the PR. I just updated the PR to resolve merge conflicts. I don't think it should be too bad to push that PR over the finish line. Happy to help during the dev days with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: enhancement improvements of code or code behavior help wanted: good first issue request for community contributions that are good for new contributors priority: low alternative solution already working and/or relevant to only specific user(s) topic: docs Issues related to documentation
Projects
None yet
Development

No branches or pull requests

4 participants