Closed cormullion closed 1 year ago
Patch coverage: 93.75
% and no project coverage change.
Comparison is base (
baedd6d
) 94.34% compared to head (42adb97
) 94.34%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Many thanks for taking on this big task. I managed to build the documentation locally without any issues. There's obviously a lot to read through, but my first impression is that people will find the REPL experience much more pleasant now that you moved the LaTeX out into separate documents. The tutorial you wrote is also really nice, and in general the layout of the documentation feels like a great improvement.
One thing I notice is that imgradients
now has no more meaningful docstring. It might be worth retaining some parts of the previous docstring.
Can we please move this forward?It would be great to get this done, issa common gripe 😓
Can we please move this forward?It would be great to get this done, issa common gripe 😓
Best way to make that happen is to give it a thorough review! But you could wait until my comments above are addressed.
(I'm not too sure how you'd preview this...)
Would adding push_preview=true
fix that? https://documenter.juliadocs.org/stable/lib/public/#Documenter.deploydocs
@timholy Thanks so much for the comments and review, and for taking the time... I confess I don't understand the fine details of the package, but perhaps the structure of the docs is a bit better now, and in the future will allow people to add more information in the right place.
When I'm back from travels I'll build this locally and give it a read-through; assuming nothing serious comes up I'll merge as-is and we can fix minor problems later. Or if anyone else wants to build it and do that for me, just let me know the verdict and we can merge more quickly.
I built it locally, and it looks awesome. Thanks ever so much, @cormullion! A huge contribution!
Did these docs ever get released?
This PR comprises a suggested reorganization of the documentation. My approach is probably reasonably similar to the Divio style - at least, try to keep different types of information separate, so that novices, casual users, experienced users, and package developers don't trip over material not meant for them. (I think this is probably the opposite of Images' current approach (judging from this RFC issue.)
The main thing was just to add some hierarchy to the manual, then to move as much stuff out of the docstrings as possible (cf my previous pet gripe, all that LaTeX). 😂
(I'm not too sure how you'd preview this...)