Indhumathy-Loganathan · Oct 26, 2026 · Oct 12, 2026 · Oct 12, 2026 · Oct 12, 2026 · Oct 12, 2026
diff --git a/.github/ACCESSIBILITY.md b/.github/ACCESSIBILITY.md
@@ -2,6 +2,8 @@
 
 The Syncfusion Blazor Toolkit **aims to conform** to **WCAG 2.2 Level AA**.
 
+> Evidence and commitments last reviewed for package **2.0.1** (includes `SfThemeRoot` theme delivery and component CSS isolation). Re-validate after major theme or styling changes.
+
 ## What this means
 
 - Every interactive component in the toolkit exposes accessible
@@ -26,12 +28,13 @@ that is not yet satisfied, and the planned remediation.
 
 - Accessibility Insights FastPass / Assessment reports for major
   components are checked in under
-  [`.github/accessibility/insights-summary.md`](accessibility/insights-summary.md).
+  [`.github/accessibility/insights-summary.md`](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/accessibility/insights-summary.md).
 - Manual screen reader smoke notes for NVDA / JAWS / Narrator against
   the major components live next to it at
-  [`.github/accessibility/screen-reader-smoke.md`](accessibility/screen-reader-smoke.md).
+  [`.github/accessibility/screen-reader-smoke.md`](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/accessibility/screen-reader-smoke.md).
 - Conformance claims are regenerated before each major release and
   filed in the release ticket.
