WIP: Made how to contribution section an added some content

src/_data/tagList.js

@@ -24,6 +24,7 @@ module.exports = {
 				"Comment créer des documents accessibles dans Office 2016",
 			microsoft365:
 				"Comment créer des documents accessibles dans Microsoft 365",
+			rolesInvolvedInAccessibility: "Rôles impliqués pour garantir l'accessibilité du Web",
 		},
 		en: {
 			aboutDisabilities: "Most Common Types of Disability",
@@ -47,6 +48,7 @@ module.exports = {
 			mainAbout: "About us section on homepage",
 			office2016: "How to create accessible documents in Office 2016",
 			microsoft365: "How to create accessible documents in Microsoft 365",
+			rolesInvolvedInAccessibility: "Roles Involved in for ensuring web accessibility",
 		},
 	},
 	subjects: {

src/main/en/about-us/how-you-can-contribute.njk

@@ -0,0 +1,30 @@
+---
+title: How you can contribute
+description: How to contribute.
+toggle: comment-contribuer
+tags: aboutUs
+---
+
+{% if collections.rolesInvolvedInAccessibility === undefined %}
+
+	{% include "partials/alert-landingpages.njk" %}
+
+{% else %}
+
+<div class="row wb-eqht mrgn-tp-lg gc-drmt">
+	{% for item in collections.rolesInvolvedInAccessibility | sort(false, false, 'data.title') | localeMatch(locale) %}
+		{% if item.data.tags[1] != "rolesInvolvedInAccessibility" %}
+			<div class="col-md-6">
+				<h3><a href="{{ item.url }}">{{ item.data.title | safe }}</a></h3>
+				<p>
+					{% if item.data.description %}
+					{{ item.data.description | safe }}
+					{% else %}
+					{{ landingPage[locale].descriptionNoneText }}
+					{% endif %}
+				</p>
+			</div>
+		{% endif %}
+	{% endfor %}
+</div>
+{% endif %}

src/main/fr/a-propos-de-nous/comment-contribuer.njk

@@ -0,0 +1,30 @@
+---
+title: Comment contribuer
+description: Comment contribuer
+toggle: how-you-can-contribute
+tags: aboutUs
+---
+
+{% if collections.rolesInvolvedInAccessibility === undefined %}
+
+	{% include "partials/alert-landingpages.njk" %}
+
+{% else %}
+
+<div class="row wb-eqht mrgn-tp-lg gc-drmt">
+	{% for item in collections.rolesInvolvedInAccessibility | sort(false, false, 'data.title') | localeMatch(locale) %}
+		{% if item.data.tags[1] != "rolesInvolvedInAccessibility" %}
+			<div class="col-md-6">
+				<h3><a href="{{ item.url }}">{{ item.data.title | safe }}</a></h3>
+				<p>
+					{% if item.data.description %}
+					{{ item.data.description | safe }}
+					{% else %}
+					{{ landingPage[locale].descriptionNoneText }}
+					{% endif %}
+				</p>
+			</div>
+		{% endif %}
+	{% endfor %}
+</div>
+{% endif %}

src/pages/en/how-you-can-contribute/administration-group.md

@@ -0,0 +1,54 @@
+---
+title: Administration Group
+description: Focuses on effective product ownership, project management, and governance to enhance digital accessibility for the Government of Canada.
+tags: rolesInvolvedInAccessibility
+toggle: groupe-d-administration
+subject:
+  - aboutUs
+---
+
+## Comprehensive guide for GitHub collaboration:
+
+- **Understand the DAT Task Force:**
+  - Carefully read the [Terms of Reference (ToR)](https://github.com/gc-da11yn/gc-da11yn.github.io/discussions) document to grasp the overall mission, objectives, and scope of the DAT Task Force.
+
+- **Engage Actively in Discussions:**
+  - Regularly participate in the [GitHub discussion forum](https://github.com/gc-da11yn/gc-da11yn.github.io/discussions) to stay up-to-date with ongoing conversations.
+  - Bring your administrative expertise to discussions, share valuable insights, and collaborate effectively with other stakeholders.
+
+- **Provide Administrative Feedback:**
+  - Identify and document administrative-related issues, challenges, or areas for improvement within your specific expertise.
+  - Utilize GitHub issues to clearly communicate administrative problems and propose solutions. Adhere to provided templates for consistency.
+
+- **Participate in Meetings:**
+  - Attend the weekly DAT Task Force meetings hosted on GitHub or other collaboration platforms.
+  - Actively contribute to the agenda items, offering your administrative insights and engaging in discussions with fellow contributors.
+
+- **Contribute to Project Management via GitHub:**
+  - **Create Issues for Project Management Challenges:**
+    - Use GitHub issues to meticulously report specific project management problems or propose improvements within the realm of DAT projects.
+    - Clearly articulate the issue, its impact, and suggest viable project management solutions.
+  - **Submit Project Management Plans:**
+    - If your group has developed project management plans, follow the detailed [Development Guide](https://github.com/gc-da11yn/gc-da11yn.github.io/blob/main/.github/DEVELOPMENT.md).
+    - Initiate pull requests to seamlessly integrate your project management plans into the DAT.
+    - Utilize the provided [Pull Request Template](https://github.com/gc-da11yn/gc-da11yn.github.io/blob/main/.github/PULL_REQUEST_TEMPLATE.md) for a standardized submission.
+
+- **Stay Informed and Attend Meetings:**
+  - Regularly review materials shared on GitHub to stay abreast of the evolving progress of the project.
+  - Consistently attend meetings to understand the decisions made within the task force that may impact your administrative role.
+
+- **Share Administrative Expertise:**
+  - Leverage the collective expertise of your Administration Role Group to provide nuanced insights into product ownership, project management, and governance.
+  - Offer best practices, guidelines, or pertinent information that can significantly enhance the effectiveness of administrative processes within the DAT.
+
+- **Participate in the Annual Review:**
+  - Actively engage in the annual review of the Terms of Reference.
+  - Provide constructive feedback on potential adjustments or improvements to ensure the task force aligns seamlessly with evolving needs.
+
+- **Explore External Collaborations in Administration:**
+  - Explore opportunities for collaboration with external entities or jurisdictions with expertise in administrative roles.
+  - Share administrative insights and learnings with the broader community to foster collaborative endeavors.
+
+- **Promote Effective Administration for Accessibility:**
+  - Advocate passionately for administrative practices that prioritize digital accessibility and align with best practices.
+  - Promote the importance of effective product ownership, project management, and governance within the Government of Canada (GC) to ensure successful DAT initiatives.

src/pages/en/how-you-can-contribute/analysis-group.md

@@ -0,0 +1,54 @@
+---
+title: Analysis Group
+description: Focuses on data-driven insights and collaboration to enhance digital accessibility for the Government of Canada.
+tags: rolesInvolvedInAccessibility
+toggle: groupe-d-analyse
+subject:
+  - aboutUs
+---
+
+## Comprehensive guide for GitHub collaboration:
+
+- **Understand the DAT Task Force:**
+  - Carefully read the [Terms of Reference (ToR)](https://github.com/gc-da11yn/gc-da11yn.github.io/discussions) document to grasp the overall mission, objectives, and scope of the DAT Task Force.
+
+- **Engage Actively in Discussions:**
+  - Regularly participate in the [GitHub discussion forum](https://github.com/gc-da11yn/gc-da11yn.github.io/discussions) to stay up-to-date with ongoing conversations.
+  - Bring your analytical expertise to discussions, share valuable insights, and collaborate effectively with other stakeholders.
+
+- **Provide Analysis Feedback:**
+  - Identify and document analysis-related issues, challenges, or areas for improvement within your specific expertise.
+  - Utilize GitHub issues to clearly communicate analysis problems and propose solutions. Adhere to provided templates for consistency.
+
+- **Participate in Meetings:**
+  - Attend the weekly DAT Task Force meetings hosted on GitHub or other collaboration platforms.
+  - Actively contribute to the agenda items, offering your analysis insights and engaging in discussions with fellow contributors.
+
+- **Contribute Data-Driven Insights via GitHub:**
+  - **Create Issues for Analysis Challenges:**
+    - Use GitHub issues to meticulously report specific analysis problems or propose improvements within the realm of data-driven insights.
+    - Clearly articulate the issue, its impact, and suggest viable analysis solutions.
+  - **Submit Data-Driven Reports:**
+    - If your group has developed data-driven insights, follow the detailed [Development Guide](https://github.com/gc-da11yn/gc-da11yn.github.io/blob/main/.github/DEVELOPMENT.md).
+    - Initiate pull requests to seamlessly integrate your analysis reports into the DAT.
+    - Utilize the provided [Pull Request Template](https://github.com/gc-da11yn/gc-da11yn.github.io/blob/main/.github/PULL_REQUEST_TEMPLATE.md) for a standardized submission.
+
+- **Stay Informed and Attend Meetings:**
+  - Regularly review materials shared on GitHub to stay abreast of the evolving progress of the project.
+  - Consistently attend meetings to understand the decisions made within the task force that may impact your analysis role.
+
+- **Share Analysis Expertise:**
+  - Leverage the collective expertise of your Analysis Group to provide nuanced insights into data-driven analysis.
+  - Offer best practices, guidelines, or pertinent information that can significantly enhance the quality of analysis shared through the DAT.
+
+- **Participate in the Annual Review:**
+  - Actively engage in the annual review of the Terms of Reference.
+  - Provide constructive feedback on potential adjustments or improvements to ensure the task force aligns seamlessly with evolving needs.
+
+- **Explore External Analysis Collaborations:**
+  - Explore opportunities for collaboration with external entities or jurisdictions with expertise in data-driven analysis.
+  - Share analysis insights and learnings with the broader community to foster collaborative endeavors.
+
+- **Promote Data-Driven Decision Making:**
+  - Advocate passionately for analysis that prioritizes data-driven decision-making and aligns with accessibility standards.
+  - Promote the importance of data-driven analysis within the Government of Canada (GC) and actively encourage the adoption of best practices.

src/pages/en/how-you-can-contribute/author-group.md

@@ -0,0 +1,61 @@
+---
+title: Author Group
+description: Responsible for creating all text presented by the deliverable in all forms (HTML, audio, video). Defines or selects the standards the content should meet and processes for its review and preparation.
+tags: rolesInvolvedInAccessibility
+toggle: groupe-d-auteur
+subject:
+  - aboutUs
+---
+
+## Comprehensive guide for GitHub collaboration:
+
+- **Familiarize with DAT Task Force Objectives:**
+   - Review the [Terms of Reference (ToR)](https://github.com/gc-da11yn/gc-da11yn.github.io/discussions) document to understand the mission, key roles, and focus areas of the DAT Task Force.
+
+- **Engage in Content Planning:**
+   - Participate in discussions related to content structure, topics, and organization on the [GitHub discussion forum](https://github.com/gc-da11yn/gc-da11yn.github.io/discussions).
+   - Contribute ideas on what content should be posted, how it should be organized, and the overall publishing strategy.
+
+- **Content Creation:**
+   - Contribute to content creation using the authoring tool, [Netlify CMS](https://www.netlifycms.org/), following guidelines outlined in the [Development Guide](DEVELOPMENT.md).
+   - Ensure content adheres to best practices for accessibility and inclusive design.
+
+- **GitHub Interaction:**
+   - Engage with GitHub by creating issues for content-related challenges, improvements, or ideas.
+   - Discuss content-related topics openly, ensuring feedback is vetted before posting.
+   - Collaborate with other contributors through pull requests and reviews.
+   - Use the provided [Pull Request Template](https://github.com/gc-da11yn/gc-da11yn.github.io/blob/main/.github/PULL_REQUEST_TEMPLATE.md) when submitting pull requests.
+
+- **Attend Task Force Meetings:**
+   - Attend weekly DAT Task Force meetings to stay updated on content-related decisions and contribute to discussions.
+   - Collaborate with other stakeholders to align content creation with overarching goals.
+
+- **Collaborate with Other Role Groups:**
+   - Work closely with the Analysis Role Group to incorporate analysis findings into content.
+   - Collaborate with the Development Role Group to ensure seamless content publishing using Netlify CMS.
+
+- **Conduct Publishing Training:**
+   - If necessary, provide training sessions on the use of Netlify CMS for other content authors.
+   - Ensure content authors are aware of best practices for accessibility and content quality.
+
+- **GitHub Contributions:**
+   - Create GitHub issues for any challenges faced during content creation or publishing.
+   - Collaborate with the development team to address technical issues hindering content publishing.
+   - Actively participate in GitHub discussions, providing constructive input and feedback.
+
+- **Testing and Maintenance:**
+   - Participate in establishing a maintenance cycle, including regular testing of the site's functionality and accessibility.
+   - Contribute to the review of current content and the addition of new content as needed.
+
+- **Promote Content Accessibility:**
+   - Advocate for content that aligns with accessibility standards and guidelines.
+   - Share best practices for accessible content creation within the GC.
+
+- **Annual Review Involvement:**
+   - Actively participate in the annual review of the Terms of Reference.
+   - Provide feedback on adjustments or improvements related to content authoring and publishing.
+
+- **External Collaboration:**
+   - Explore opportunities for collaboration with external entities or jurisdictions with expertise in content creation and publishing.
+   - Share insights and learnings with the broader community.
+   - Foster collaborative efforts on GitHub by participating in discussions with external contributors.

src/pages/en/how-you-can-contribute/design-group.md

@@ -0,0 +1,54 @@
+---
+title: Design Group
+description: These roles define the general “look and feel” of the products covering presentation, functionality, features, operation. They translate input from business roles into user stories, requirements, specifications, documentation, guidelines used by other roles (mainly Development) to build the finish product. This includes applying research and understanding of the intended audiences for a quality experience.
+tags: rolesInvolvedInAccessibility
+toggle: groupe-de-conception
+subject:
+  - aboutUs
+---
+
+## Comprehensive guide for GitHub collaboration:
+
+- **Understand the DAT Task Force:**
+   - Thoroughly read and comprehend the [Terms of Reference (ToR)](https://github.com/gc-da11yn/gc-da11yn.github.io/discussions) document to gain a comprehensive understanding of the purpose, goals, and scope of the DAT Task Force.
+
+- **Engage in Discussions:**
+   - Actively participate in the [GitHub discussion forum](https://github.com/gc-da11yn/gc-da11yn.github.io/discussions) to stay informed about ongoing discussions.
+   - Bring your design expertise to discussions, share valuable insights, and collaborate effectively with other stakeholders.
+
+- **Provide Design Feedback:**
+   - Identify design-related issues, challenges, or areas for improvement within your expertise.
+   - Create well-documented GitHub issues, ensuring adherence to provided templates for consistency.
+
+- **Attend Meetings:**
+   - Attend the weekly DAT Task Force meetings, hosted on GitHub or other collaboration platforms.
+   - Contribute proactively to the agenda items, share your design expertise, and actively engage in discussions.
+
+- **Contribute Visual Designs via GitHub:**
+   - **Create Issues:**
+      - Use GitHub issues to meticulously report specific design problems or propose improvements within the realm of visual design.
+      - Clearly articulate the issue, its impact, and, if feasible, suggest viable design solutions.
+   - **Submit Visual Design Mockups:**
+      - If your group has developed visual designs, follow the [Development Guide](https://github.com/gc-da11yn/gc-da11yn.github.io/blob/main/.github/DEVELOPMENT.md).
+      - Initiate pull requests to seamlessly integrate your visual designs into the DAT.
+      - Refer to the provided [Pull Request Template](https://github.com/gc-da11yn/gc-da11yn.github.io/blob/main/.github/PULL_REQUEST_TEMPLATE.md) for a standardized submission.
+
+- **Stay Informed:**
+   - Regularly review materials shared on GitHub to stay abreast of the evolving progress of the project.
+   - Attend meetings consistently to grasp the decisions made within the task force that may impact your design role.
+
+- **Share Design Expertise:**
+   - Leverage the collective expertise of your Design Role Group to provide nuanced insights into visual design and user experience.
+   - Offer best practices, guidelines, or pertinent information that can significantly enhance the quality of designs shared through the DAT.
+
+- **Annual Review Participation:**
+   - Actively participate in the annual review of the Terms of Reference.
+   - Provide constructive feedback on potential adjustments or improvements to ensure the task force aligns seamlessly with evolving needs.
+
+- **External Design Collaborations:**
+   - Explore opportunities for collaboration with external entities or jurisdictions with expertise in design.
+   - Share design insights and learnings with the broader community.
+
+- **Promote User-Centric Design:**
+   - Advocate for designs that prioritize user experience and align with accessibility standards.
+   - Promote the importance of user-centric design within the Government of Canada (GC) and actively encourage the adoption of best practices.