You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think one of the biggest pain points for GopherJS users (current and potential) is the lack of accessible and comprehensive user documentation. We have some bits scattered between the README, docs directory and wiki, but I wouldn't call that user-friendly.
A simple site with organized tutorials, documentation, FAQs, etc. would be a great improvement. It doesn't have to be anything sophisticated, just a static site would be more than enough, most of the effort would be dedicated to simply organizing the existing material and maybe filling in some gaps.
We already have GitHub Pages repository we could use. We could also pick up a per-made template like Docsy. AFAICT that's what TinyGo uses for their web site.
The text was updated successfully, but these errors were encountered:
As an alternative/suppliment, we could also take better advantage of GoDoc and the README.md, which requires no additional volunteer upkeep effort on our part.
I think one of the biggest pain points for GopherJS users (current and potential) is the lack of accessible and comprehensive user documentation. We have some bits scattered between the README, docs directory and wiki, but I wouldn't call that user-friendly.
A simple site with organized tutorials, documentation, FAQs, etc. would be a great improvement. It doesn't have to be anything sophisticated, just a static site would be more than enough, most of the effort would be dedicated to simply organizing the existing material and maybe filling in some gaps.
We already have GitHub Pages repository we could use. We could also pick up a per-made template like Docsy. AFAICT that's what TinyGo uses for their web site.
The text was updated successfully, but these errors were encountered: