You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This RFC proposes adding an API documentation index page (e.g., see NumPy).
This would provide a single page which links to all the package docs. This would be useful both to provide a high level overview of symbols in the namespace and for crawling.
One question is how this index should be organized. By namespace? Alphabetically according to path basename (e.g., @stdlib/math/base/special/sin => sin)? Do we replicate the tree structure? Do we list all packages as just a single flat list?
I think replicating the tree structure should be fine. We can, however, be more economical with space by arranging tree leaves across, say, 4 columns. For example,
A
array
base
bar foo1 foo4 foo7
beep foo2 foo5 foo8
boop foo3 foo6 foo9
contains
...
There might be some tricky issues with layout (namely, indentation). Could also limit tree depth and use . syntax (e.g., base.special.sin), which may also be fine.
Description
This RFC proposes adding an API documentation index page (e.g., see NumPy).
This would provide a single page which links to all the package docs. This would be useful both to provide a high level overview of symbols in the namespace and for crawling.
Related Issues
No.
Questions
No.
Other
No.
Checklist
RFC:
.The text was updated successfully, but these errors were encountered: