Update contributing.md

Author: Kyaa-dost

contributing.md

@@ -28,18 +28,9 @@ Once you fork the Windows Community Toolkit repo, it is essential to create all
 :warning: **We will not merge the PR to the main repo if your changes are not in the feature branch of your forked repository** :warning:
 
 
-## <a name="submit-pr"></a>Submit Pull Request :rocket:
-Before submitting Pull Request, you must:
+## <a name="submit-pr"></a>Submit or Review Pull Request :rocket:
 
-*	Test your code with the [supported SDKs](https://github.com/windows-toolkit/WindowsCommunityToolkit/blob/master/readme.md#supported)
-*	Follow the [quality guidance](#xaml), [coding style and conventions](#conventions), and [naming convention](#naming)
-*	Target master branch (or an appropriate release branch if appropriate for a bug fix)
-*	Follow the Windows Community Toolkit [PR Template](https://github.com/windows-toolkit/WindowsCommunityToolkit/blob/master/.github/PULL_REQUEST_TEMPLATE.md) 
-*	If adding a new feature
-o	Before starting coding, you should open an [issue](https://github.com/windows-toolkit/WindowsCommunityToolkit/issues/new?assignees=&labels=feature+request+%3Amailbox_with_mail%3A&template=feature_request.md&title=%5BFeature%5D) and start discussing with the community to see if your idea/feature is interesting enough.
-o	Add or update a sample for the [Sample app](https://github.com/windows-toolkit/WindowsCommunityToolkit/tree/master/Microsoft.Toolkit.Uwp.SampleApp)
-	If creating a new sample, create a new icon by following the [Thumbnail Style Guide and templates](https://github.com/Microsoft/UWPCommunityToolkit-design-assets)
-o	Add or update unit tests (if applicable)
+Please visit [Windows Community Toolkit Wiki](https://aka.ms/wct/wiki) for detailed information and steps it require to Submit or Review Pull Request. 
 
 
 ## <a name="pr"></a>Add New Feature :mailbox_with_mail:
@@ -48,106 +39,11 @@ o	Add or update unit tests (if applicable)
 *	If it gets approved by the team, proceed to submit a PR of the proposed Feature. 
 *	If the PR contains an error-free code and the reviewer signs off, the PR will be merged.
 
-## <a name="docs"></a> Add Documentation :page_with_curl:
-Documentation is **required** when adding, removing, or updating a control or an API. To update the documentation, you must submit a separate Pull Request in the [WindowsCommunityToolkitDocs](https://github.com/MicrosoftDocs/WindowsCommunityToolkitDocs) repository (use the master branch). **Both Pull Requests (code and docs) must be approved by the core team before either one is merged**.
+## <a name="docs"></a> Add or Improve Documentation :page_with_curl:
 
-Make sure to update both Pull Requests with a link to each other.
+Due to the multiple steps invovled to add or improve documents; it is required to visit [Windows Community Toolkit Wiki](https://aka.ms/wct/wiki) to follow contribution guidelines.
 
-If adding a new documentation page:
-
-*	Copy the [documentation template](https://github.com/MicrosoftDocs/WindowsCommunityToolkitDocs/blob/master/docs/.template.md) and follow the same format.
-
-*	Update the [Table of Contents](https://github.com/MicrosoftDocs/WindowsCommunityToolkitDocs/blob/master/docs/toc.md) to point to the new page
-
-## <a name="improve-docs"></a> Improve Documentation :page_with_curl:
-All the Windows Community Toolkit Docs are hosted on [WindowsCommunityToolkitDocs](https://github.com/MicrosoftDocs/WindowsCommunityToolkitDocs) repository. Therefore to open a Pull Request, start by forking this repository. Then, based on the type of change you're making you'll need to create a new branch from either the `master` or `live` branches:
-
-For documentation regarding introducing new features, please base your fork off the master branch.
-
-If you have a typo or existing document improvement to an already shipped feature, please base your change off of the [live branch](https://github.com/MicrosoftDocs/WindowsCommunityToolkitDocs/tree/live). This will allow us to get the change to the published documentation between releases.
-
-Once the PR is submitted and merged then depending on the improvement you are proposing the changes will eventually appear in these links.
-
-- [Staging review from 'master' branch](https://review.docs.microsoft.com/windows/communitytoolkit/?branch=master) **This link is currently only available for Microsoft Employees**
-- [Live site from 'live' branch](https://docs.microsoft.com/windows/communitytoolkit)
-
-## Review PR :book:
-
-Pre-requisites: Find the current list of PR’s [here](https://github.com/windows-toolkit/WindowsCommunityToolkit/pulls) (Make certain that PR has an appropriate branch. If there are multiple changes then make certain it is stated in the [PR Template](https://github.com/windows-toolkit/WindowsCommunityToolkit/blob/master/.github/PULL_REQUEST_TEMPLATE.md)), Download Visual Studio 2017 or 2019, Install [Windows Community Toolkit Sample App](http://aka.ms/uwptoolkitapp), [Install Git](https://github.com/github/hub#installation), [Install Hub](https://hub.github.com/#install)
-
-Steps to review PR
- 
-* Open Command Prompt or [Windows Terminal](https://www.microsoft.com/en-us/p/windows-terminal/9n0dx20hk701?activetab=pivot:overviewtab)
-* Locate the place where you want the WCT clone to appear by using the cd path. 
-* Go to [Windows Community Toolkit](https://github.com/windows-toolkit/WindowsCommunityToolkit) repository and click on **Code** button to copy the HTTPS or SSH URL.
-* Paste the link in Command Prompt by following the [Hub Command](https://hub.github.com/#developer) to Clone Windows Community Toolkit.
-* [Fork](https://hub.github.com/#contributor) the repo by following the command.
-* Checkout PR by using [hub pr checkout](https://hub.github.com/hub-pr.1.html#synopsis) Command
-* Open the Visual Studio 
-* Click on “Open a project or solution” 
-* Locate the cloned repository folder in the local machine and select the .sln file to open the solution.
-* You will see the PR checkout branch in the bottom right corner of the Visual Studio page. (By default it should have been on the master branch but since the PR checkout command has been performed; therefore, it’s on the branch that is ready to be tested).
-* Now run the Microsoft.Toolkit.Uwp.SampleApp and Open [Windows Community Toolkit Sample App](https://www.microsoft.com/en-us/p/windows-community-toolkit-sample-app/9nblggh4tlcq?rtc=1) as well. 
-* Review and test the changes side by side.
-* Once approved signoff by leaving feedback and results.
 
 
-## <a name="xaml"></a> Building XAML Controls :control_knobs:
-Follow these guidelines when submitting Pull Requests for controls:
-
-*	Your control must be usable and efficient with the keyboard only.
-*	Tab order must be logical.
-*	Focused controls must be visible.
-*	Action must be triggered when hitting the Enter key.
-*	Do not use custom colors but instead rely on theme colors so high contrasts themes can be used with your control.
-*	Add AutomationProperties.Name on all controls to define the control’s purpose (Name is minimum, but there are some other things too that can help the screen reader).
-*	Don't use the same Name on two different elements unless they have different control types.
-*	Use Narrator Dev mode (Launch Narrator [WinKey+Enter], then CTRL+F12) to test the screen reader experience. Is the information sufficient, meaningful and helps the user navigate and understand your control.
-*	Ensure that you have run your XAML file changes through Xaml Styler (version 2.3+), which can be downloaded from [here](https://visualstudiogallery.msdn.microsoft.com/3de2a3c6-def5-42c4-924d-cc13a29ff5b7). Do not worry about the settings for this as they are set at the project level (settings.xamlstyler).
-
-## <a name="conventions"></a> Coding Style and Conventions :balance_scale: 
-*	DO NOT require that users perform any extensive initialization before they can start programming basic scenarios.
-*	DO provide good defaults for all values associated with parameters, options, etc.
-*	DO ensure that APIs are intuitive and can be successfully used in basic scenarios without referring to the reference documentation.
-*	DO communicate incorrect usage of APIs as soon as possible.
-*	DO design an API by writing code samples for the main scenarios. Only then, you define the object model that supports those code samples.
-*	DO NOT use regions. DO use partial classes instead.
-*	DO declare static dependency properties at the top of their file.
-*	DO NOT seal controls.
-*	DO use extension methods over static methods where possible.
-*	DO NOT return true or false to give success status. Throw exceptions if there was a failure.
-*	DO use verbs like GET.
-*	DO NOT use verbs that are not already used like fetch.
-
-## <a name="accessibility"></a> Accessibility Guideline
-
-Basic accessibility features for each control. 
-
-### Color & High Contrast themes
-* Controls must support the 4 high contrast themes by default on Windows, in addition to changing the theme while the app is running.
-* Controls must have a contrast ratio of at least 4.5:1 between the text (and images with text) and the background behind it.
-### Keyboard
-* Controls must support keyboard navigation (tabs and arrow keys), the tab order must be the same as the UI and non-interactive elements mustn't be focusable. 
-* Composite elements must ensure proper inner navigation among the contained elements
-* Clickable UI elements must be invokable with the keyboard (The trigger keys are enter and space).
-* Focusable elements must have a visual focus indicator. It's usually a rectangle shape around the control's normal bounding rectangle.
-### Narrator
-* Controls must support the narrator.
-
-## <a name="naming"></a> Naming conventions
-* We are following the coding guidelines of [.NET Core Foundational libraries](https://github.com/dotnet/corefx/blob/master/Documentation/coding-guidelines/coding-style.md). 
-
-## <a name="documentation"></a> Documentation
-* DO NOT expect that your API is so well designed that it needs no documentation. No API is that intuitive.
-* DO provide great documentation with all APIs. 
-* DO use readable and self-documenting identifier names. 
-* DO use consistent naming and terminology.
-* DO provide strongly typed APIs.
-* DO use verbose identifier names.
-
-## <a name="files"></a> Files and folders
-* DO associate no more than one class per file.
-* DO use folders to group classes based on features.
-
-
-:rotating_light: **Please visit [Windows Community Toolkit Wiki](https://github.com/windows-toolkit/WindowsCommunityToolkit/wiki) to view complete and detail-oriented content of this page** :rotating_light:
+# Thank You :heart::heart:
+**Thank you so much for participating and contributing in this amazing project. We hope you continue to find yourself a strong asset to the Windows Community Toolkit and always find this platform highly reliable.**