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
Originally mentioned in #212, but in light of @odow's work in jump-dev/JuMP.jl#3386, I think this deserves a dedicated issue.
Have function, type, module etc. reference as a separate set of pages, one item per page. Every item would then have a systematic URL (e.g. /reference/Documents/Page) to page that would contain the docstring, but also additional information (source links, lists of methods etc).
I think this is definitely a feature that should be explored, to nudge people towards more thorough docstrings etc.
One thing we could also do is generate backlinks from those reference pages to (1) where the docstring is referenced with at-ref, and (2) if we simultaneously allow including the docstrings in-line (related: #1079), we should also backlink to those.
I do think this should be done, in the first iteration, as a plugin package. Once that stabilizes, we could integrate it into Documenter-proper.
The text was updated successfully, but these errors were encountered:
Originally mentioned in #212, but in light of @odow's work in jump-dev/JuMP.jl#3386, I think this deserves a dedicated issue.
I think this is definitely a feature that should be explored, to nudge people towards more thorough docstrings etc.
One thing we could also do is generate backlinks from those reference pages to (1) where the docstring is referenced with at-ref, and (2) if we simultaneously allow including the docstrings in-line (related: #1079), we should also backlink to those.
I do think this should be done, in the first iteration, as a plugin package. Once that stabilizes, we could integrate it into Documenter-proper.
The text was updated successfully, but these errors were encountered: