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

needs documentation #5

Open
alcohol opened this issue Jun 30, 2016 · 7 comments
Open

needs documentation #5

alcohol opened this issue Jun 30, 2016 · 7 comments

Comments

@alcohol
Copy link
Owner

alcohol commented Jun 30, 2016

I'm considering (either, or both) the following 2 options:

  • extend readme with some basic examples;
  • create api documentation and use the gh-pages branch.
@robjbrain
Copy link

Any chance of getting some documentation on this? It's not at all clear how to use it as it stands?

@alcohol
Copy link
Owner Author

alcohol commented Sep 13, 2016

The chance is quite high. It is more a question of when. I have limited time available. Anyone can contribute this if they want to. Simply add relevant document(s) to the docs folder.

The first thing that should be documented is the interface (it is really quite trivial), which can be found in DataProvider.php.

After that, documentation can be extended to include details about how to load a customized dataset and such (but this is less important, cause anyone going down this path can probably figure it out from the code themselves).

alcohol added a commit that referenced this issue Sep 14, 2016
@davidjeddy
Copy link

davidjeddy commented Sep 21, 2016

Idea: Run phpDocumentor over the project and publish to gh-pages? I know it is not an all inclusive solution but would provide a start. I'd be happy to do this for you @alcohol.

@alcohol
Copy link
Owner Author

alcohol commented Sep 22, 2016

That only provides a very basic API summary. I've added the interface methods already. You're free to add the phpdoc output to the existing docs. See the docs directory. I don't publish the docs through a gh-pages branch, since that is no longer necessary after the changes Github introduced.

@davidjeddy
Copy link

Per comment on #30 (comment) ; what did you have in mind for documentation?

@alcohol
Copy link
Owner Author

alcohol commented Sep 29, 2016

Just another one or two pages on top of what is currently in docs/. A very brief description of the methods, their signature, and perhaps explaining what they do (if it isn't obvious from the name and signature yet).

@davidjeddy
Copy link

Ah, ok. Now I understand what you were looking for.

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