-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
42f5d45
commit f8247b7
Showing
1 changed file
with
9 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,10 @@ | ||
# Remote images | ||
|
||
Besides local images, provider functions allow using also remote images, i.e. images that are static parts of your local project. The most common use case is to load images from an [image CDN](https://web.dev/image-cdns/), that is then used to offload all image processing to the Cloud. This allows for _dynamic_ image processing, in cases where your images are not | ||
available at build-time. For example you could have an API endpoint refer to the raw (large, unprocessed) image, and use | ||
an image CDN as a proxy to scale, optimize and deliver that image as needed, at _runtime_. | ||
|
||
See the [image CDNs](../cdn/index.md) section for information on loading remote images from supported image CDNs. | ||
|
||
> [!TIP] | ||
> Besides the built-in support for selected image CDNs, you can also create your own custom integration by writing your own provider functions. The only requirement for the [image component](./component.md) is to receive an `ImageData` objects as its `src` argument. See the [Concepts page](./concepts.md#image-source) for more information. |