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

Document code #48

Open
ericholiveira opened this issue May 13, 2016 · 6 comments
Open

Document code #48

ericholiveira opened this issue May 13, 2016 · 6 comments

Comments

@ericholiveira
Copy link
Owner

We must document studio code and use some lib to generate documentation from it. Any ideas on the lib?

@avishnyak
Copy link
Contributor

I tend to use DocStrap (a JSDoc3-based doc generator) because it's easy to get running, everyone understands JSDoc, is themeable, has search built in and has the ability to add markdown tutorials right to the final output.

Here is an example including tutorials:
http://docstrap.github.io/docstrap/themes/flatly/index.html

@sean-hill
Copy link

@ericholiveira I really like gitbook. It's really sexy and simple to use. Check out featherjs as an example. It's also easy to use with Github, so that's a plus 👍

@sean-hill
Copy link

sean-hill commented May 14, 2016

@ericholiveira we could also create a Studio github organization because it sounds like we'll have multiple repositories, and it'd be helpful to not have them all under your own github account, and have us all as members instead.

@sean-hill
Copy link

@ericholiveira as an example I threw this together really quick.

Gitbook example

@ericholiveira
Copy link
Owner Author

@sean-hill i completely agree with a Studio organization, thats the reason ive been asking you guys about your vision on the future of the project to make sure we are all on the same page. Also, i loved this gitbook, its possible to generate api documentation from codes comments like jsdoc? If its not possible, can we integrate both (jsdoc and gitbook)?

@avishnyak
Copy link
Contributor

avishnyak commented May 14, 2016

@ericholiveira we can probably make jsdoc to gitbook happen by using jsdoc-to-markdown as part of the build steps.

Also, here is an example of what looks like gitbook documentation that is similar to Studio.

https://www.serfdom.io/docs/index.html

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

No branches or pull requests

3 participants