microsoft · Roman-Pilip · Jun 10, 2026 · Jun 10, 2026 · Jun 10, 2026 · Jun 11, 2026
diff --git a/CommonDataModelforNonprofits/README.md b/CommonDataModelforNonprofits/README.md
@@ -1,8 +1,8 @@
 # Common Data Model for Nonprofits
 
-The Common Data Model for Nonprofits (CDM) is an open source data schema that provides a common foundation for nonprofit solutions. It is made up of entities and attributes commonly used by nonprofits across fundraising, constituent management, awards, program delivery, and impact tracking. It reflects industry best practices and promotes cross-solution and cross-organization data integration, enabling powerful insights across activities and departments.
+Common Data Model for Nonprofits is an open source data schema that provides a common foundation for nonprofit solutions. It is made up of entities and attributes commonly used by nonprofits across fundraising, constituent management, awards, program delivery, and impact tracking. It reflects industry best practices and promotes cross-solution and cross-organization data integration, enabling powerful insights across activities and departments.
 
-The CDM provides a foundation for vendors, partners, and nonprofits to map their applications and connectors for data and application interoperability.
+Common Data Model for Nonprofits provides a foundation for vendors, partners, and nonprofits to map their applications and connectors for data and application interoperability.
 
 Learn more with [Common Data Model for Nonprofits documentation](https://aka.ms/DocsCDMforNonprofits).
 

diff --git a/Documents/dataverse-build-and-deploy.md b/Documents/dataverse-build-and-deploy.md
@@ -29,7 +29,7 @@ Before building or deploying a Dataverse solution, ensure you have the following
 - A **valid authentication method** for `pac auth create` (e.g., username/password, client ID & secret, certificate-based auth).
 
 ### 🏛 Required Data Model
-Before installing Fundraising, Outcome Management, Grant Management, or any other nonprofit solutions based on Dataverse, ensure that the Common Data Model (CDM) for Nonprofits is installed first.
+Before you install Fundraising, Grant Management, Outcome Management, Volunteer Management, or another solution built on Dataverse, install Common Data Model for Nonprofits first.
 
 This ensures compatibility and proper data structure alignment for all dependent solutions.
 

diff --git a/Documents/img/volunteer-engagement-home-page.png b/Documents/img/volunteer-engagement-home-page.png
diff --git a/Documents/portal-build-and-deploy.md b/Documents/portal-build-and-deploy.md
diff --git a/Fundraising/README.md b/Fundraising/README.md
@@ -9,7 +9,7 @@ Fundraising aggregates constituent and fundraising data across various constitue
 - View a comprehensive donation history for individual and organizational donors.
 - Process gifts, import donations, and generate receipt data.
 
-Fundraising is built on the [Common Data Model (CDM) for Nonprofits](https://aka.ms/GitHubCDMforNonprofits), an industry-led, open-source data schema that reflects industry best practices and connects data across the organization to enable powerful interoperability, fuel greater insight and efficacy, and provide data transparency. With the CDM and Power Platform as the foundation, Fundraising connects with other platforms and applications in a seamless data flow, increasing operational efficiency and enabling data-driven decision-making.
+Fundraising is built on [Common Data Model for Nonprofits](https://aka.ms/GitHubCDMforNonprofits), an industry-led, open-source data schema that reflects industry best practices and connects data across the organization to enable powerful interoperability, fuel greater insight and efficacy, and provide data transparency. With Common Data Model for Nonprofits and Microsoft Power Platform as the foundation, Fundraising connects with other platforms and applications in a seamless data flow, increasing operational efficiency and enabling data-driven decision-making.
 
 Learn More:
 - Read about Fundraising on [MS Learn](https://learn.microsoft.com/en-us/industry/nonprofit/fundraising)

diff --git a/GrantManagement/README.md b/GrantManagement/README.md
@@ -9,7 +9,7 @@ Grant Management aggregates constituent and grant data into a comprehensive prof
 - Track disbursements by type, amount, status, and schedule.
 - Aggregate reports and manage activities, providing insights into, and enabling proactive management of, stakeholders across the grant lifecycle.
 
-Grant Management is built on the [Common Data Model (CDM) for Nonprofits](https://aka.ms/GitHubCDMforNonprofits), an industry-led, open-source data schema that reflects industry best practices and connects data across the organization to enable powerful interoperability, fuel greater insight and efficacy, and provide data transparency. With the CDM and Power Platform as the foundation, Grant Management connects with other platforms and applications in a seamless data flow, increasing operational efficiency and enabling data-driven decision-making.
+Grant Management is built on [Common Data Model for Nonprofits](https://aka.ms/GitHubCDMforNonprofits), an industry-led, open-source data schema that reflects industry best practices and connects data across the organization to enable powerful interoperability, fuel greater insight and efficacy, and provide data transparency. With Common Data Model for Nonprofits and Microsoft Power Platform as the foundation, Grant Management connects with other platforms and applications in a seamless data flow, increasing operational efficiency and enabling data-driven decision-making.
 
 Learn More:
 - Read about Grant Management on [MS Learn](https://learn.microsoft.com/en-us/industry/nonprofit/grant-management)

diff --git a/OutcomeManagement/README.md b/OutcomeManagement/README.md
@@ -9,7 +9,7 @@ Outcome Management helps nonprofits manage the impact of programs, projects, and
 - Define and adapt programs and projects based on output, outcome, and results.
 - Manage impact indicators and measurements.
 
-Outcome Management is built on the [Common Data Model (CDM) for Nonprofits](https://aka.ms/GitHubCDMforNonprofits), an industry-led, open-source data schema that reflects industry best practices and connects data across the organization to enable powerful interoperability, fuel greater insight and efficacy, and provide data transparency. With the CDM and Power Platform as the foundation, Outcome Management connects with other platforms and applications in a seamless data flow, increasing operational efficiency and enabling data-driven decision-making.
+Outcome Management is built on [Common Data Model for Nonprofits](https://aka.ms/GitHubCDMforNonprofits), an industry-led, open-source data schema that reflects industry best practices and connects data across the organization to enable powerful interoperability, fuel greater insight and efficacy, and provide data transparency. With Common Data Model for Nonprofits and Microsoft Power Platform as the foundation, Outcome Management connects with other platforms and applications in a seamless data flow, increasing operational efficiency and enabling data-driven decision-making.
 
 Learn More:
 - Read about Outcome Management on [MS Learn](https://learn.microsoft.com/en-us/industry/nonprofit/outcome-management)

diff --git a/README.md b/README.md
@@ -23,7 +23,7 @@ The solutions contained in this repository are accelerators designed to make it
 | [Grant Management](./GrantManagement/README.md)           | Grant Management provides partners with a flexible, easily extensible foundation for building grant management solutions for nonprofit customers. | [Deploy](./Documents/dataverse-build-and-deploy.md) | [Documentation](https://learn.microsoft.com/en-us/industry/nonprofit/grant-management) |
 | [Nonprofit data solutions in Microsoft Fabric](./NonprofitDataSolutions/Fundraising/README.md) | Nonprofit data solutions in Microsoft Fabric consist of a preconfigured, scalable data architecture and analytics framework designed to help nonprofit organizations unify, transform, and analyze their data. | [Deploy](https://learn.microsoft.com/en-us/industry/nonprofit/deploy-nonprofit-data-solutions) | [Documentation](https://learn.microsoft.com/en-us/industry/nonprofit/nonprofit-data-solutions-overview) |
 | [Outcome Management](./OutcomeManagement/README.md)       | Outcome Management provides partners with a flexible, easily extensible foundation for building program measurement solutions for nonprofit customers. | [Deploy](./Documents/dataverse-build-and-deploy.md) | [Documentation](https://learn.microsoft.com/en-us/industry/nonprofit/outcome-management) |
-| [Volunteer Engagement](./VolunteerEngagement/README.md)   | Volunteer Engagement is a Power Page where volunteers can easily find and apply for engagement opportunities. | [Deploy](./Documents/portal-build-and-deploy.md) | [Documentation](https://learn.microsoft.com/en-us/industry/nonprofit/volunteer-engagement-use) |
+| [Volunteer Engagement](./VolunteerEngagement/README.md)   | Volunteer Engagement is a Power Pages React SPA where volunteers can find and apply for engagement opportunities. | [Deploy](./VolunteerEngagement/Portal-EDM/README.md) | [Documentation](./VolunteerEngagement/README.md) |
 | [Volunteer Management](./VolunteerManagement/README.md)   | Volunteer Management is a Power App that enables the management of day-to-day processes to recruit, onboard, and retain volunteers. | [Deploy](./Documents/dataverse-build-and-deploy.md) | [Documentation](https://learn.microsoft.com/en-us/industry/nonprofit/volunteer-management-use) |
 
 ---

diff --git a/VolunteerEngagement/.ai/coding-guidelines/README.md b/VolunteerEngagement/.ai/coding-guidelines/README.md
@@ -0,0 +1,36 @@
+# Coding Guidelines
+
+This folder contains AI assistant guidelines for maintaining code quality and consistency across the Volunteer Engagement Portal project.
+
+## 📁 Guidelines Structure
+
+### 📋 Current Guidelines
+- **`code-formatting.md`** - Code formatting standards using Prettier configuration (`Portal-EDM/.prettierrc.json`), ESLint rules, and import organization via `@trivago/prettier-plugin-sort-imports`
+- **`component-structure-standards.md`** - Strict component folder structure, naming conventions, file content standards, nesting strategy, barrel exports, and type system best practices
+
+### 🎯 Future Guidelines (planned)
+- **`refactoring-standards.md`** - Best practices for code refactoring and simplification
+- **`react-patterns.md`** - React component patterns (Fluent UI v9, React Router, context)
+- **`naming-conventions.md`** - Variable, function, and file naming standards
+- **`error-handling.md`** - Consistent error handling patterns
+- **`state-management.md`** - State management best practices
+- **`typescript-standards.md`** - TypeScript usage guidelines and type definitions
+
+## 🎯 Purpose
+
+These guidelines help AI assistants:
+1. **Maintain consistency** across the codebase
+2. **Follow established patterns** when making changes
+3. **Prevent common issues** like duplicate imports or inconsistent formatting
+4. **Apply best practices** automatically during refactoring
+5. **Ensure quality** in generated or modified code
+
+## 📝 Usage
+
+- Each guideline file contains specific, actionable instructions
+- Include real examples and anti-patterns
+- Reference these guidelines when making code changes
+- Update guidelines as patterns evolve
+
+---
+*These guidelines are specifically designed for AI assistant use to maintain codebase quality and consistency.*