+- Formal VPAT: [`docs/VPAT-2.5-INT.md`](https://github.com/syncfusion/blazor-toolkit/blob/main/docs/VPAT-2.5-INT.md).
 
 ## Reporting issues
 
@@ -41,4 +44,4 @@ reader pairing, the component affected, and the WCAG success criterion
 that is failing.
 
 For private disclosure, contact [email protected] following
-[SECURITY.md](SECURITY.md).
+[SECURITY.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/SECURITY.md).
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
@@ -6,13 +6,24 @@ First and foremost: if you are thinking about contributing a bigger change or fe
 
 ## Code of Conduct
 
-Please see our [Code of Conduct](CODE_OF_CONDUCT.md).
+Please see our [Code of Conduct](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/CODE_OF_CONDUCT.md).
 
 ## Contributing Code
 
-Currently, we are in the beginning phases of building up the Syncfusion Toolkit for Blazor. Yet, we are still very excited for you to join us during this exciting time!
+The Syncfusion Toolkit for Blazor is an open-source, MIT-licensed package
+on a **2.x** release line. We welcome contributions of all sizes—bug fixes,
+tests, docs, accessibility, and new capabilities that fit the [roadmap](https://github.com/syncfusion/blazor-toolkit/blob/main/ROADMAP.md).
 
-Have a look at our [Development Guide](DEVELOPMENT.md) to learn about setting up your development environment.
+Have a look at our [Development Guide](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/DEVELOPMENT.md) to learn about setting up your development environment.
+
+### Repo map (quick)
+
+- Samples: open `samples/Blazor.Toolkit.Samples.slnx`
+  (`Blazor.Toolkit.Samples` host, `Blazor.Toolkit.Samples.Client` WASM).
+- Unit tests: `tests/Syncfusion.Blazor.Toolkit.BUnitTest/`
+- Browser tests: `tests/Syncfusion.Blazor.Playwright.Test/`
+- Prefer paths in [DEVELOPMENT.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/DEVELOPMENT.md) and the root
+  [README.md](../README.md) over short/legacy folder names.
 
 ### What to Work On
 
@@ -23,11 +34,11 @@ Follow the style used by the [.NET Foundation](https://github.com/dotnet/runtime
 - We do not use the `private` keyword, as it is the default accessibility level in C#.
 - We use hard tabs over spaces.
 
-Read and follow our [pull request template](PULL_REQUEST_TEMPLATE.md).
+Read and follow our [pull request template](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/PULL_REQUEST_TEMPLATE.md).
 
 ### Pull Request Requirements
 
-Please refer to our [pull request template](PULL_REQUEST_TEMPLATE.md).
+Please refer to our [pull request template](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/PULL_REQUEST_TEMPLATE.md).
 
 Please check the "Allow edits from maintainers" checkbox on your pull request. This allows us to make minor fixes and resolve conflicts for you quickly.
 

diff --git a/.github/DEVELOPMENT.md b/.github/DEVELOPMENT.md
@@ -3,14 +3,32 @@
 This page contains the steps to build and run the Syncfusion Toolkit for Blazor repository from source. If you are looking to build apps with the Syncfusion Toolkit for Blazor, please head over to the links in the [README](https://github.com/syncfusion/blazor-toolkit/blob/main/README.md) to get started.
 
 ## Initial setup
-   ### Windows
-   - Install Visual Studio 2022 (v17.10 or newer) with ASP.NET and web development workload.
-   - Install [.NET 8 SDK](https://dotnet.microsoft.com/download/dotnet/8.0).
-   - Clone the repository:
-     ```shell
-     git clone https://github.com/syncfusion/blazor-toolkit.git
-     cd blazor-toolkit
-     ```
+
+### Prerequisites (all platforms)
+
+- **.NET SDKs** for all supported target frameworks:
+  [.NET 8](https://dotnet.microsoft.com/download/dotnet/8.0),
+  [.NET 9](https://dotnet.microsoft.com/download/dotnet/9.0), and
+  [.NET 10](https://dotnet.microsoft.com/download/dotnet/10.0)
+  (or an install that provides SDKs for 8, 9, and 10).
+- **Node.js (LTS)** on `PATH` if project targets require it during pack/build.
+- Clone the repository:
+  ```shell
+  git clone https://github.com/syncfusion/blazor-toolkit.git
+  cd blazor-toolkit
+
+### Windows (primary)
+
+- Install Visual Studio 2022 (v17.10 or newer) with the ASP.NET and web development workload, or use the `dotnet` CLI alone.
+- Build: `dotnet build ./src/Syncfusion.Blazor.Toolkit.slnx`
+- Samples: open `samples/Blazor.Toolkit.Samples.slnx` in Visual Studio and set the desired startup project.
+
+### macOS / Linux
+- Use the `dotnet` CLI with the SDKs above.
+- Optional: VS Code or JetBrains Rider.
+- Build: `dotnet restore` then `dotnet build ./src/Syncfusion.Blazor.Toolkit.slnx`.
+- Samples: open `samples/Blazor.Toolkit.Samples.slnx` in a supported IDE, or run the host project with `dotnet run` from the samples folder.
+
 
 ## Building the Solution
 
@@ -24,7 +42,7 @@ This page contains the steps to build and run the Syncfusion Toolkit for Blazor
 
 ### Release sanity check (local)
 
-If you want to mimic what `.github/workflows/nuget-publish.yml` does on a release runner, pass `-p:ContinuousIntegrationBuild=true` so SourceLink and the package hash match what CI produces:
+To produce a local pack that matches CI **unsigned** pack properties (SourceLink / package metadata), pass `-p:ContinuousIntegrationBuild=true`:
 
 ```dotnetcli
 dotnet restore src/Syncfusion.Blazor.Toolkit.csproj -p:ContinuousIntegrationBuild=true
@@ -62,18 +80,20 @@ The threat model and security posture are reviewed on a structured schedule:
 
 | Trigger | Activity |
 |---|---|
-| Every **major release** (`x.0.0`) | Full review of [THREAT-MODEL.md](THREAT-MODEL.md): reassess all threats, verify mitigations, update or re-ratify the accepted-risks table. |
+| Every **major release** (`x.0.0`) | Full review of [THREAT-MODEL.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/THREAT-MODEL.md): reassess all threats, verify mitigations, update or re-ratify the accepted-risks table. |
 | Every **minor release** (`x.y.0`) | Review the accepted-risks table; escalate any entry whose circumstances have changed. |
-| **Monthly servicing** | Dependency review and CVE triage per [SECURITY.md §3.3](SECURITY.md). |
+| **Monthly servicing** | Dependency review and CVE triage per [SECURITY.md §3.3](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/SECURITY.md). |
 
-The outcome of each structured review is recorded by updating the "Security Self-Attestation" date in [SECURITY.md](SECURITY.md) and the accepted-risks table in [THREAT-MODEL.md](THREAT-MODEL.md).
+The outcome of each structured review is recorded by updating the "Security Self-Attestation" date in [SECURITY.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/SECURITY.md) and the accepted-risks table in [THREAT-MODEL.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/THREAT-MODEL.md).
 
 ## Versioning and API stability
 
 The project follows [Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html).
-Release history lives on the GitHub release page:
 
-> **Release history:** <https://github.com/syncfusion/blazor-toolkit/releases>
+Release history:
+
+- **GitHub Releases:** <https://github.com/syncfusion/blazor-toolkit/releases>
+- **In-repo changelog:** [CHANGELOG.md](https://github.com/syncfusion/blazor-toolkit/blob/main/CHANGELOG.md)
 
 Every published tag has a release page on that URL that enumerates
 the added, changed, deprecated, and removed APIs for that version.
@@ -88,10 +108,14 @@ The short version of the policy is:
 - **Minor (`x.y.0`)** — backwards-compatible additions only.
 - **Patch (`x.y.z`)** — backwards-compatible bug fixes only.
 
-Until the project ships a `1.0.0` release, the minor digit may
-include breaking changes per SemVer §4. The current source declares
-`2.0.1` in `src/Syncfusion.Blazor.Toolkit.csproj`; the most recent
-published release on the GitHub releases page is `v1.0.2`.
+The package version is declared in `src/Syncfusion.Blazor.Toolkit.csproj`
+(currently `2.0.1`). The latest published GitHub release is `v2.0.1`.
+
+The pre-1.0 SemVer exception no longer applies. On **2.x**, breaking changes
+require a new major version. **2.0.0** was a breaking re-baseline; see
+[CHANGELOG.md](https://github.com/syncfusion/blazor-toolkit/blob/main/CHANGELOG.md),
+[docs/API-COMPATIBILITY.md](https://github.com/syncfusion/blazor-toolkit/blob/main/docs/API-COMPATIBILITY.md), and
+[docs/API-BREAK-INVENTORY.md](https://github.com/syncfusion/blazor-toolkit/blob/main/docs/API-BREAK-INVENTORY.md).
 
 APIs marked `[Obsolete]` are retained for at least **two minor
 releases** before removal. APIs marked `[Experimental]` are not
@@ -213,16 +237,29 @@ bUnit test enforces this by reflection over every public `[Parameter]`
 in `src/Components/` and asserts `EditorRequiredAttribute` presence
 when the docs mark the parameter as required.
 
-### D5 / BEQ-20 — `e-*` style contract
+### D5 / BEQ-20 — Style and theme delivery (2.0)
+
+As of **2.0.0**, toolkit styling is delivered in two layers:
+
+1. **Component styles** — Colocated Blazor CSS isolation (`.razor.css` next to
+   each component). Edit component appearance in those source files. The build
+   produces the scoped CSS bundle.
+
+2. **Shared theme layer** — `:root` tokens, base/utility styles, icon font,
+   keyframes, and dark / high-contrast / forced-colors rules are emitted at
+   render time by **`SfThemeRoot`** (`src/Base/SfThemeRoot.cs`,
+   `SfThemeRoot.Payload.cs`), with ownership coordinated by **`SfThemeScope`**.
+   Root toolkit components render `<SfThemeRoot />` as the previous sibling of
+   their root element. For the common case, consumers do **not** need separate
+   toolkit theme `<link>` tags.
+
+Class names may still use the `e-*` prefix where applicable. Prefer matching
+existing isolated selectors and the theme payload rather than a permanent
+checked-in `src/wwwroot/styles/` tree. `src/wwwroot/` primarily holds
+JavaScript interop scripts.
 
-Global styles for the toolkit are namespaced under `e-*`. They are
-shipped from `src/wwwroot/styles/` and consumed via the
-`_content/Syncfusion.Blazor.Toolkit/styles` static asset path. The
-contract, including stable selectors and renaming policy, is defined
-in [`src/wwwroot/styles/STYLE-CONTRACT.md`](../src/wwwroot/styles/STYLE-CONTRACT.md).
-A subset of components uses Blazor CSS isolation for self-contained
-styling (`Border.razor.css` under `Spinner`, `SfNumericTextBox.razor.css`);
-those files are colocated with the component.
+See [CHANGELOG.md](https://github.com/syncfusion/blazor-toolkit/blob/main/CHANGELOG.md) section `[2.0.0]` (theme delivery model and
+CSS isolation) for migration details.
 
 ### D6 / PI-06 — SBOM (manual)
 
@@ -410,7 +447,7 @@ that are documented as static or server-only. The render mode is
 declared per sample, not per component. The render-mode contract for
 each component is documented in its XML doc-comment `Remarks`
 section. Security implications are summarised in
-[RENDER-MODE-SECURITY.md](RENDER-MODE-SECURITY.md).
+[RENDER-MODE-SECURITY.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/RENDER-MODE-SECURITY.md).
 
 ### Performance notes
 
@@ -448,7 +485,7 @@ This means:
 .NET matrix (8.0.x, 9.0.x, 10.0.x). Playwright validation runs on the
 same triple. The unpacked WebAssembly sample smoke runs on .NET 10
 only. Documented coverage and gaps are kept up to date in
-[TEST-MATRIX.md](TEST-MATRIX.md).
+[TEST-MATRIX.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/TEST-MATRIX.md).
 
 ### Known analyzer / trim / AOT findings
 

diff --git a/.github/Index.md b/.github/Index.md
@@ -8,84 +8,130 @@ The documents referenced below contain project information related to licensing,
 
 ## Licensing and Dependencies
 
-- [THIRD-PARTY-NOTICES.md](./THIRD-PARTY-NOTICES.md)
+- [THIRD-PARTY-NOTICES.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/THIRD-PARTY-NOTICES.md)
   - Third-party dependency inventory and license information.
 
 ---
 
 ## Security Documentation
 
-- [SECURITY.md](./SECURITY.md)
+- [SECURITY.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/SECURITY.md)
   - Security reporting process and vulnerability management.
 
-- [THREAT-MODEL.md](./THREAT-MODEL.md)
+- [THREAT-MODEL.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/THREAT-MODEL.md)
   - Security threats, mitigations, and accepted risks.
 
-- [RENDER-MODE-SECURITY.md](./RENDER-MODE-SECURITY.md)
+- [RENDER-MODE-SECURITY.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/RENDER-MODE-SECURITY.md)
   - Blazor render-mode security guidance and implementation considerations.
 
 ---
 
 ## Accessibility Documentation
 
-- [ACCESSIBILITY.md](./ACCESSIBILITY.md)
+- [ACCESSIBILITY.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/ACCESSIBILITY.md)
   - Accessibility commitments and compliance guidance.
 
-- [accessibility/insights-summary.md](./accessibility/insights-summary.md)
+- [accessibility/insights-summary.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/accessibility/insights-summary.md)
   - Accessibility Insights assessment summary.
 
-- [accessibility/screen-reader-smoke.md](./accessibility/screen-reader-smoke.md)
+- [accessibility/screen-reader-smoke.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/accessibility/screen-reader-smoke.md)
   - Screen-reader validation and testing results.
 
 ---
 
 ## Development and Release Guidance
 
-- [DEVELOPMENT.md](./DEVELOPMENT.md)
+- [DEVELOPMENT.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/DEVELOPMENT.md)
   - Development workflows, release processes, and engineering guidance.
 
 ---
 
+## Getting started and changelog
+
+- [README.md](https://github.com/syncfusion/blazor-toolkit/blob/main/README.md) — Product overview and getting started.
+- [CHANGELOG.md](https://github.com/syncfusion/blazor-toolkit/blob/main/CHANGELOG.md) — In-repo release history.
+- [ROADMAP.md](https://github.com/syncfusion/blazor-toolkit/blob/main/ROADMAP.md) — Chart-first priorities, exploratory component direction, and evidence gaps. Not a delivery commitment.
+
+---
+
+## API and compliance (`docs/`)
+
+- [API-COMPATIBILITY.md](https://github.com/syncfusion/blazor-toolkit/blob/main/docs/API-COMPATIBILITY.md) — 2.0 compatibility contract (upgraders from 1.0.2).
+- [API-BREAK-INVENTORY.md](https://github.com/syncfusion/blazor-toolkit/blob/main/docs/API-BREAK-INVENTORY.md) — Inventory of accepted 2.0 API breaks.
+- [VPAT-2.5-INT.md](https://github.com/syncfusion/blazor-toolkit/blob/main/docs/VPAT-2.5-INT.md) — Formal VPAT 2.5 report.
+
+---
+
 ## Performance Documentation
 
-- [evidences/performance/virtualization-strategy.md](./evidences/performance/virtualization-strategy.md)
+- [evidences/performance/virtualization-strategy.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/evidences/performance/virtualization-strategy.md)
   - Virtualization approach and rationale.
 
-- [evidences/performance/render-tree-efficiency.md](./evidences/performance/render-tree-efficiency.md)
+- [evidences/performance/render-tree-efficiency.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/evidences/performance/render-tree-efficiency.md)
   - Rendering performance analysis.
 
-- [evidences/performance/shouldRender-optimization.md](./evidences/performance/shouldRender-optimization.md)
+- [evidences/performance/shouldRender-optimization.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/evidences/performance/shouldRender-optimization.md)
   - Component rendering optimization guidance.
 
-- [evidences/performance/key-usage.md](./evidences/performance/key-usage.md)
+- [evidences/performance/key-usage.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/evidences/performance/key-usage.md)
   - Usage of @key and component lifecycle optimizations.
 
 ---
 
 ## Software Bill of Materials (SBOM)
 
-- [artifacts/sbom/](../artifacts/sbom/README.md)
+- [artifacts/sbom/](https://github.com/syncfusion/blazor-toolkit/blob/main/artifacts/sbom/README.md)
   - Generated SBOM artifacts and related package metadata.
 
 ---
 
 ## Support and Lifecycle
 
-- [SUPPORT.md](./SUPPORT.md)
+- [SUPPORT.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/SUPPORT.md)
   - Support process, service expectations, and lifecycle commitments.
 
 ---
 
-## Samples and Documentation
+## Samples and external links
 
-- [samples/](../samples/)
-  - Component samples and usage examples.
+- [samples/](https://github.com/syncfusion/blazor-toolkit/blob/main/samples/)
+  - In-repo sample browser (host and client projects).
 
-- https://blazor.syncfusion.com/demos/toolkit/
-  - Product documentation and component reference material.
+- **Demos:** https://blazor.syncfusion.com/demos/toolkit/
+  - Interactive toolkit demos.
+
+- **Documentation:** https://blazor.syncfusion.com/documentation/toolkit/overview
+  - Product documentation and component reference.
 
 ---
 
+## Getting started and changelog
+
+- [README.md](https://github.com/syncfusion/blazor-toolkit/blob/main/README.md)
+  - Product overview, repository structure, and consumer getting started.
+- [CHANGELOG.md](https://github.com/syncfusion/blazor-toolkit/blob/main/CHANGELOG.md)
+  - In-repo release history and migration notes.
+- [ROADMAP.md](https://github.com/syncfusion/blazor-toolkit/blob/main/ROADMAP.md)
+  - Chart-first priorities and exploratory direction. Not a delivery commitment.
+
+## API and compliance (`docs/`)
+
+- [API-COMPATIBILITY.md](https://github.com/syncfusion/blazor-toolkit/blob/main/docs/API-COMPATIBILITY.md)
+  - 2.0 compatibility and migration contract.
+- [API-BREAK-INVENTORY.md](https://github.com/syncfusion/blazor-toolkit/blob/main/docs/API-BREAK-INVENTORY.md)
+  - Inventory of accepted 2.0 API breaks.
+- [VPAT-2.5-INT.md](https://github.com/syncfusion/blazor-toolkit/blob/main/docs/VPAT-2.5-INT.md)
+  - Accessibility VPAT.
+
+## Contributing and tests
+
+- [CONTRIBUTING.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/CONTRIBUTING.md)
+  - Contribution process and PR expectations.
+- [TEST-MATRIX.md](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/TEST-MATRIX.md)
+  - Test coverage matrix and gaps.
+- [skills/](https://github.com/syncfusion/blazor-toolkit/blob/main/.github/skills/)
+  - Component skill guidance (`SKILL.md` per area).
+
 ## Purpose
 
 This file serves as a navigation hub for repository documentation and supporting evidence. Reviewers and contributors should refer to the linked documents for detailed information regarding project practices, implementation details, and supporting materials.