Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upI would like take up the task of improving documentation #854
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
process-bot
Apr 18, 2017
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!
Here is what to expect next, and if anyone wants to comment, keep these things in mind.
process-bot
commented
Apr 18, 2017
|
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it! Here is what to expect next, and if anyone wants to comment, keep these things in mind. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
lukewestby
May 17, 2017
Member
Hey @anilreddykatta,
GitHub issues here are for reporting bugs. Ideas for how to improve something broader like documentation are best discussed on the elm-dev mailing list or the #elm-dev channel in slack
|
Hey @anilreddykatta, GitHub issues here are for reporting bugs. Ideas for how to improve something broader like documentation are best discussed on the elm-dev mailing list or the #elm-dev channel in slack |
anilreddykatta commentedApr 18, 2017
•
edited
Edited 1 time
-
anilreddykatta
edited Apr 18, 2017 (most recent)
Currently, most of the documentation is textual for some core modules without sample code and it's output. Do you guys think it's a good idea to have documentation with some sample code for core package? If yes, I can raise series of pull request to improve on those lines?
Also, thinking of providing a
replso a user can play in place without any installations?