Feature Title
Add DatoCMS image provider support
Description
Add a documented DatoCMS integration by reusing the existing Imgix provider. DatoCMS documents an Imgix-backed asset pipeline, so a separate transformation engine is unnecessary.
Use Case
A DatoCMS-backed application needs a clear supported configuration for its asset URLs and responsive image modifiers without discovering the underlying Imgix compatibility itself.
Proposed Solution
- If a named
datocms integration is added, export and register it in core for shared Angular, React, and Svelte configuration. Keep the implementation in its base provider.
- Verify the existing Imgix provider against documented DatoCMS delivery examples, including
datocms-assets.com URLs and existing asset metadata parameters.
- Provide a named
datocms alias or thin wrapper if it improves configuration discoverability; a documented Imgix configuration recipe is sufficient if no behavior differs.
- Preserve the source hostname and query metadata while applying modifiers. Document any DatoCMS-specific capability limits established during verification and keep serialization in the shared Imgix implementation.
- Add setup documentation and focused fixtures covering DatoCMS source URLs, existing metadata parameters, modifier overrides, and parity with the shared Imgix serializer. Validate advertised dimensions and content types against an enabled service or controlled server where applicable.
Alternatives Considered
Configure the existing imgix provider directly. That is the intended reuse path; this request adds verified examples and, if useful, a discoverable provider name.
Examples from Other Libraries
Feature Title
Add DatoCMS image provider support
Description
Add a documented DatoCMS integration by reusing the existing Imgix provider. DatoCMS documents an Imgix-backed asset pipeline, so a separate transformation engine is unnecessary.
Use Case
A DatoCMS-backed application needs a clear supported configuration for its asset URLs and responsive image modifiers without discovering the underlying Imgix compatibility itself.
Proposed Solution
datocmsintegration is added, export and register it in core for shared Angular, React, and Svelte configuration. Keep the implementation in its base provider.datocms-assets.comURLs and existing asset metadata parameters.datocmsalias or thin wrapper if it improves configuration discoverability; a documented Imgix configuration recipe is sufficient if no behavior differs.Alternatives Considered
Configure the existing imgix provider directly. That is the intended reuse path; this request adds verified examples and, if useful, a discoverable provider name.
Examples from Other Libraries