Front End Code for the MassEnergize Community Portal. The community portal is customized for each participating community, and has the canonical URL https://community.massenergize.org/<community-name>/. For example, https://community.massenergize.org/wayland/.
As a user of the website, I want to understand better what teams are, why they matter, and how to use them, so that I can make an informed decision about whether or not to create a team, and have access to tips, tricks, guides, and examples so that I can make the most of my Team.
Additional details/context
On the main Teams page, the language about teams should be improved upon, and there should be a link to a Guide to Teams page that contains the rest of the information. This Guide is probably best kept up centrally, rather than expecting each instance of the platform to write/maintain their own guid.
Value added
The current representation of teams is very sparse, and I expect that the adoption of teams, and the effective use of teams, would increase if there was better documentation that explained what they are, how to use them, etc.
Acceptance criteria
This seems like a relatively light lift. The first part is simply updating the language about teams on the Teams landing page. The second part is creating a centralized guide. I am happy to help with writing the copy for both parts.
User Story
As a user of the website, I want to understand better what teams are, why they matter, and how to use them, so that I can make an informed decision about whether or not to create a team, and have access to tips, tricks, guides, and examples so that I can make the most of my Team.
Additional details/context
On the main Teams page, the language about teams should be improved upon, and there should be a link to a Guide to Teams page that contains the rest of the information. This Guide is probably best kept up centrally, rather than expecting each instance of the platform to write/maintain their own guid.
Value added
The current representation of teams is very sparse, and I expect that the adoption of teams, and the effective use of teams, would increase if there was better documentation that explained what they are, how to use them, etc.
Acceptance criteria
This seems like a relatively light lift. The first part is simply updating the language about teams on the Teams landing page. The second part is creating a centralized guide. I am happy to help with writing the copy for both parts.