Include necessary files for public repo

CODE_OF_CONDUCT.md

@@ -0,0 +1,72 @@
+# Syncfusion Code of Conduct and Corporate Ethics Policy
+
+## 1. Purpose
+
+Syncfusion is committed to responsible corporate citizenship. Our commitment to integrity begins with following all local, state, and federal laws and regulations.
+
+Employment at Syncfusion is based exclusively on individual merit and qualifications. The company prohibits discrimination on the basis of race, color, religion, veteran status, national origin, ancestry, pregnancy status, sex, gender identity or expression, age, marital status, mental or physical disability, medical condition, sexual orientation, or any other characteristic protected by law.
+
+Syncfusion will not tolerate discrimination, harassment, or bullying in any form and will not retaliate against any employee who reports or participates in an investigation of such behavior.
+
+## 2. Standards
+
+Syncfusion complies with all laws relating to minimum wage and overtime payments. Employees must record their time accurately in accordance with the company’s established procedures.
+
+The company adheres to all laws prohibiting child labor, slave labor, and other illegal workplace practices.
+
+Syncfusion believes that acting ethically and responsibly is not just the right thing to do—it is also good for business and crucial for our continued success. We are dedicated to full compliance with all applicable laws and to maintaining high ethical standards in all business transactions.
+
+## 3. Commitment to Ethics
+
+Syncfusion is committed to protecting employees, customers, partners, vendors, and the company from illegal or damaging actions by individuals, knowingly or unknowingly. This policy establishes behavioral and ethical standards for Syncfusion’s employees, vendors, and the company.
+
+This policy also aligns with the community standards of open-source initiatives maintained by Syncfusion, including the Syncfusion Blazor Toolkit.
+
+### 3.1 Executive Commitment to Ethics
+
+Executives must:
+- Maintain an open-door policy and welcome suggestions or concerns.
+- Disclose any conflicts of interest regarding their position within Syncfusion.
+
+### 3.2 Employee Commitment to Ethics
+
+Syncfusion employees shall:
+- Treat everyone fairly and respectfully.
+- Promote a team environment and avoid unethical or compromising practices.
+- Abide by Syncfusion’s mission, values, and policies.
+- Avoid dishonesty, fraud, or misrepresentation.
+- Comply with all legal regulations and standards of equity.
+- Respect diversity and differences in people.
+- Refrain from profanity, abuse, or violence.
+- Maintain confidentiality during and after employment.
+- Respect and abide by management decisions.
+- Avoid public criticism that could harm Syncfusion’s reputation.
+
+### 3.3 Maintaining Ethical Practices
+
+Every employee must:
+- Support ethical behavior consistently.
+- Notify supervisors of any actual or potential conflicts of interest.
+- Avoid prohibited activities, including:
+  - Using their position for personal or family gain.
+  - Accepting or offering gifts or preferential treatment.
+  - Misusing Syncfusion’s assets or resources.
+
+### 3.4 Unethical Behavior
+
+Unethical or illegal practices are strictly prohibited, including:
+- Corruption, bribery, or misuse of proprietary information.
+- Unauthorized use of company assets or confidential relationships.
+- Abuse of employment benefits.
+
+All violations must be reported to: **legal@syncfusion.com**
+
+## 4. Open Source Contribution Ethics – Blazor Toolkit
+
+Syncfusion maintains high ethical and community standards for its open-source projects. Contributors and users of the Syncfusion Blazor Toolkit are expected to adhere to its [Code of Conduct](https://github.com/syncfusion/blazor-toolkit) harassment-free collaboration environment.
+
+Anyone participating in the open-source community representing Syncfusion should:
+- Follow the same integrity and professionalism expected of internal employees.
+- Avoid discriminatory or abusive behavior in any form.
+- Promote transparency and respect among all contributors, users, and maintainers.
+

CONTRIBUTING.md

@@ -0,0 +1,37 @@
+# Contributing
+
+Thank you for your interest in contributing to the Syncfusion Toolkit for Blazor! In this document, we'll outline what you need to know about contributing and how to get started.
+
+First and foremost: if you are thinking about contributing a bigger change or feature, **please open an issue or talk to a core team member first**! By doing this, we can coordinate and see if the change you are going to work on is something that aligns with our current priorities and is something we can commit to reviewing and merging within a reasonable time. We would want to prevent you from investing a lot of your valuable time in something that might not be in line with what we want for the toolkit.
+
+## Code of Conduct
+
+Please see our [Code of Conduct](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!
+
+Have a look at our [Development Guide](DEVELOPMENT.md) to learn about setting up your development environment.
+
+### What to Work On
+
+If you're looking for something to work on, please browse our [backlog](https://github.com/syncfusion/blazor-toolkit/issues?q=is%3Aopen+is%3Aissue+milestone%3ABacklog). Any issue that is not already assigned is up for grabs. 
+
+Please adhere to the coding standards outlined by the [.NET Foundation](https://github.com/dotnet/runtime/blob/master/docs/coding-guidelines/coding-style.md). Additionally, review and follow the guidelines specified in our [pull request template](PULL_REQUEST_TEMPLATE.md) when submitting changes.
+
+### Pull Request Requirements
+
+Please refer to our [pull request template](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.
+
+## Proposals/Enhancements/Suggestions
+
+To propose a change or new feature, open an issue using the [feature request template](https://github.com/syncfusion/blazor-toolkit/issues/new?assignees=&labels=proposal-open%2C+t%2Fenhancement+%E2%9E%95&template=feature_request.yml&title=%5BEnhancement%5D+YOUR+IDEA!). You may also use the [spec template](https://github.com/syncfusion/blazor-toolkit/issues/new?assignees=&labels=proposal-open%2C+t%2Fenhancement+%E2%9E%95&template=spec.md&title=[Spec]++) if you have an idea of what the API should look like. Be sure to also browse current issues that may be related.
+
+## Review Process
+All pull requests need to be reviewed and tested by at least two members of the Blazor Toolkit team. We do our best to review pull requests in a timely manner, but please be patient! Two reviewers will be assigned and will start the review process as soon as possible. If there are any changes requested, the contributor should make them at their earliest convenience or let the reviewers know that they are unable to make further contributions. If the pull request requires only minor changes, then someone else may pick it up and finish it. We will do our best to make sure that all credit is retained for contributors. 
+
+## Merge Process
+All PRs should target the main branch.

DEVELOPMENT.md

@@ -0,0 +1,45 @@
+# Development Guide
+
+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) or latest version .NET SDK.
+   - Clone the repository:
+     ```shell
+     git clone https://github.com/syncfusion/blazor-toolkit.git
+     cd blazor-toolkit
+     ```
+
+## Building the Solution
+
+1. Open a command prompt/terminal window.
+2. Navigate to the location of your cloned `syncfusion/blazor-toolkit` repo.
+3. Run these commands:
+    ```dotnetcli
+    dotnet restore
+    dotnet build ./Syncfusion.Blazor.Toolkit.slnx
+    ```
+
+## Running Samples
+
+- Open the `samples/Blazor.Toolkit.Samples.slnx` file in Visual Studio.
+- Set the desired sample project as the startup project and run.
+
+## What branch should I use?
+
+As a general rule:
+- [main](https://github.com/syncfusion/blazor-toolkit/tree/main)
+
+## Sample projects
+
+### Samples
+```
+├── samples
+│   ├── Blazor.Toolkit.Samples
+│   ├── Blazor.Toolkit.Samples.Client
+```
+
+- *Blazor.Toolkit.Samples*: Full gallery sample with all of the controls and features of the Syncfusion Blazor Toolkit.
+- *Blazor.Toolkit.Samples.Client*: Client-side Blazor WebAssembly sample project.

LICENSE.txt

@@ -0,0 +1,23 @@
+The MIT License (MIT)
+
+Copyright (c) 2025-2026 Syncfusion Inc.
+
+All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,23 @@
+### Root Cause of the Issue
+
+<!-- Enter the root cause of the issue in this section. -->
+
+### Description of Change
+
+<!-- Enter description of the fix in this section. -->
+
+### Issues Fixed
+
+<!-- Please make sure that there is a bug logged for the issue being fixed. The bug should describe the problem and how to reproduce it. -->
+
+Fixes #
+
+<!--
+Are you targeting main? All PRs should target the main branch unless otherwise noted.
+-->
+
+### Screenshots
+
+#### Before:
+
+#### After:

SECURITY.md

@@ -0,0 +1,33 @@
+# Security Policy
+
+## 1. Purpose
+
+We prioritize our project’s security and encourage the community to responsibly report any vulnerabilities.
+
+## 2. Reporting a Vulnerability
+
+We take the security of our Syncfusion .NET MAUI Toolkit project very seriously. If you discover a security vulnerability, please report it responsibly using the steps outlined below.
+
+### 2.1 How to Report
+
+#### 2.1.1 Contact us privately:
+- Please email us at **security@syncfusion.com** with a detailed report of the vulnerability.
+- Wait until we verify that the problem has been fixed before making the announcement in public.
+
+#### 2.1.2 Provide details:
+- Provide instructions on how to replicate the vulnerability.
+- Share any possible impact or exploitation scenarios.
+
+#### 2.1.3 Expect a response:
+- We will acknowledge receipt of your report within **2 business days**.
+- You will receive updates on the progress as we investigate and resolve the issue.
+
+## 3. Security Patch Process
+
+### 3.1 After a vulnerability is reported and verified:
+- We will assess its severity and impact.
+- A fix will be developed and tested internally.
+
+The resolution will be included in the next available release. If necessary, a security patch will be issued immediately.
+
+Affected users will be notified in the GitHub repository's **Releases** page and other relevant channels.