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

Redo documentation #136

Open
sglyon opened this issue Aug 16, 2016 · 3 comments
Open

Redo documentation #136

sglyon opened this issue Aug 16, 2016 · 3 comments

Comments

@sglyon
Copy link
Member

sglyon commented Aug 16, 2016

Our documentation is woefully out of date.

It's time for an update.

I propose we make the following changes:

  • Use Documenter.jl
  • Use DocStringExtensions.jl to automate a lot of our docstrings (insert function signatures, type fields, etc.)
  • Lighten up the docstring syntax/structure. Right now we are kind of following python conventions, but it doesn't feel quite as natural in Julia. This happened because we were one of the first packages to have docstrings and docstring generated online docs. Since then, a community standard has emerged that mostly mimics Base julia. If you work on this and don't know what to put I suggest the following:
    • Look at Documenter.jl, DocStringExtensions.jl, and Base julia for examples of what their docstrings look like. The former two packages there should give you an idea of how to use the automation tools in DocStringExtensions.jl
    • Open an issue or PR with a proposed doctoring change and the team can give feedback/guidance on the changes.
  • Split the documentation into two parts:
    1. A user guide that goes over installation and usage. This section would include some examples and tutorials
    2. An API section where we just dump all the docstring info we will be re-writing.
@jstac
Copy link
Contributor

jstac commented Aug 16, 2016

@spencerlyon2 Thanks for putting this together. It would be great to see progress.

@sbromberger
Copy link

We just converted to Documenter over in LG. Overall it's great. It requires github pages for hosting if you don't have it already. Feel free to ask questions or take a look at our scripts if you need some inspiration. The Documenter folks are also really willing to help.

@sglyon
Copy link
Member Author

sglyon commented Sep 13, 2016

Thank you for the heads up. I have used Documenter in a couple packages and it worked out really well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants