Fix broken links caught by CI link validator

- Fix 4 remaining /images/transform-images/ references in fundamentals and use-cases
- Fix double trailing slash in serve-private-images// (2 instances)
- Remove /cloudflare-one/applications/ link that fails validation

Author: deannalam

src/content/docs/fundamentals/reference/cdn-cgi-endpoint.mdx

@@ -12,7 +12,7 @@ A few examples include (but are not limited to):
 
 * [Identify the Cloudflare data center serving your request](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#identify-the-cloudflare-data-center-serving-your-request), which is helpful for troubleshooting (`https://<YOUR_DOMAIN>/cdn-cgi/trace`).
 * [JavaScript detection](/bots/additional-configurations/javascript-detections/) used by Cloudflare bot products (`example.com/cdn-cgi/challenge-platform/`)
-* [Image transformations](/images/transform-images) in the new URLs you would use for images (`example.com/cdn-cgi/image/`)
+* [Image transformations](/images/optimization/transformations/overview/) in the new URLs you would use for images (`example.com/cdn-cgi/image/`)
 * [Email address obfuscation](/waf/tools/scrape-shield/email-address-obfuscation/) used to hide email addresses from malicious bots (`example.com/cdn-cgi/l/email-protection`)
 * [Web analytics](/web-analytics/get-started/#sites-proxied-through-cloudflare) for a website proxied through Cloudflare (`example.com/cdn-cgi/rum`). This endpoint returns a `204` HTTP status code.
 * [Speed Brain](/speed/optimization/content/speed-brain/) adds an HTTP header called `Speculation-Rules` to web page responses. This header contains a URL that hosts an opinionated Speculation-Rules configuration, which instructs the browser to initiate prefetch requests for anticipated future navigations.

src/content/docs/images/optimization/hosted-images/browser-ttl.mdx

@@ -51,6 +51,6 @@ When the Browser TTL is set to one day for images requested with this variant, t
 
 :::note
 
-[Private images](/images/optimization/hosted-images/serve-private-images//) do not respect default or custom TTL settings. The private images cache time is set according to the expiration time and can be as short as one hour.
+[Private images](/images/optimization/hosted-images/serve-private-images/) do not respect default or custom TTL settings. The private images cache time is set according to the expiration time and can be as short as one hour.
 
 :::

src/content/docs/images/optimization/hosted-images/serve-from-custom-domains.mdx

@@ -86,4 +86,4 @@ regex_replace(
 
 ## Limitations
 
-When using a custom domain, it is not possible to directly set up WAF rules that act on requests hitting the `/cdn-cgi/imagedelivery/` path. If you need to set up WAF rules, you can use a Cloudflare Worker to access your images and a Route using your domain to execute the worker. For an example worker, refer to [Serve private images using signed URL tokens](/images/optimization/hosted-images/serve-private-images//).
+When using a custom domain, it is not possible to directly set up WAF rules that act on requests hitting the `/cdn-cgi/imagedelivery/` path. If you need to set up WAF rules, you can use a Cloudflare Worker to access your images and a Route using your domain to execute the worker. For an example worker, refer to [Serve private images using signed URL tokens](/images/optimization/hosted-images/serve-private-images/).

src/content/docs/images/optimization/transformations/control-origin-access.mdx

@@ -113,7 +113,7 @@ export default {
 
 ## Authenticated origin
 
-Cloudflare image transformations cache resized images to aid performance. Images stored with restricted access are generally not recommended for resizing because sharing images customized for individual visitors is unsafe. However, in cases where the customer agrees to store such images in public cache, Cloudflare supports resizing images through Workers. At the moment, this is supported on authenticated AWS, Azure, Google Cloud, SecureAuth origins and origins behind [Cloudflare Access](/cloudflare-one/applications/).
+Cloudflare image transformations cache resized images to aid performance. Images stored with restricted access are generally not recommended for resizing because sharing images customized for individual visitors is unsafe. However, in cases where the customer agrees to store such images in public cache, Cloudflare supports resizing images through Workers. At the moment, this is supported on authenticated AWS, Azure, Google Cloud, SecureAuth origins and origins behind Cloudflare Access.
 
 ```js null {9}
 // generate signed headers (application specific)

src/content/docs/images/optimization/transformations/flows.mdx

@@ -0,0 +1,81 @@
+---
+pcx_content_type: reference
+title: Create transformation flows
+sidebar:
+  order: 4
+---
+import { Description, Render } from "~/components";
+
+<Description>
+	Flows are automated rules that apply image optimization without requiring URL changes or custom code.
+</Description>
+
+When optimizing remote images, you can create flows to define how Cloudflare should handle image requests on your zone.
+
+Each flow matches trigger conditions with a set of actions that Images automatically applies to each qualifying request.
+
+## Types of flows
+
+You can use pre-built flows to handle migrations from other image optimization services (like Fastly) create your own custom flows.
+
+A **provider flow** acts as a translation layer to map image URLs from another image optimization service to the Cloudflare equivalent. Currently, Cloudflare supports flows for Fastly Image Optimizer.
+
+When you set up a provider flow, you can continue serving images using another provider's URL structure and optimization parameters.
+
+**Custom flows** let you define conditions (such as file extension or URL path) and a set of optimization actions to automatically apply. This is well-suited for situations where you want to optimize your images broadly and consistently, such as:
+
+- Automatically converting all images to modern formats like AVIF or WebP across your entire site.
+- Resizing images based on device so that mobile users receive appropriately sized images quickly.
+- Enforcing a consistent size and fit behavior for all images in a particular directory, such as 100x100 images for images where the path contains `/thumbnail`.
+
+## How flows work
+
+Before setting up a flow, make sure that transformations are turned on for your zone. In the Cloudflare dashboard, go to **Images** > **Transformations**.
+
+When an image request is made on your zone, Cloudflare evaluates your configured flows in order. If the request matches a flow's condition, then it is routed through Cloudflare's image processing pipeline. If a request matches more than one flow, then only the first matching flow is applied.
+
+Flows are evaluated after standard HTTP redirect rules in your request lifecycle.
+
+## Setting up a provider flow
+
+Currently, Cloudflare supports flows to handle migrations from Fastly Image Optimizer. To add a provider flow:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. Go to **Images** > **Transformations** and select the zone where you want to enable the provider flow.
+3. Select the **Automation** tab, then select **Add provider flow**.
+4. Choose **Fastly** as the provider.
+5. Select **Save**.
+
+When you enable the provider flow for Fastly, Cloudflare automatically handles differences in parameter naming and behavior. For example:
+
+- Fastly's `brightness` parameter accepts a range from `-100` to `100`, while Cloudflare's `brightness` works as a multiplier. The value will be scaled accordingly to match the intended result.
+- Fastly's `orient` parameter maps to Cloudflare's `flip` and `rotate` parameters, which handle the same behavior separately.
+
+Your existing URLs will continue to work as-is, and end-users will see no change in the image URLs they receive.
+
+## Setting up a custom flow
+
+### 1. Create a new flow
+
+In the Cloudflare dashboard, go to [**Images** > **Transformations**](https://dash.cloudflare.com/?to=/:account/images/transformations) and select the zone where you want to enable your flow.
+
+Then, select the **Automation** tab, and select **Add custom flow**. This will open a side panel where you can configure your flow.
+
+![Custom flow configuration panel](~/assets/images/images/custom-flow.png)
+
+### 2. Configure the conditions
+
+A custom flow is triggered when an incoming request matches one or more of the following conditions:
+
+- **File extension** — Match requests for all image formats or only specific file extensions, such as `.jpg`, `.png`, or `.gif`.
+- **URL path** — Match requests where the URL path matches a pattern you define, such as `/images/*` or `/assets/thumbnails/*`.
+
+Define the conditions that will trigger this flow to occur. You can combine conditions so that a flow triggers only when all of them are met.
+
+### 3. Configure the actions
+
+Next, define the optimization operations that should be performed when the flow is triggered. Multiple actions can be applied within a single flow.
+
+### 4. Save your flow
+
+Select **Save** on the side panel to add your custom flow, then select **Save** on your list of flows to make your flow live.

src/content/docs/images/tutorials/migration/akamai.mdx

@@ -0,0 +1,47 @@
+---
+pcx_content_type: tutorial
+title: Optimize mobile viewing
+description: Lazy loading is an easy way to optimize the images on your webpages for mobile devices, with faster page load times and lower costs.
+sidebar:
+  order: 1
+reviewed: 2025-07-07
+---
+
+You can use lazy loading to optimize the images on your webpages for mobile viewing. This helps address common challenges of mobile viewing, like slow network connections or weak processing capabilities.
+
+Lazy loading has two main advantages:
+
+- **Faster page load times** — Images are loaded as the user scrolls down the page, instead of all at once when the page is opened.
+- **Lower costs for image delivery** — When using Cloudflare Images, you only pay to load images that the user actually sees. With lazy loading, images that are not scrolled into view do not count toward your billable Images requests.
+
+Lazy loading is natively supported on all major browsers, including Chrome, Safari, Firefox, Opera, and Edge.
+
+:::note
+If you use older methods, involving custom JavaScript or a JavaScript library, lazy loading may increase the initial load time of the page since the browser needs to download, parse, and execute JavaScript.
+:::
+
+## Modify your loading attribute
+
+Without modifying your loading attribute, most browsers will fetch all images on a page, prioritizing the images that are closest to the viewport by default. You can override this by modifying your `loading` attribute.
+
+There are two possible `loading` attributes for your `<img>` tags: `lazy` and `eager`.
+
+### Lazy loading
+
+Lazy loading is recommended for most images. With Lazy loading, resources like images are deferred until they reach a certain distance from the viewport. If an image does not reach the threshold, then it does not get loaded.
+
+Example of modifying the `loading` attribute of your `<img>` tags to be `"lazy"`:
+
+```html
+<img src="example.com/cdn-cgi/width=300/image.png" loading="lazy" />
+```
+
+### Eager loading
+
+If you have images that are in the viewport, eager loading, instead of lazy loading, is recommended. Eager loading loads the asset at the initial page load, regardless of its location on the page.
+
+Example of modifying the `loading` attribute of your `<img>` tags to be `"eager"`:
+
+```html
+<img src="example.com/cdn-cgi/width=300/image.png" loading="eager" />
+```

src/content/docs/images/tutorials/migration/fastly.mdx

@@ -0,0 +1,47 @@
+---
+pcx_content_type: tutorial
+title: Optimize mobile viewing
+description: Lazy loading is an easy way to optimize the images on your webpages for mobile devices, with faster page load times and lower costs.
+sidebar:
+  order: 1
+reviewed: 2025-07-07
+---
+
+You can use lazy loading to optimize the images on your webpages for mobile viewing. This helps address common challenges of mobile viewing, like slow network connections or weak processing capabilities.
+
+Lazy loading has two main advantages:
+
+- **Faster page load times** — Images are loaded as the user scrolls down the page, instead of all at once when the page is opened.
+- **Lower costs for image delivery** — When using Cloudflare Images, you only pay to load images that the user actually sees. With lazy loading, images that are not scrolled into view do not count toward your billable Images requests.
+
+Lazy loading is natively supported on all major browsers, including Chrome, Safari, Firefox, Opera, and Edge.
+
+:::note
+If you use older methods, involving custom JavaScript or a JavaScript library, lazy loading may increase the initial load time of the page since the browser needs to download, parse, and execute JavaScript.
+:::
+
+## Modify your loading attribute
+
+Without modifying your loading attribute, most browsers will fetch all images on a page, prioritizing the images that are closest to the viewport by default. You can override this by modifying your `loading` attribute.
+
+There are two possible `loading` attributes for your `<img>` tags: `lazy` and `eager`.
+
+### Lazy loading
+
+Lazy loading is recommended for most images. With Lazy loading, resources like images are deferred until they reach a certain distance from the viewport. If an image does not reach the threshold, then it does not get loaded.
+
+Example of modifying the `loading` attribute of your `<img>` tags to be `"lazy"`:
+
+```html
+<img src="example.com/cdn-cgi/width=300/image.png" loading="lazy" />
+```
+
+### Eager loading
+
+If you have images that are in the viewport, eager loading, instead of lazy loading, is recommended. Eager loading loads the asset at the initial page load, regardless of its location on the page.
+
+Example of modifying the `loading` attribute of your `<img>` tags to be `"eager"`:
+
+```html
+<img src="example.com/cdn-cgi/width=300/image.png" loading="eager" />
+```

src/content/docs/images/tutorials/migration/index.mdx

@@ -0,0 +1,12 @@
+---
+title: Tutorials
+pcx_content_type: navigation
+sidebar:
+  order: 10
+  group:
+    hideIndex: true
+---
+
+import { DirectoryListing } from "~/components";
+
+<DirectoryListing />

src/content/docs/use-cases/media-streaming/image-optimization.mdx

@@ -28,4 +28,4 @@ Automatic image compression without quality loss. [Learn more about Polish](/ima
 
 1. [Images get started](/images/get-started/)
 2. [Enable Polish](/images/polish/)
-3. [Transform images via URL](/images/transform-images/)
+3. [Transform images via URL](/images/optimization/transformations/overview/)

src/content/docs/use-cases/media-streaming/index.mdx

@@ -48,13 +48,13 @@ Handle media uploads from users at scale:
 ### Create a new application
 
 - A [Cloudflare account](https://dash.cloudflare.com/sign-up). Stream and R2 are account-level offerings. You do not need a domain added to Cloudflare to upload, encode, or store media.
-- For Image Transformations: enable the feature per domain from the [Transformations page](https://dash.cloudflare.com/?to=/:account/images/transformations) in the dashboard. Refer to [Image Transformations](/images/transform-images/).
+- For Image Transformations: enable the feature per domain from the [Transformations page](https://dash.cloudflare.com/?to=/:account/images/transformations) in the dashboard. Refer to [Image Transformations](/images/optimization/transformations/overview/).
 
 ### Use an existing application
 
 - A [Cloudflare account](https://dash.cloudflare.com/sign-up).
 - A domain [added to Cloudflare](/fundamentals/manage-domains/add-site/) with DNS records proxied through Cloudflare. This is required for CDN caching, image optimization (Polish), and cache rules.
-- For Image Transformations on an existing domain: enable the feature from the [Transformations page](https://dash.cloudflare.com/?to=/:account/images/transformations) in the dashboard. Refer to [Image Transformations](/images/transform-images/).
+- For Image Transformations on an existing domain: enable the feature from the [Transformations page](https://dash.cloudflare.com/?to=/:account/images/transformations) in the dashboard. Refer to [Image Transformations](/images/optimization/transformations/overview/).
 
 ---