Update CONTRIBUTING and Build Testing docs (#590)

Signed-off-by: David Hoyt <dhoyt@hoyt.net>

Author: dwtza

CONTRIBUTING.md

@@ -18,15 +18,27 @@ We require all participants to abide by our [Code of Conduct](CODE_OF_CONDUCT.md
 
 ## Get Connected
 
-The first thing to do, before anything else, is to talk to us! Whether you are reporting an issue, requesting or implementing a feature, or just asking a question, please don’t hesitate to reach out to project maintainers or the community as a whole. This is an important first step because your issue, feature, or question may have been solved or discussed already, and you will save yourself a lot of time by asking first.
+The first thing to do, before anything else, is to talk to us! Whether you are reporting an issue, requesting or implementing a feature, or just asking a question, please don’t hesitate to reach out to the project maintainers or the community. This is an important first step because your issue, feature, or question may have been solved or discussed already, and you will save yourself a lot of time by asking first.
 
-How do you talk to us? There are several ways to get in touch:
+**Before opening a Pull Request, please start a conversation with us.**  
+All Pull Requests should be tied to an existing Issue that discusses the problem or feature being addressed. This helps ensure the change aligns with project goals and prevents wasted effort on work that may already be in progress or out of scope.
 
-* [GitHub Issues](https://github.com/InternationalColorConsortium/iccDev/issues):
-GitHub **issues** are a great place to start a conversation! Issues aren’t
-restricted to bugs; we happily welcome feature requests and other suggestions
-submitted as issues. The only conversations we would direct away from issues are
-questions in the form of “How do I do X”. Those questions should be discussed on the ICC Members Mailing List.
+### How do you talk to us?
+
+* [GitHub Issues](https://github.com/InternationalColorConsortium/iccDev/issues)  
+  GitHub **issues** are the primary place for project discussion. Issues aren’t
+  restricted to bugs; we happily welcome feature requests and other suggestions
+  submitted as issues. Opening an issue is the expected first step before
+  submitting a Pull Request.
+
+* [GitHub Discussions](https://github.com/InternationalColorConsortium/iccDev/discussions)  
+  GitHub **Discussions** are the place for open-ended conversation and exploration.
+  Use Discussions to ask questions, float new ideas, firm up enhancement proposals,
+  or gather feedback before opening an Issue or Pull Request.
+
+  The only conversations we would direct away from GitHub are questions in the
+  form of “How do I do X with ICC profiles”. Those questions should be discussed on
+  the ICC Members Mailing List.
 
 ## Legal Requirements
 

docs/build.md

@@ -1,13 +1,6 @@
 # Building iccDEV
 
-## Quickstart installation: 
-
-| Method | Command |
-|--------|---------|
-| **Homebrew** | `brew install iccdev` |
-| **NPM** | `npm install iccdev` |
-| **Docker Pull** | `docker pull ghcr.io/internationalcolorconsortium/iccdev:latest` |
-| **Docker Run** | `docker run -it ghcr.io/internationalcolorconsortium/iccdev:latest` |
+iccDEV requires C++17 or higher to compile.
 
 ## Required libraries
 
@@ -17,13 +10,11 @@
 | **Windows**       | libpng, libjpeg-turbo, libtiff, libxml2, wxwidgets, nlohmann-json         |
 | **Linux (Ubuntu)** | libpng-dev, libjpeg-dev, libtiff-dev, libxml2-dev, wxwidgets*, nlohmann-json |
 
+## Ubuntu
+
 \* **Note:** On Ubuntu, `wxwidgets` is installed via distribution-specific development packages  
 (e.g. `libwxgtk3.2-dev`). Refer to the `apt install` command below for the exact package names.
 
-iccDEV requires C++17 or higher to compile.
-
-
-## Ubuntu
 
 ```
 export CXX=clang++
@@ -58,4 +49,23 @@ cmake --preset vs2022-x64 -B . -S Build/Cmake
 cmake --build . -- /m /maxcpucount
 ```
 
----
+### Reporting Build Issues
+
+Before submitting a PR for build failures:
+
+1. Test local environment:
+   - Build in a clean container/VM
+   - Open an Issue first
+   - Utilize Testing Scripts
+     - [Unix](https://github.com/InternationalColorConsortium/iccDEV/blob/research/contrib/HelperScripts/unix-issue-template.sh)
+       ```
+       /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/InternationalColorConsortium/iccDEV/refs/heads/research/contrib/HelperScripts/unix-pr-review.sh)"
+       ```
+     - [Windows](https://raw.githubusercontent.com/InternationalColorConsortium/iccDEV/refs/heads/research/contrib/HelperScripts/windows-pr-review.ps1)
+       ```
+       iex (iwr -Uri "https://raw.githubusercontent.com/InternationalColorConsortium/iccDEV/refs/heads/research/contrib/HelperScripts/windows-issue-template.ps1").Content
+       ```
+
+2. Open or Update an Issue with the script output.
+
+3. [CI](https://github.com/InternationalColorConsortium/iccDEV/actions/workflows/ci-latest-release.yml) provides the latest builds for macOS, Windows & Linux.

docs/install.md

@@ -0,0 +1,11 @@
+## Quickstart installation: 
+
+| Method | Command |
+|--------|---------|
+| **Homebrew** | `brew install iccdev` |
+| **NPM** | `npm install iccdev` |
+| **Docker Pull** | `docker pull ghcr.io/internationalcolorconsortium/iccdev:latest` |
+| **Docker Run** | `docker run -it ghcr.io/internationalcolorconsortium/iccdev:latest` |
+
+## Build Instructions
+Build instructions are available in [docs/build.md](docs/build.md).