website: Added editorconfig-setup page to configure .editorconfig support in common IDEs and other text editors. Added step to CONTRIBUTING.md to review that section before contributing.

Author: NightOwl888

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# Lucene.NET Contributor's Guide
+# Lucene.NET Contributor's Guide
 
 Have you found a bug or do you have an idea for a cool new enhancement? Contributing code is a great way to give something back to the open-source community. Before you dig right into the code there are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
 
@@ -7,6 +7,7 @@ Have you found a bug or do you have an idea for a cool new enhancement? Contribu
 - Read [Open Source Contribution Etiquette](http://tirania.org/blog/archive/2010/Dec-31.html) and [Don't "Push" Your Pull Requests](http://www.igvita.com/2011/12/19/dont-push-your-pull-requests/).
 - Make sure you have a [GitHub account](https://github.com/signup/free). NOTE: Although this is a mirror of our Git repository, pull requests are accepted through GitHub.
 - If you are thinking of adding a feature, we would appreciate you opening a discussion on our [developer mailing list](https://cwiki.apache.org/confluence/display/LUCENENET/Mailing+Lists) before you start writing. It could save both you and our team quite a bit of work if the code doesn't have to be rewritten to fit in with our overall objectives.
+- [Set Up .editorconfig support](https://lucenenet.apache.org/contributing/editorconfig-setup.html) in your editor to ensure common styles (such as whitespace handling) are respected.
 - Submit a [new issue on GitHub](https://github.com/apache/lucenenet/issues), assuming one doesn't exist already.
   - If reporting a bug, clearly describe the issue including steps to reproduce, observed behavior, and expected behavior.
   - If reporting a bug, provide source code that we can run without any alteration demonstrating the issue. Issues submitted with runnable code will be given a higher priority than those submitted without.

websites/site/contributing/editorconfig-setup.md

@@ -0,0 +1,48 @@
+---
+uid: contributing/editorconfig-setup
+---
+
+# EditorConfig Setup
+
+This project uses style rules setup in .editorconfig files. This allows us to manage style rules such as whitespace and indent style so they are consistent between different contributors and will create smaller diffs to review. To make pull requests go smoothly, it is important that each contributor ensure that these rules are respected. The best way is to use an editor that supports .editorconfig styles and to configure it to detect these files automatically.
+
+### 🧠 Visual Studio
+- Go to: **Tools > Options > Text Editor > [Language] > Code Style > General**
+- Enable: **"Detect EditorConfig settings"**
+- Optionally enable: **"Reformat on save"** (under Code Cleanup)
+
+### 🧰 JetBrains Rider
+- Go to: **Preferences > Editor > Code Style**
+- Enable: **"Enable EditorConfig support"**
+- Re-save the affected files to apply the formatting
+
+### 💡 Visual Studio Code
+- Install the **EditorConfig for VS Code** extension
+- In your `settings.json`, enable:
+  - `"files.insertFinalNewline": true`
+  - `"files.trimTrailingWhitespace": true`
+
+### 📝 Notepad++
+- Go to: **Settings > Preferences > MISC**
+  - Enable: **"Final line ending"**
+- Go to: **Settings > Preferences > Language > Tab Settings**
+  - Enable: **"Replace by space"** and configure indentation properly
+
+### 🔧 Other Common Editors for .NET
+- **JetBrains ReSharper** (for Visual Studio)
+- **OmniSharp**-based editors (NeoVim, Sublime Text, etc.)
+- **Vim** with [`editorconfig-vim`](https://github.com/editorconfig/editorconfig-vim)
+- **Emacs** with [`editorconfig-emacs`](https://github.com/editorconfig/editorconfig-emacs)
+
+### 🌍 Not Sure If Your Editor Supports It?
+Check these official lists:
+- Editors with built-in support: https://editorconfig.org/#pre-installed
+- Editors with plugin support: https://editorconfig.org/#download
+
+---
+
+✅ After configuring your editor, **open each file with errors, make a whitespace-only change, and save**. This will apply your formatting settings and fix the rule violations.
+
+## Pull Request Workflow
+
+We highly recommend using an editor that supports .editorconfig and configure it to respect the formatting rules. However, when submitting pull request, there is an EditorConfig Rules Check workflow that will compare the styles in the PR against the .editorconfig and report any violations. This uses the [editorconfig-checker tool](https://github.com/editorconfig-checker/editorconfig-checker), which reports the file path and line number of each violation. If any of these checks fail, it will allow contributors to fix any style violations prior to requesting a PR review even if the editor used doesn't support .editorconfig.

websites/site/contributing/toc.yml

@@ -1,4 +1,4 @@
-- name: Community Links
+- name: Community Links
   href: community-links.md
 - name: Mailing Lists
   href: mailing-lists.md
@@ -8,6 +8,8 @@
   href: issue-tracker.md
 - name: Website & Docs
   href: documentation.md
+- name: EditorConfig Setup
+  href: editorconfig-setup.md
 - name: Current status
   href: current-status.md
 - name: Making a release