Enable Smart Placement for Workers with Assets

src/content/docs/workers/configuration/smart-placement.mdx

@@ -31,6 +31,8 @@ Smart Placement only considers candidate locations where the Worker has previous
 
 Smart Placement only affects the execution of [fetch event handlers](/workers/runtime-apis/handlers/fetch/). Workers without a fetch event handler will be ignored by Smart Placement. For Workers with both fetch and non-fetch event handlers, Smart Placement will only affect the execution of the fetch event handler.
 
+Similarly, Smart Placement will not affect where [static assets](/workers/static-assets/) are served from. Static assets will continue to be served from the location nearest to the incoming request. If a Worker is invoked and your code retrieves assets via the [static assets binding](https://developers.cloudflare.com/workers/static-assets/binding/), then assets will be served from the location that your Worker runs in.
+
 ## Enable Smart Placement
 
 Smart Placement is available to users on all Workers plans.

src/content/docs/workers/static-assets/compatibility-matrix.mdx

@@ -42,15 +42,15 @@ We plan to bridge the gaps between Workers and Pages and provide ways to migrate
 | [Custom HTTP headers for static assets](/pages/configuration/headers/)              | 🟡 [^2] | ✅      |
 | [Middleware](/pages/functions/middleware/)                                          | 🟡 [^3] | ✅      |
 | [Redirects](/pages/configuration/redirects/)                                        | 🟡 [^4] | ✅      |
-| [Smart Placement](/workers/configuration/smart-placement/)                          | ⏳ [^5] | ✅      |
+| [Smart Placement](/workers/configuration/smart-placement/)                          | ✅      | ✅      |
 | **Observability**                                                                   |         |         |
 | [Workers Logs](/workers/observability/)                                             | ✅      | ❌      |
 | [Logpush](/workers/observability/logs/logpush/)                                     | ✅      | ❌      |
 | [Tail Workers](/workers/observability/logs/tail-workers/)                           | ✅      | ❌      |
 | [Real-time logs](/workers/observability/logs/real-time-logs/)                       | ✅      | ✅      |
 | **Runtime APIs & Compute Models**                                                   |         |         |
 | [Node.js Compatibility Mode](/workers/runtime-apis/nodejs/)                         | ✅      | ✅      |
-| [Durable Objects](/durable-objects/api/)                                            | ✅      | 🟡 [^6] |
+| [Durable Objects](/durable-objects/api/)                                            | ✅      | 🟡 [^5] |
 | [Cron Triggers](/workers/configuration/cron-triggers/)                              | ✅      | ❌      |
 | **Bindings**                                                                        |         |         |
 | [AI](/workers-ai/get-started/workers-wrangler/#2-connect-your-worker-to-workers-ai) | ✅      | ✅      |
@@ -78,8 +78,8 @@ We plan to bridge the gaps between Workers and Pages and provide ways to migrate
 | [Branch Deploy Controls](/pages/configuration/branch-build-controls/)               | ❌      | ✅      |
 | [Custom Branch Aliases](/pages/how-to/custom-branch-aliases/)                       | ❌      | ✅      |
 | **Pages Functions**                                                                 |         |         |
-| [File-based Routing](/pages/functions/routing/)                                     | ❌ [^7] | ✅      |
-| [Pages Plugins](/pages/functions/plugins/)                                          | ❌ [^8] | ✅      |
+| [File-based Routing](/pages/functions/routing/)                                     | ❌ [^6] | ✅      |
+| [Pages Plugins](/pages/functions/plugins/)                                          | ❌ [^7] | ✅      |
 
 [^1]: Does not currently support Workers with static assets. For more details on which bindings are supported in remote development, [refer to the docs](/workers/testing/local-development/#supported-resource-bindings-in-different-environments).
 
@@ -89,10 +89,8 @@ We plan to bridge the gaps between Workers and Pages and provide ways to migrate
 
 [^4]: You can handle redirects by adding code to your Worker (a [community package](https://npmjs.com/package/redirects-in-workers) is available for `_redirects` support), or you can use [Bulk Redirects](/rules/url-forwarding/bulk-redirects/).
 
-[^5]: You cannot yet enable [Smart Placement](/workers/configuration/smart-placement/) for Workers with static assets. This is a temporary limitation we are working to remove.
+[^5]: To [use Durable Objects with your Cloudflare Pages project](/pages/functions/bindings/#durable-objects), you must create a separate Worker with a Durable Object and then declare a binding to it in both your Production and Preview environments. Using Durable Objects with Workers is simpler and recommended.
 
-[^6]: To [use Durable Objects with your Cloudflare Pages project](/pages/functions/bindings/#durable-objects), you must create a separate Worker with a Durable Object and then declare a binding to it in both your Production and Preview environments. Using Durable Objects with Workers is simpler and recommended.
+[^6]: Workers [supports popular frameworks](/workers/frameworks/), many of which implement file-based routing.
 
-[^7]: Workers [supports popular frameworks](/workers/frameworks/), many of which implement file-based routing.
-
-[^8]: Everything that is possible with Pages Functions can also be achieved by adding code to your Worker or by using framework-specific plugins for relevant third party tools.
+[^7]: Everything that is possible with Pages Functions can also be achieved by adding code to your Worker or by using framework-specific plugins for relevant third party tools.