-
Notifications
You must be signed in to change notification settings - Fork 70
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
Request for documenting the jco project #131
Comments
It would be amazing to work towards some consolidated documentation for the project. I'm very much open to suggestions with regards to structure and process, would be great to discuss / hear your thoughts further on this. All that to say, thanks for bringing this up and offering to help! |
Since you'll be (presumably) around during WasmCon, maybe we could catch up there to discuss this further? I can summarise the plan of action here, once done. |
Yes I'll be there, it would be great to discuss this, and thanks again for the interest. I'll leave this issue open to track further. |
Thanks so much @divya-mohan0209 for raising this and starting this conversation, and glad we could meet at Wasmcon. I've created a general tracking issue for an overall documentation effort for this project in #165. As we head towards stability this will be an important aspect of that stabilization for the project. Let's continue this conversation there, and please do feel free to open any other issues as you feel appropriate. |
Thank you for creating jco!
I wanted to propose a formal documentation consolidation effort for API reference & the project itself.
P.S. As a current docs maintainer for multiple projects & a former technical writer, I'd be happy to chip in and/or work together to see this through.
The text was updated successfully, but these errors were encountered: