Context:
These suggestions are assuming that the https://golang.org/project/ should get people excited and motivated about participating in the project. That they will be able to navigate through: what the project is and who it came from, what the community around the project looks like, how they can contribute and the future of the project. My suggestions will be more content and organization focused but the design and 'feel' of the site could use an upgrade as well.
Note: this page could use better design navigation for knowing what will be on the page. We could potentially start w/ a statement of intent about what the page will go over, but IMO that's not ideal.
I'll run through the page by referring to specific screenshots to indicate possible changes for future plans to rebuilding the pages.
Sketch for potenital changes:
- By who? Would feel more personal if we linked to a team pages or something here. The link to Google is misleading for some reason. Would be nice to define what a contributor is and their importance. “From the community” what community? I see no links or indication on the site that this is a thriving community….
-
IMO the word users should be avoided in most situations when describing a group of people. If we assume we want to give the feeling of ‘welcome’ then community members could be an alternative.
Directions unclear. Should be “We encourage all Go community members to join the golang-announce google group and subscribe to receive notifications.”
-
This whole section feels a little out of place, why is it here instead of under developer resources?
-
Also, is that newsletter the only option/ the only form of comm run by the go team?
- Build out an entire history section here... not just the versions. If you’re going to have a history portion we should include, where’s the meat on the project itself: who were the creators? Why did they create go? What was the vision?
- Super confusing that these are clickable, def doesn't feel accessible or clear on where I would go if I clicked.
- Are these all the resources? Who are they maintained by? How do I know if I should or should not opt in?
-
There have got to be more ways to help than this. (Add Experience Reports here!)
-
There are def other ways to contribute... it'd be nice to build out this section into more inclusive code, community, content.
Hmmm...
If these ideas sound on track, we can easily get more granular about the section, language, and information changes (although it should be a part of the entire site redesign.)
Context:
These suggestions are assuming that the https://golang.org/project/ should get people excited and motivated about participating in the project. That they will be able to navigate through: what the project is and who it came from, what the community around the project looks like, how they can contribute and the future of the project. My suggestions will be more content and organization focused but the design and 'feel' of the site could use an upgrade as well.
Note: this page could use better design navigation for knowing what will be on the page. We could potentially start w/ a statement of intent about what the page will go over, but IMO that's not ideal.
I'll run through the page by referring to specific screenshots to indicate possible changes for future plans to rebuilding the pages.
Sketch for potenital changes:
IMO the word users should be avoided in most situations when describing a group of people. If we assume we want to give the feeling of ‘welcome’ then community members could be an alternative.
Directions unclear. Should be “We encourage all Go community members to join the golang-announce google group and subscribe to receive notifications.”
This whole section feels a little out of place, why is it here instead of under developer resources?
Also, is that newsletter the only option/ the only form of comm run by the go team?
There have got to be more ways to help than this. (Add Experience Reports here!)
There are def other ways to contribute... it'd be nice to build out this section into more inclusive code, community, content.
Hmmm...
If these ideas sound on track, we can easily get more granular about the section, language, and information changes (although it should be a part of the entire site redesign.)