Merge pull request #57 from DSACMS/nat/readme-updates2

README Updates: About The Project Subsections and Minor Revisions

tier1/{{cookiecutter.project_slug}}/README.md

@@ -1,11 +1,21 @@
 ## **{Project Name}**
-
 **{project description}**
 
 ## About the Project
-
 **{project statement}**
 
+<!-- 
+### Project Mission
+**{project mission}** -->
+
+<!-- 
+### Agency Mission
+# TODO: Must include since this is an agency-led project -->
+
+<!-- 
+### Team Mission
+# TODO: Must include since this is an agency-led project -->
+
 ## Core Team
 
 An up-to-date list of core team members can be found in [MAINTAINERS.md](MAINTAINERS.md). At this time, the project is still building the core team and defining roles and responsibilities. We are eagerly seeking individuals who would like to join the community and help us define and fill these roles.
@@ -56,7 +66,7 @@ The **{project name}** team is taking a community-first and open source approach
 
 We know that we can learn from a wide variety of communities, including those who will use or will be impacted by the tool, who are experts in technology, or who have experience with similar technologies deployed in other spaces. We are dedicated to creating forums for continuous conversation and feedback to help shape the design and development of the tool.
 
-We also recognize capacity building as a key part of involving a diverse open source community. We are doing our best to use accessible language, provide technical and process documents in multiple languages, and offer support to community members with a wide variety of backgrounds and skillsets.
+We also recognize capacity building as a key part of involving a diverse open source community. We are doing our best to use accessible language, provide technical and process documents, and offer support to community members with a wide variety of backgrounds and skillsets.
 
 ### Community Guidelines
 

tier2/{{cookiecutter.project_slug}}/README.md

@@ -4,7 +4,20 @@
 ## About the Project
 **{project statement}**
 
+### Project Vision
+**{project vision}**
+
+### Project Mission
+**{project mission}**
+
+### Agency Mission
+<!-- # TODO: Must include since this is an agency-led project -->
+
+### Team Mission
+<!-- # TODO: Must include since this is an agency-led project -->
+
 ## Core Team
+
 An up-to-date list of core team members can be found in [MAINTAINERS.md](MAINTAINERS.md). At this time, the project is still building the core team and defining roles and responsibilities. We are eagerly seeking individuals who would like to join the community and help us define and fill these roles.
 
 <!--
@@ -55,7 +68,7 @@ The **{project name}** team is taking a community-first and open source approach
 
 We know that we can learn from a wide variety of communities, including those who will use or will be impacted by the tool, who are experts in technology, or who have experience with similar technologies deployed in other spaces. We are dedicated to creating forums for continuous conversation and feedback to help shape the design and development of the tool.
 
-We also recognize capacity building as a key part of involving a diverse open source community. We are doing our best to use accessible language, provide technical and process documents in multiple languages, and offer support to community members with a wide variety of backgrounds and skillsets. 
+We also recognize capacity building as a key part of involving a diverse open source community. We are doing our best to use accessible language, provide technical and process documents, and offer support to community members with a wide variety of backgrounds and skillsets. 
 
 ### Community Guidelines
 Principles and guidelines for participating in our open source community are can be found in [COMMUNITY_GUIDELINES.md](COMMUNITY_GUIDELINES.md). Please read them before joining or starting a conversation in this repo or one of the channels listed below. All community members and participants are expected to adhere to the community guidelines and code of conduct when participating in community spaces including: code repositories, communication channels and venues, and events. 

tier3/{{cookiecutter.project_slug}}/README.md

@@ -4,6 +4,22 @@
 ## About the Project
 **{project statement}**
 
+<!--- 
+### Project Vision
+**{project vision}** -->
+
+<!-- 
+### Project Mission
+**{project mission}** -->
+
+<!-- 
+### Agency Mission
+# TODO: Must include since this is an agency-led project -->
+
+<!-- 
+### Team Mission
+# TODO: Must include since this is an agency-led project -->
+
 ## Core Team
 An up-to-date list of core team members can be found in [MAINTAINERS.md](MAINTAINERS.md). At this time, the project is still building the core team and defining roles and responsibilities. We are eagerly seeking individuals who would like to join the community and help us define and fill these roles.
 
@@ -54,7 +70,7 @@ The **{project name}** team is taking a community-first and open source approach
 
 We know that we can learn from a wide variety of communities, including those who will use or will be impacted by the tool, who are experts in technology, or who have experience with similar technologies deployed in other spaces. We are dedicated to creating forums for continuous conversation and feedback to help shape the design and development of the tool.
 
-We also recognize capacity building as a key part of involving a diverse open source community. We are doing our best to use accessible language, provide technical and process documents in multiple languages, and offer support to community members with a wide variety of backgrounds and skillsets. 
+We also recognize capacity building as a key part of involving a diverse open source community. We are doing our best to use accessible language, provide technical and process documents, and offer support to community members with a wide variety of backgrounds and skillsets. 
 
 ### Community Guidelines
 Principles and guidelines for participating in our open source community are can be found in [COMMUNITY_GUIDELINES.md](COMMUNITY_GUIDELINES.md). Please read them before joining or starting a conversation in this repo or one of the channels listed below. All community members and participants are expected to adhere to the community guidelines and code of conduct when participating in community spaces including: code repositories, communication channels and venues, and events. 

tier4/{{cookiecutter.project_slug}}/README.md

@@ -4,6 +4,14 @@
 ## About the Project
 **{project_statement}**
 
+<!--- 
+### Project Vision
+**{project vision}** -->
+
+<!-- 
+### Project Mission
+**{project mission}** -->
+
 ## Core Team
 An up-to-date list of core team members can be found in [MAINTAINERS.md](MAINTAINERS.md). At this time, the project is still building the core team and defining roles and responsibilities. We are eagerly seeking individuals who would like to join the community and help us define and fill these roles.
 
@@ -56,7 +64,7 @@ The **{project_name}** team is taking a community-first and open source approach
 
 We know that we can learn from a wide variety of communities, including those who will use or will be impacted by the tool, who are experts in technology, or who have experience with similar technologies deployed in other spaces. We are dedicated to creating forums for continuous conversation and feedback to help shape the design and development of the tool.
 
-We also recognize capacity building as a key part of involving a diverse open source community. We are doing our best to use accessible language, provide technical and process documents in multiple languages, and offer support to community members with a wide variety of backgrounds and skillsets. 
+We also recognize capacity building as a key part of involving a diverse open source community. We are doing our best to use accessible language, provide technical and process documents, and offer support to community members with a wide variety of backgrounds and skillsets. 
 
 ### Community Guidelines
 Principles and guidelines for participating in our open source community are can be found in [COMMUNITY_GUIDELINES.md](COMMUNITY_GUIDELINES.md). Please read them before joining or starting a conversation in this repo or one of the channels listed below. All community members and participants are expected to adhere to the community guidelines and code of conduct when participating in community spaces including: code repositories, communication channels and venues, and events.