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
Right now I think golang.org is heavily tied to the Go release cycle because it uses GoDoc.
Splitting the site and blog off into a Hugo site deployed to Google Cloud Storage or elsewhere could go a long ways towards reducing the friction of updating the website.
+1. Currently, I'm running "The Go Blog Japanese translation project" so that many JP Gophers can read great articles there. It would be great if many L10N project can contribute to the central repo if available.
I think the golang.org depending on the release cycle of Go makes things even worse because people cannot contribute to the documentation with examples and corrections without having to wait for a new release of Go.
Maybe a more flexible approach to this can / should be found as that would help increasing the interaction between contributors and potential new contributors. I've started my open-source experience contributing to the documentation of a framework and I still remember how exciting it was having the first PR merged and then visible on the website in a couple of hours.
:) This list will be plentiful.
Some relevant comments golang/go#21025
The text was updated successfully, but these errors were encountered: