ICU-23425 Fix broken links in documentation site

Author: mihnita

docs/devsetup/cpp/vscode.md

@@ -37,5 +37,5 @@ parent: C++ Setup
 
 NOTE:
 Run the
-[`./runConfigureICU` command](https://unicode-org.github.io/icu/userguide/icufaq)
+[`./runConfigureICU` command](../../userguide/icu4c/faq.md)
 before building `icu4c` from VSCode.

docs/devsetup/source/index.md

@@ -102,7 +102,7 @@ There are many resources available to help you work with git, here are a few:
 *   <https://try.github.io/> - Resources to learn Git
 
 Want to contribute back to ICU? See
-[How to contribute](../../userguide/processes/contribute.md).
+[How to contribute](../../userguide/dev/index.md).
 
 ## Repository Layout
 
@@ -138,7 +138,7 @@ There are other tags and branches which may be cleaned up/deleted at any time.
 *   long running shared feature branches (In general, feature work is done on
     personal forks of the repository.)
 
-See also the [Tips (for developers)](repository/tips/index.md) subpage.
+See also the [git and Github for ICU Developers](../../userguide/dev/gitdev.md) subpage.
 
 ## A Bit of History
 

docs/download/76.md

@@ -255,7 +255,7 @@ We accept patches for other platforms.
 For ICU 76, we have received a contribution to make ICU4C work again on z/OS,
 using a newer (clang-based) compiler. ([ICU-22714](https://unicode-org.atlassian.net/browse/ICU-22714) [icu/pull/3008](https://github.com/unicode-org/icu/pull/3008) + [ICU-22916](https://unicode-org.atlassian.net/browse/ICU-22916) [icu/pull/3208](https://github.com/unicode-org/icu/pull/3208))
 
-Windows: The minimum supported version is Windows 7. (See [How To Build And Install On Windows](../userguide/icu4c/build.html#how-to-build-and-install-on-windows) for more details.)
+Windows: The minimum supported version is Windows 7. (See [How To Build And Install On Windows](../userguide/icu4c/build#how-to-build-and-install-on-windows) for more details.)
 
 ## ICU4J Platform Support
 

docs/download/77.md

@@ -129,7 +129,7 @@ We routinely test on recent versions of Linux, macOS, and Windows.
 
 We accept patches for other platforms.
 
-Windows: The minimum supported version is Windows 7. (See [How To Build And Install On Windows](../userguide/icu4c/build.html#how-to-build-and-install-on-windows) for more details.)
+Windows: The minimum supported version is Windows 7. (See [How To Build And Install On Windows](../userguide/icu4c/build#how-to-build-and-install-on-windows) for more details.)
 
 ## ICU4J Platform Support
 

docs/download/78.md

@@ -221,7 +221,7 @@ We routinely test on recent versions of Linux, macOS, and Windows.
 We accept patches for other platforms.
 
 Windows: The minimum supported version is Windows 7.
-(See [How To Build And Install On Windows](../userguide/icu4c/build.html#how-to-build-and-install-on-windows)
+(See [How To Build And Install On Windows](../userguide/icu4c/build#how-to-build-and-install-on-windows)
 for more details.)
 
 ## ICU4J Platform Support

docs/processes/cldr-icu.md

@@ -290,7 +290,7 @@ ant proddata 2>&1 | tee $NOTES/cldr-newData-proddataLog.txt
 
 > Note, for CLDR development, at this point tests are sometimes run on the
    production data, see
-   [BRS: Run tests on production data](https://cldr.unicode.org/development/cldr-big-red-switch/brs-run-tests-on-production-data)
+   [BRS: Run tests on production data](https://cldr.unicode.org/development/cldr-big-red-switch/)
 
 > Note, also for CLDR development, periodically at this point the CompareResolved
   tool should be run to compare the fully-resolved data generated from `$CLDR_DIR/common/main`

docs/processes/release/tasks/docs.md

@@ -70,7 +70,7 @@ See the [User Guide, ICU Architectural Design, ICU API
 compatibility](https://unicode-org.github.io/icu/userguide/icu/design#icu-api-compatibility).
 
 On ICU4J, run
-[com.ibm.icu.dev.tool.docs.CheckTags](https://github.com/unicode-org/icu/blob/main/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/CheckTags.java)
+[com.ibm.icu.dev.tool.docs.CheckTags](https://github.com/unicode-org/icu/blob/main/icu4j/tools/build/src/main/java/com/ibm/icu/dev/tool/docs/CheckTags.java)
 (see file for instructions). This requires a JDK with javadoc available, i.e, JDK11. The
 tool will need to change to reflect the release number to search for.
 
@@ -303,7 +303,7 @@ Instructions ***for ICU4C 4.8.x and earlier***:
 
 Run the ICU4J versus JDK API comparison tool against the target JDK (anything
 that will come out before our next release, basically) with the tool
-[com.ibm.icu.dev.tool.docs.ICUJDKCompare](https://github.com/unicode-org/icu/blob/main/icu4j/tools/build/src/com/ibm/icu/dev/tool/docs/ICUJDKCompare.java)
+[com.ibm.icu.dev.tool.docs.ICUJDKCompare](https://github.com/unicode-org/icu/blob/main/icu4j/tools/build/src/main/java/com/ibm/icu/dev/tool/docs/ICUJDKCompare.java)
 and make sure ICU4J adequately covers the JDK API for the classes we replicate.
 
 ---

docs/processes/release/tasks/integration.md

@@ -372,8 +372,7 @@ Instructions for verifying the XLIFF conversion tools.
 ## Test sample and demo programs
 
 Build and run all of the sample and demo apps that are included with ICU, on
-each of the reference platforms. A list of them is in the
-[readme](http://icu.sanjose.ibm.com/internal/checklist/icu-progs-list.html).
+each of the reference platforms. A list of them [here](../../../demos/index.md).
 Also see the build system.
 
 Another worthy test: Test suites and demos *from the previous release* should

docs/processes/release/tasks/legal/index.md

@@ -25,7 +25,7 @@ License & terms of use: http://www.unicode.org/copyright.html#License
 
 Scan the source code to make sure that every file that was touched recently has
 the current year in the copyright statement. See the [ICU Copyright
-Scanner](../../../copyright-scan.md) page and follow the link to the scripts and
+Scanner](https://icu.unicode.org/processes/copyright-scan) page and follow the link to the scripts and
 the readme.
 
 Scan the source code to include third-party company names in copyright notices

docs/processes/release/tasks/publish/index.md

@@ -339,7 +339,7 @@ That new flow overlaps with _"Using the output from the build bots"_ below.
 
 *   Manual process:
     *   Build with MSVC x64 Release. (See the ICU
-        [readme.html](https://github.com/unicode-org/icu/main/blob/icu4c/readme.html)
+        [readme.html](https://github.com/unicode-org/icu/blob/main/icu4c/readme.html)
         file for details).
     *   Open a command prompt.
         ```
@@ -522,8 +522,8 @@ Note that updating ICU4C demos online requires Gcloud access.
 
 ### Online information update
 
-Collation and [comparison](../../../../charts/comparison/index.md) charts need
-to be updated. See [charts/Performance & Size](../../../../charts/index.md).
+Collation and [comparison](https://icu.unicode.org/charts/comparison) charts need
+to be updated. See [charts/Performance & Size](https://icu.unicode.org/charts).
 
 ### Old sensitive tickets
 
@@ -581,9 +581,9 @@ Jira.
 ## Update readme
 
 Update [ICU4C
-readme.html](https://github.com/unicode-org/icu/main/icu4c/readme.html)
+readme.html](https://github.com/unicode-org/icu/blob/main/icu4c/readme.html)
 and [ICU4J
-readme.html](https://github.com/unicode-org/icu/main/icu4j/readme.html)
+readme.html](https://github.com/unicode-org/icu/blob/main/icu4j/readme.html)
 before every milestone (GA / RC / Milestone-N). Make sure the following items
 are up to date.