docs: Fix links resulting in 404

doc/articles/Uno-UI-Performance.md

@@ -152,7 +152,7 @@ Here's what to look for:
 
 ### Profiling applications
 
-A profiling guide for Uno Platform apps is [available here](ref:Uno.Tutorials.ProfilingApplications).
+A profiling guide for Uno Platform apps is [available here](xref:Uno.Tutorials.ProfilingApplications).
 
 ### FrameworkTemplatePool
 

doc/articles/common-issues-all-ides.md

@@ -21,7 +21,7 @@ Try building your project again.
 
 ## Runtime error `No parameterless constructor defined for XXXX`
 
-This error is generally caused by some missing [IL Linker](https://github.com/mono/linker/tree/master/docs) configuration on WebAssembly. You may need to add some of your application assemblies in the LinkerConfig.xml file of your project. You can find [additional information in the documentation](features/using-il-linker-webassembly.md).
+This error is generally caused by some missing [IL Linker](https://github.com/dotnet/runtime/tree/main/src/tools/illink) configuration on WebAssembly. You may need to add some of your application assemblies in the LinkerConfig.xml file of your project. You can find [additional information in the documentation](features/using-il-linker-webassembly.md).
 
 Similar error messages using various libraries:
 

doc/articles/concepts/overview/why-uno-platform.md

@@ -162,7 +162,7 @@ The Uno Platform provides access to SkiaSharp as a render canvas for your app, e
 
 ## Animations: Beyond storyboards, access to Lottie and Rive
 
-Based on SkiaSharp support, Uno Platform provides AnimatedVisualPlayer to give the ability to render rich Lottie files directly in your app, for all target platforms.
+Based on SkiaSharp support, Uno Platform provides AnimatedVisualPlayer to give the ability to render rich [Lottie files](https://airbnb.io/lottie/#/) directly in your app, for all target platforms.
 
 ## Performance and app size with AOT/Jiterpreter
 

doc/articles/contributing/guidelines/issue-triage.md

@@ -35,10 +35,10 @@ Is something unclear? Do we need to improve our documentation or samples?
 
 Community support requests should be directed to:
 
-* Our [documentation](https://platform.uno/docs/) and [troubleshooting guide](https://platform.uno/docs/troubleshooting-guide).
+* Our [documentation](https://platform.uno/docs/) and [troubleshooting guide](xref:Uno.UI.CommonIssues).
 * [GitHub Discussions](https://github.com/unoplatform/uno/discussions)
 * The [Discord Server](https://platform.uno/discord)
-* On [Twitter using the #unoplatform](https://twitter.com/search?q=%23unoplatform) hashtag.
+* On [X/Twitter using the #unoplatform](https://x.com/search?q=%23unoplatform) hashtag.
 
 Organizations that want a deeper level of support beyond community support should be directed to [contact Uno Platform](https://platform.uno/contact/) to discuss obtaining professional support.
 

doc/articles/contributing/guidelines/updating-dependencies.md

@@ -8,7 +8,7 @@ We use Dependabot to notify the team of any updates to dependencies. Once a week
 
 ## Internal dependencies
 
-The following dependencies don't change the public API surface and are typically safe to merge and we could potentially [configure mergify to automatically merge them if CI passes](https://medium.com/mergify/merging-bots-pull-requests-automatically-548ed0b4a424):
+The following dependencies don't change the public API surface and are typically safe to merge and we could potentially [configure mergify to automatically merge them if CI passes](https://docs.mergify.com/workflow/automerge/):
 
 - BenchmarkDotNet
 - [FluentAssertions](https://github.com/unoplatform/uno/pull/1196)

doc/articles/features/pointers-keyboard-and-other-user-inputs.md

@@ -28,7 +28,7 @@ User inputs are usually propagated using `RoutedEvents`. See Uno's [routed event
 | **_manipulation events_**
 | `ManipulationStarting`        | Yes     | Yes              | Yes     | Yes          | [Documentation](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.manipulationstarting) |
 | `ManipulationStarted`         | Yes     | Yes              | Yes     | Yes          | [Documentation](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.manipulationstarted) |
-| `ManipulationDelta`           | Yes     | Yes              | Yes     | Yes          | [Documentation](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.manipulationedelta) |
+| `ManipulationDelta`           | Yes     | Yes              | Yes     | Yes          | [Documentation](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.manipulationdelta) |
 | `ManipulationInertiaStarting` | Yes     | Yes              | Yes     | Yes          | [Documentation](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.manipulationinertiastarting) |
 | `ManipulationCompleted`       | Yes     | Yes              | Yes     | Yes          | [Documentation](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.manipulationcompleted) |
 | **_gesture events_**

doc/articles/features/using-linux-framebuffer.md

@@ -4,7 +4,7 @@ uid: Uno.Skia.Linux.Framebuffer
 
 # Using the Linux FrameBuffer and `libinput`
 
-Uno Platform supports the [Linux FrameBuffer](https://www.kernel.org/doc/html/latest/fb/framebuffer.html) and [libinput](https://github.com/wayland-project/libinput) as a target, in the case where your target device does not provide a Window Manager.
+Uno Platform supports the [Linux FrameBuffer](https://www.kernel.org/doc/html/latest/fb/framebuffer.html) and [libinput](https://wayland.freedesktop.org/libinput/doc/latest/what-is-libinput.html) as a target, in the case where your target device does not provide a Window Manager.
 
 There are some restrictions for the support for the FrameBuffer:
 

doc/articles/features/using-the-uno-sdk.md

@@ -67,7 +67,7 @@ Here are the supported features:
 | `Navigation`         | Adds support for [Navigation](xref:Uno.Extensions.Navigation.Overview) using [Uno.Extensions](xref:Uno.Extensions.Overview).                                                                                                               |
 | `LoggingSerilog`     | Adds support for [Serilog](https://github.com/serilog/serilog) using [Uno.Extensions](xref:Uno.Extensions.Overview).                                                                                                                       |
 | `Storage`            | Adds support for [Storage](xref:Uno.Extensions.Storage.Overview) using [Uno.Extensions](xref:Uno.Extensions.Overview).                                                                                                                     |
-| `Serialization`      | Adds support for [Serialization](Uno.Extensions.Serialization.Overview) using [Uno.Extensions](xref:Uno.Extensions.Overview).                                                                                                              |
+| `Serialization`      | Adds support for [Serialization](xref:Uno.Extensions.Serialization.Overview) using [Uno.Extensions](xref:Uno.Extensions.Overview).                                                                                                              |
 | `Toolkit`            | Adds support for the [Uno.Toolkit](xref:Toolkit.GettingStarted).                                                                                                                                                                           |
 | `Material`           | Adds support for the [Material Design Theme](xref:Uno.Themes.Material.GetStarted) library. If the `Toolkit` feature is also used, it will add support for the [Material Design Toolkit](xref:Toolkit.GettingStarted.Material) library.     |
 | `Cupertino`          | Adds support for the [Cupertino Design Theme](xref:Uno.Themes.Cupertino.GetStarted) library. If the `Toolkit` feature is also used, it will add support for the [Cupertino Design Toolkit](xref:Toolkit.GettingStarted.Cupertino) library. |

doc/articles/features/working-with-accessibility.md

@@ -65,7 +65,7 @@ Setting this property does the following:
 - On **Android**, it sets the [`View.ContentDescription`](https://developer.android.com/reference/android/view/View.html#setContentDescription(java.lang.CharSequence)) property
 - On **iOS**, it sets the [`UIView.AccessibilityIdentifier`](https://developer.apple.com/documentation/uikit/uiaccessibilityidentification/1623132-accessibilityidentifier) property
 - On **macOS**, it sets the [`NSView.AccessibilityIdentifier`](https://developer.apple.com/documentation/appkit/nsaccessibility/1535023-accessibilityidentifier) property
-- On **WebAssembly**, it sets [`aria-label`](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-label_attribute) and the `xamlautomationid` property on the HTML element. The [`role`](https://www.w3.org/WAI/PF/HTML/wiki/RoleAttribute) HTML Attribute is also set based on the XAML view type whose `AutomationProperties.AutomationId` was set.
+- On **WebAssembly**, it sets [`aria-label`](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-label) and the `xamlautomationid` property on the HTML element. The [`role`](https://www.w3.org/WAI/PF/HTML/wiki/RoleAttribute) HTML Attribute is also set based on the XAML view type whose `AutomationProperties.AutomationId` was set.
 
 This property is generally used alongside [Uno.UITest](https://github.com/unoplatform/Uno.UITest) to create UI Tests, and is particularly useful to select items using data-bound identifiers.
 

doc/articles/getting-started/wizard/includes/authentication.md

@@ -1,4 +1,4 @@
-Adds Uno Platform's [Custom Authentication](xref:Learn.Tutorials.Authentication.HowToAuthentication) support to the generated project.
+Adds Uno Platform's [Custom Authentication](xref:Uno.Extensions.Authentication.HowToAuthentication) support to the generated project.
 
 Using Uno's authentication tools you can easily integrate in your app a login screen and authenticate users. It also helps you manage and track the state of the app's authentication, by allowing you to log out or switch users as well as other authentication-related actions.
 
@@ -44,7 +44,7 @@ Uno.Extensions.Authentication currently supports these types of authentication:
     dotnet new unoapp -auth web
     ```
 
-Read the [Authentication documentation](xref:Overview.Authentication) to get more knowledge about Uno Platform's authentication support and the tools it provides.
+Read the [Authentication documentation](xref:Uno.Extensions.Authentication.Overview) to get more knowledge about Uno Platform's authentication support and the tools it provides.
 
 > [!NOTE]
 > The Authentication option is selected by default in the Default template, and not in the Blank one.

doc/articles/getting-started/wizard/includes/extensions.md

@@ -9,7 +9,7 @@ The available extensions are:
 
 Dependency Injection (DI) is an Inversion of Control (IoC) technique that enables consuming classes not to worry about the management or creation of their dependencies and instead rely on a central service to provide it when needed, based on how the provider was configured.  
 
-Uno Platform brings the power of [Microsoft Extensions Dependency Injection](https://learn.microsoft.com/dotnet/core/extensions/dependency-injection) to all OSs Uno Platform targets and adds its additional functionality via its Uno.Extensions.DependencyInjection library, which you can learn more about [here](xref:Overview.DependencyInjection).  
+Uno Platform brings the power of [Microsoft Extensions Dependency Injection](https://learn.microsoft.com/dotnet/core/extensions/dependency-injection) to all operating systems it targets and enhances it with additional functionality through its Uno.Extensions.DependencyInjection library. You can learn more about it in the [Uno.Extensions.DependencyInjection overview](xref:Uno.Extensions.DependencyInjection.Overview).
 
 This is included by default in the recommended preset, but not in the blank preset.
 
@@ -24,7 +24,7 @@ dotnet new unoapp -di
 
 This extension provides a way to load application configuration data from and to various sources using the [Options Pattern](https://learn.microsoft.com/dotnet/core/extensions/options). This is included by default in the recommended preset, but not in the blank preset.
 
-Refer to the [Uno Configuration](xref:Overview.Configuration) documentation for more information.
+Refer to the [Uno Configuration](xref:Uno.Extensions.Configuration.Overview) documentation for more information.
 
 ```dotnetcli
 dotnet new unoapp -config
@@ -34,9 +34,9 @@ dotnet new unoapp -config
 
 Uno.Extensions.Http allows for the registration of API endpoints as multiple typed HttpClient instances. In this centralized location for accessing web resources, the lifecycle of the corresponding HttpMessageHandler objects is managed. Added clients can optionally be configured to use the platform-native handler. Additional functionality is provided to clear cookies or log diagnostic messages in responses. This library uses Microsoft.Extensions.Http for any HTTP-related work. This is included by default in the recommended preset, but not in the blank preset.
 
-For more documentation on HTTP requests, [read the documentation](xref:Overview.Http).
+For more documentation on HTTP requests, [read the documentation](xref:Uno.Extensions.Http.Overview).
 
-Refer to the [documentation](xref:Overview.Http#refit) to learn how to use it in an Uno Platform app.
+Refer to the [documentation](xref:Uno.Extensions.Http.Overview#Refit) to learn how to use it in an Uno Platform app.
 
 ```dotnetcli
 dotnet new unoapp -http
@@ -47,9 +47,9 @@ dotnet new unoapp -http
 The Localization extension is responsible for managing globalization in your app.  
 This enables keeping all translations of your app in a single place and enables the user to easily switch the UI language.
 
-The generated app contains *resw* files which can be used to define the application strings. The defined languages are configured in *appsettings.json*. Follow [this link](Learn.Tutorials.Localization.HowToUseLocalization#3-update-the-ui-culture-with-localizationsettings) to learn how to switch the UI culture.
+The generated app contains *resw* files, which are used to define the application strings. The supported languages are configured in *appsettings.json*. To learn how to switch the UI culture, refer to the [localization tutorial](xref:Uno.Extensions.Localization.HowToUseLocalization#4-update-the-ui-culture-with-localizationsettings).
 
-![Visual Studio Solution Explorer showing localization files](assets/localization.jpg)
+![Visual Studio Solution Explorer showing localization files](../assets/localization.jpg)
 
 The default settings come with the following pre-set languages: English (*en*), Spanish (*es*), French (*fr*), and Portuguese - Brazil (*pt-BR*).
 

doc/articles/guides/silverlight-migration/09-client-auth-service.md

@@ -25,7 +25,7 @@ As discussed earlier, the UWP implementation of the **TimeEntryUno** application
 > [!TIP]
 > The IdentityServer4 server-side implementation used in the sample mirrors the QuickStart tutorial shown below. :
 >
-> * [Protecting an API using Client Credentials](http://docs.identityserver.io/en/latest/quickstarts/1_client_credentials.html)
+> * [Protecting an API using Client Credentials](https://docs.duendesoftware.com/identityserver/v7/quickstarts/1_client_credentials/)
 
 The code to retrieve the access token is encapsulated within the a class **IdentityServerClient** and uses the **HttpClient** class as well as the **IdentityModel** NuGet package.
 

doc/articles/guides/silverlight-migration/98-timeentry-samples.md

@@ -10,7 +10,7 @@ The sample application is made up of 3 solutions containing multiple projects an
 
 * Uno.Samples
   * reference
-    * [TimeEntryRia](https://github.com/unoplatform/Uno.Samples/tree/master/reference/TimeEntryRia)
+    * [TimeEntryRia](https://github.com/unoplatform/Uno.Samples/tree/master/ArchivedProjects/UI/TimeEntryRia/TimeEntryRia)
   * UI
     * TimeEntry
       * [TimeEntryServices](https://github.com/unoplatform/Uno.Samples/tree/master/UI/TimeEntry/TimeEntryServices)

doc/articles/migrating-from-xamarin-to-net6.md

@@ -16,8 +16,8 @@ There are two ways to migrate an application to .NET 7.
 
    1. In a separate folder, create a new application from the templates using [`dotnet new unoapp -o MyApp`](get-started-dotnet-new.md) (MyApp being of the same name as your existing app), or by using the Visual Studio `Uno Platform App` template
    2. Move the `MyApp.Mobile` project folder and include it in your existing solution
-   3. Make the adjustments to move from the [UWP APIs to the WinUI APIs](updating-to-winui3.ms)
-   4. Optionally [convert your legacy Xamarin heads](updating-to-winui3.md) to use Uno.WinUI instead of Uno.UI
+   3. Make the adjustments to move from the [UWP APIs to the WinUI APIs](xref:Uno.Development.UpdatingToWinUI3)
+   4. Optionally [convert your legacy Xamarin heads](xref:Uno.Development.UpdatingToWinUI3) to use Uno.WinUI instead of Uno.UI
 
 ## Additional considerations
 

doc/articles/uno-community-toolkit-v7.md

@@ -53,7 +53,7 @@ These package ids are for Uno Platform (non-Windows) projects. For WinUI 3 proje
 - [Uno.Microsoft.Toolkit.UWP](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.UWP)
 - [Uno.Microsoft.Toolkit.Uwp.Notifications](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.Notifications)
 - [Uno.Microsoft.Toolkit.Uwp.Services](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.Services)
-- [Uno.Microsoft.Toolkit.Uwp.UI.Controls.DataGrid](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.UWP.UI.DataGrid)
+- [Uno.Microsoft.Toolkit.Uwp.UI.Controls.DataGrid](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.UI.Controls.DataGrid)
 - [Uno.Microsoft.Toolkit.Uwp.UI](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.UWP.UI)
 - [Uno.Microsoft.Toolkit.Uwp.UI.Animations](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.UI.Animations)
 - [Uno.Microsoft.Toolkit.Uwp.UI.Controls](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.UI.Controls)

doc/articles/uno-development/building-uno-ui.md

@@ -13,9 +13,9 @@ This article explains how to build Uno.UI locally, for instance, if you wish to
   - Select the **.NET Multi-Platform App UI development`** workload
   - Select the **.NET desktop development** workload
   - To build the UWP flavor of Uno, you'll need **UWP Development**, install all recent UWP SDKs, starting from 10.0.19041 (or above or equal to `TargetPlatformVersion` line [in this file](https://github.com/unoplatform/uno/blob/master/src/Uno.CrossTargetting.targets))
-- Install (**Tools** / **Android** / **Android SDK manager**) all Android SDKs starting from 7.1 (or the Android versions `TargetFrameworks` [list used here](https://github.com/unoplatform/uno/blob/master/src/Uno.UI.BindingHelper.Android/Uno.UI.BindingHelper.Android.csproj))
+- Install (**Tools** / **Android** / **Android SDK manager**) all Android SDKs starting from 7.1 (or the Android versions `TargetFrameworks` [list used here](https://github.com/unoplatform/uno/blob/master/src/Uno.UI.BindingHelper.Android/Uno.UI.BindingHelper.Android.netcoremobile.csproj))
 - Run [Uno.Check](https://github.com/unoplatform/uno.check) on your dev machine to setup .NET Android/iOS workloads
-- Install the version of the .NET SDK specified in [global.json](../../../global.json).
+- Install the version of the .NET SDK specified in [global.json](https://github.com/unoplatform/uno/blob/master/global.json).
 
 ## Recommended Windows hardware