Mounted assets docs

[WalshyDev]

Summary

Documents mounting assets on a given path and the behaviour of it.

Note: Waiting on Wrangler to go out

Screenshots (optional)

Documentation checklist

• The documentation style guide has been adhered to.
• If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
• Files which have changed name or location have been allocated redirects.

[cloudflare-workers-and-pages]

Deploying cloudflare-docs with    Cloudflare Pages

Latest commit:	b88b6e0
Status:	✅  Deploy successful!
Preview URL:	https://7da55866.cloudflare-docs-7ou.pages.dev
Branch Preview URL:	https://walshy-mounted-assets.cloudflare-docs-7ou.pages.dev

View logs

[github-actions]

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/workers/static-assets/routing/	https://walshy-mounted-assets.cloudflare-docs-7ou.pages.dev/workers/static-assets/routing/
https://developers.cloudflare.com/workers/static-assets/compatibility-matrix/	https://walshy-mounted-assets.cloudflare-docs-7ou.pages.dev/workers/static-assets/compatibility-matrix/

[irvinebroque]

interesting that this is something that also wasn't possible with Pages - right?

I can have a custom domain with a Pages project.

But I can't define a route to say — run the Pages project at /blog.

And so here, I can just run the Worker, and its assets at /blog — that was already possible.

But before — if I had /blog directory, and ran the Worker on the /blog route, to access /dist/blog/index.html I would have to go to example.com/blog/blog

And now just example.com/blog

Is that accurate before/after?

[irvinebroque]

Or did we just disallow mounting assets on a route before

[hyperlint-ai-deprecated]

1 files reviewed, 1 total issue(s) found.

[korinne]

Looks great, thanks so much!