@imgly/codesign-mcp 0.1.0

package/assets/docs/guide/text.md

@@ -0,0 +1,33 @@
+> This is one page of the CE.SDK Vanilla JS/TS documentation. For a complete overview, see the [Vanilla JS/TS Documentation Index](https://img.ly/docs/cesdk/js.md). For all docs in one file, see [llms-full.txt](./llms-full.txt.md).
+
+**Navigation:** [Guides](./guides.md) > [Create and Edit Text](./text.md)
+
+---
+
+---
+
+## Related Pages
+
+- [Overview](./text/overview.md) - Add, style, and customize text layers in your design using CE.SDK’s flexible text editing tools.
+- [Add Text](./text/add.md) - Insert text blocks into your CE.SDK scene.
+- [Edit Text](./text/edit.md) - Edit text content directly on the canvas or through the properties panel.
+- [Text Styling](./text/styling.md) - Apply fonts, colors, alignment, and other styling options to customize text appearance.
+- [Text Decorations](./text/decorations.md) - Add underline, strikethrough, and overline decorations to text with customizable styles, colors, and thickness.
+- [Text Designs](./text/text-designs.md) - Create and customize text component libraries using predefined text designs that appear in your asset library.
+- [Text Enumerations](./text/enumerations.md) - Add bullet lists and numbered lists to text blocks in CE.SDK using per-paragraph list styles and nesting levels.
+- [Auto-Size](./text/auto-size.md) - Configure text blocks to automatically adapt their dimensions or font size for dynamic content.
+- [Text Effects](./text/effects.md) - Apply visual effects to text blocks including drop shadows and stroke outlines.
+- [Emojis](./text/emojis.md) - Insert and style emojis alongside text for expressive, modern typographic designs.
+- [Adjust Text Spacing](./text/adjust-spacing.md) - Control letter spacing, line height, and paragraph spacing in CE.SDK text blocks for precise typographic control.
+- [Customize Fonts](./text/custom-fonts.md) - Load and manage custom fonts to match brand guidelines or user preferences.
+- [Text and Language Support](./text/language-support.md) - Create designs that work seamlessly across different languages and writing systems with RTL text, complex scripts, and multilingual font support.
+- [Understanding Text Rendering](./guides/text/rendering-internals.md) - Learn how CE.SDK renders text internally by visualizing font metrics, baselines, ascenders, descenders, and line height.
+
+---
+
+## More Resources
+
+- **[Vanilla JS/TS Documentation Index](https://img.ly/docs/cesdk/js.md)** - Browse all Vanilla JS/TS documentation
+- **[Complete Documentation](./llms-full.txt.md)** - Full documentation in one file (for LLMs)
+- **[Web Documentation](./js.md)** - Interactive documentation with examples
+- **[Support](mailto:support@img.ly)** - Contact IMG.LY support

package/assets/docs/guide/to-v1-10.md

@@ -0,0 +1,131 @@
+> This is one page of the CE.SDK Vanilla JS/TS documentation. For a complete overview, see the [Vanilla JS/TS Documentation Index](https://img.ly/docs/cesdk/js.md). For all docs in one file, see [llms-full.txt](./llms-full.txt.md).
+
+**Navigation:** [Upgrading](./upgrade.md) > [To v1.10](./to-v1-10.md)
+
+---
+
+Version v1.10 introduced major changes to how and where engine and the UI store assets.
+This guide helps you navigate those changes and explains what you need to do to bring your integration up to speed.
+
+## 1. Scene Uploads are no longer serialized
+
+Image uploads are no longer stored in the scene and will not reappear upon scene load. To offer specific assets in your editor, configure and [add an asset source](./serve-assets.md) containing the desired assets.
+
+## 2. Deprecating Extensions
+
+Starting with `v1.10` we fully embrace [Asset Sources](./import-media/from-remote-source/unsplash.md) as our standard interface for asset management.
+We're deprecating extension packs, previously stored in `/assets/extensions` and indexed via `manifest.json` files.
+
+**Fonts are not affected by this deprecation yet, but will receive the same treatment in an upcoming version.**
+
+We'll deprecate the `config.extensions` field for `CreativeEditorSDK`.
+As part of this deprecation, we'll **no longer ship** the following packs in the `/assets/extensions` directory in our `npm` packages:
+
+- `ly.img.cesdk.images.samples`
+- `ly.img.cesdk.shapes.default`
+- `ly.img.cesdk.stickers.doodle`
+- `ly.img.cesdk.stickers.emoji`
+- `ly.img.cesdk.stickers.emoticons`
+- `ly.img.cesdk.stickers.hand`
+- `ly.img.cesdk.vectorpaths`
+- `ly.img.cesdk.vectorpaths.abstract`
+
+To keep offering the contained assets in your deployment, use our new [convenience functions](#making-use-of-default-and-demo-asset-sources) to instantiate asset sources holding these assets.
+If you have existing scenes where an asset from an extension pack might be included, you must make sure you're still serving the corresponding files from your baseURL, so that `<baseURL>/extensions/…` paths still resolve properly.
+You can acquire a copy of the extension packs shipped in `v1.9.2` [from our CDN](https://cdn.img.ly/packages/imgly/cesdk-engine/1.9.2/assets/extensions.zip).
+Otherwise your scenes will **render missing asset alerts**.
+
+### 2.1 Making use of Default and Demo Asset Sources
+
+We still want to offer a package, that has all batteries included and quickly gets you up to speed.
+To do so, we introduced two new convenience functions, that can be used to add a set of predefined asset sources to your integration:
+
+#### `addDefaultAssetSources`
+
+Adds a set of asset sources containing our default assets.
+
+These assets may be used in production and [served from your own servers](./serve-assets.md).
+The assets are parsed from the IMG.LY CDN at `{{base_url}}/<id>/content.json`, where `base_url` defaults to `https://cdn.img.ly/assets/v1`.
+Each source is created via `addLocalSource` and populated with the parsed assets.
+You can specify your own `base_url` or exclude certain source IDs.
+
+The following sources are added:
+
+| ID                        | Description                     |
+| ------------------------- | ------------------------------- |
+| `'ly.img.sticker'`        | Various stickers                |
+| `'ly.img.vectorpath'`     | Shapes and arrows               |
+| `'ly.img.filter.lut'`     | LUT effects of various kinds.   |
+| `'ly.img.filter.duotone'` | Color effects of various kinds. |
+
+#### `addDemoAssetSources`
+
+Registers a set of demo asset sources containing our example assets.
+These are not to meant to be used in your production code.
+
+The assets are parsed from the IMG.LY CDN at `https://cdn.img.ly/assets/demo/v1`.
+The `sceneMode` and `withUploadAssetSources` parameters control whether audio/video and upload sources are added.
+
+The following sources are added:
+
+| ID                      | Description                        |
+| ----------------------- | ---------------------------------- |
+| `'ly.img.image'`        | Sample images                      |
+| `'ly.img.image.upload'` | Demo source to upload image assets |
+| `'ly.img.audio'`        | Sample audios                      |
+| `'ly.img.audio.upload'` | Demo source to upload audio assets |
+| `'ly.img.video'`        | Sample audios                      |
+| `'ly.img.video.upload'` | Demo source to upload video assets |
+
+#### Modifying Default & Demo Sources
+
+After registration you can freely modify the contained assets using the Asset APIs.
+You can add or remove entire asset sources or individual assets.
+
+#### Upload Asset Sources
+
+The upload asset sources and library entries for video and audio were added to the default configuration from `addDefaultAssetSources`. If you have added these sources manually (like mentioned in our video docs) you can remove them now.
+
+## 3. AssetAPI Changes
+
+To further streamline interaction, the following breaking changes were made to the AssetAPI:
+
+- The `applyAsset` callbacks and `defaultApplyAsset` API now return an optional design block id in their callback if they created a new block.
+- `thumbUri` and `size` properties in `AssetDefinition` and `AssetResult` are now part of the `meta` property dictionary.
+- Values of the `blockType` asset meta property must now be design block type ids (e.g. `//ly.img.ubq/image`)
+
+## 4. A New Way to Add Images
+
+Instead of specifying additional images for the `CreativeEditorSDK` in `config.presets.images`, you should make use of `asset.addAsset` and add your images into the `ly.img.image` asset source.
+
+## 5. General API Changes
+
+The `blockType` `meta` property for assets changed from `ly.img.<type>` to fully qualified block types: E.g. `'ly.img.image'` now needs to be `'//ly.img.ubq/image'`.
+
+As we're starting to apply the 'fill' concept to more parts of the interface, we deprecated various fill color related APIs:
+
+- Deprecated `hasFillColor`, use `hasFill` and query `block.getEnum(id, 'fill/type')` for `Solid` type instead.
+- Deprecated `get/setFillColorRGBA`, use `setFillSolidColor`instead..
+- Deprecated `isFillColorEnabled`, use `isFillEnabled` instead.
+- Deprecated `setFillType` and `setFillGradientType`, use `createFill`, e.g., with type 'color' and then apply the fill block with `setFill` to the block instead. If the block has a fill, it should be removed with `getFill` and `destroy`.
+- Deprecated `getFillType` and `getFillGradientType`, query `block.getEnum(id, 'fill/type')` and `block.getEnum(id, 'fill/gradient/type')` instead instead
+- Deprecated `add/removeFillGradientColorStop` and `get/setFillGradientColorStops`.
+- Deprecated `get/setFillGradientControlPointX/Y`, use `block.getFloat(fill, keypath)` and `block.setFloat(fill, keypath, value)` with key paths 'fill/gradient/linear/startPointX/Y', 'fill/gradient/radial/centerPointX/Y', and 'fill/gradient/conical/centerPointX/Y' instead.
+- Deprecated `get/setFillGradientRadius`, use `block.getFloat(fill, 'fill/gradient/radial/radius')` and `block.setFloat(fill, 'fill/gradient/radial/radius', value)` instead."
+
+`camera/clearColor` property was replaced it with a global `clearColor` setting to allow controlling the clear color before loading a scene.
+
+Properties affecting playback that existed on both `Audio` and `VideoFill` where moved to a common `playback/` namespace:
+
+- `'fill/video/looping'` and `'audio/looping'` are now `'playback/looping'`
+- `'fill/video/volume'` and `'audio/volume'` are now `'playback/volume'`
+- `'fill/video/muted'` and `'audio/muted'` are now `'playback/muted'`
+
+---
+
+## More Resources
+
+- **[Vanilla JS/TS Documentation Index](https://img.ly/docs/cesdk/js.md)** - Browse all Vanilla JS/TS documentation
+- **[Complete Documentation](./llms-full.txt.md)** - Full documentation in one file (for LLMs)
+- **[Web Documentation](./js.md)** - Interactive documentation with examples
+- **[Support](mailto:support@img.ly)** - Contact IMG.LY support

package/assets/docs/guide/to-v1-13.md

@@ -0,0 +1,165 @@
+> This is one page of the CE.SDK Vanilla JS/TS documentation. For a complete overview, see the [Vanilla JS/TS Documentation Index](https://img.ly/docs/cesdk/js.md). For all docs in one file, see [llms-full.txt](./llms-full.txt.md).
+
+**Navigation:** [Upgrading](./upgrade.md) > [To v1.13](./to-v1-13.md)
+
+---
+
+In version v1.13, the way the CreativeEngine and
+CreativeEditor SDK are configured has changed. Several configuration options
+that were previously passed to `CreativeEngine.init()` or `CreativeEditor
+SDK.init()` have been removed or replaced. This document will explain the
+changes and describe the steps you can take to adapt them to your setup.
+
+#### CreativeEditorSDK initialization
+
+We are also introducing a new way of instantiating the CreativeEditorSDK, that
+provides more precise control over the initialization. Using
+`CreativeEditorSDK.create()`, you have the chance to configure the SDK before
+loading or creating a scene. This was not possible before. When using
+`CreativeEditorSDK.init()`, the SDK would create the initial scene before giving
+you the option to perform additional configuration via the API.
+
+The `create()` method will not create an initial scene for you. You need to do
+that yourself, using either the Scene API at `cesdk.editor.scene`, or one of the
+methods on the CreativeEditorSDK instance itself (`createDesignScene`,
+`createVideoScene`, `loadFromUrl`, `loadFromString`).
+
+### Rationale
+
+Over time the number options you could pass into the call to
+`CreativeEngine.init({...config})` has grown quite a bit. Initially this was the
+only place where you could configure the behavior and settings of the
+CreativeEngine, but over the past year we introduced several new APIs. One of those APIs
+is the EditorAPI, which lets you
+
+[adjust](./settings.md) many
+[settings](./settings.md) at runtime, not just at the launch of the app.
+
+To improve consistency of our APIs, we decided to scale back the options
+available in the configuration object in favor of changing settings via the
+EditorAPI. The only options that remain are those that are strictly necessary
+for the initialization of the CreativeEngine, such as the `baseUrl` and
+`license`.
+
+These changes were performed with the Creative Engine in mind, but since the
+CreativeEditor SDK shares a lot of the same code, the changes described in this
+document also apply to the configuration for the CE.SDK.
+
+### Changed configuration options
+
+The following is a list of all configuration options that have been changed or
+removed, along with instructions on how to migrate the use of these options in
+your codebase:
+
+- `scene` options (`dpi`, `pixelScaleFactor`) have been removed.
+  `scene/dpi` and `scene/pixelScaleFactor` can now be found as [properties on the scene in the BlockAPI](./concepts/blocks.md).
+- `page` options have been removed.
+  - `page.title.show` has been replaced with `cesdk.engine.editor.setSettingBool('page/title/show', enabled)`
+  - `page.title.fontFileUri` has been replaced with `cesdk.engine.editor.setSettingString('page/title/fontFileUri', uri)`
+  - `page.dimOutOfPageAreas` has been replaced with `cesdk.engine.editor.setSettingBool('page/dimOutOfPageAreas', dimEnabled)`
+- `assetSources` have been removed. To add asset sources, use the AssetAPI at `cesdk.engine.asset`.
+- `preset.colors` has been removed as it was never used, previously.
+- `presets.colorPalettes` has been removed from CreativeEngine as it was not used. It has been moved to `ui.colorPalette` in the CESDK.
+- `presets.images` has been removed. To add assets and asset sources, use the AssetAPI at `cesdk.engine.asset`.
+- `presets.pageFormats` has been removed from the CreativeEngine as it was not used. Is has been moved to `ui.pageFormats` in the CESDK.
+  Previously it was possible to mark a page format as default by setting `meta: {default: true}` in it.
+  In `ui.pageFormats`, this has been simplified, to just `default: true`.
+- `variables` has been removed. Use the [VariableAPI](./create-templates/add-dynamic-content/text-variables.md) instead.
+- `callbacks.log` has been moved to `logger`. Previously the logger callback would take
+  a `Loglevel` enum as a second parameter. This enum has been removed. Instead you can
+  define the loglevel with plain strings `'Warning' | 'Error' | 'Info' `
+
+### Change initialization code
+
+To ensure your users perceive a consistent UI experience, settings that have been moved
+to api calls should be made immediately after initializing the CreativeEngine.
+For the Creative Editor SDK, use the `create()` method, instead of `init()`
+
+#### CreativeEngine
+
+```
+const engine = await CreativeEngine.init(config);
+// 1. Configure Engine
+engine.editor.setSettingEnum('doubleClickSelectionMode', 'Direct');
+// ... other settings
+
+// 2. Create/load scene
+const sceneId = await engine.scene.create();
+
+// 3. Append Engine canvas element to the DOM
+document.getElementById('my-engine-container').append(engine.element);
+
+// ... your application code
+```
+
+#### CreativeEngine SDK
+
+```
+const cesdk = await CreativeEditorSDK.create('my-engine-container', config);
+// 1. Configure SDK
+cesdk.engine.asset.addSource(myAssetSource);
+// ... other settings
+
+// 2. Create/load scene
+const sceneId = await cesdk.createDesignScene(myPageFormats[pageFormatId]);
+
+// ... your application code
+```
+
+### Fallback and warnings
+
+The CreativeEngine and CreativeEditor SDK still interpret the config object with
+its previous settings.
+If removed configuration options are detected during intialization, a warning is
+printed to the console, with individual instructions on how to migrate them.
+It is recommended to adjust your configuration as described above for the best
+compatibility with future developments and to get rid of these warnings.
+
+The fallback mechanism is not enabled for the new `CreativeEditorSDK.create()`
+method! Passing removed configuration options to `create()` will cause that
+option to be ignored and an error will be printed to the console.
+
+### CreativeEngine Typescript definitions
+
+The more complex parts of our configuration (such as the page format definitions)
+were previously exporting type definitions under the `ConfigTypes` namespace
+in the CreativeEngine package. This namespace and all the types in it have been removed or moved elsewhere.
+
+For now we still export `ConfigTypes`, but have marked it and its members as `@deprecated`.
+Most of them are not used at all anymore, the rest have been moved elsewhere:
+
+- `ConfigTypes.Color` can now be imported directly as `PaletteColor`
+- `ConfigTypes.TypefaceDefinition` can be imported directly, as `TypefaceDefinition`.
+- `ConfigTypes.PageFormatDefinition` can be imported directly as `PageFormatDefinition` (CE.SDK only).
+- `ConfigTypes.Logger` can be imported directly as `Logger`
+
+The `LogLevel` enum that was previously used by `Logger` has been replaced with
+a string union (`'Warning' | 'Error' | 'Info'`).
+
+### CreativeEditorSDK Typescript definitions
+
+The CreativeEditor SDK package still _does_ export a `ConfigTypes` namespace.
+
+For use with the new `CreativeEditorSDK.create()`, we are offering a new type
+`CreateConfiguration`, which is lacking all of the removed keys instead of
+marking them as deprecated.
+
+### Demo asset sources
+
+When adding demo asset sources using `cesdk.addDemoAssetSources()`, or
+`engine.addDemoAssetSources()`, make sure to specify the correct scene mode. The
+installed demo asset sources vary between Design and Video modes.
+
+If you don't specify a scene mode, `addDemoAssetSources()` will try to add the
+correct sources based on the current scene, and default to `'Design'`. If you
+call `addDemoAssetSources()` _without_ a scene mode, and _before_ loading or
+creating a video scene, the audio and video asset sources will not be added.
+
+---
+
+## More Resources
+
+- **[Vanilla JS/TS Documentation Index](https://img.ly/docs/cesdk/js.md)** - Browse all Vanilla JS/TS documentation
+- **[Complete Documentation](./llms-full.txt.md)** - Full documentation in one file (for LLMs)
+- **[Web Documentation](./js.md)** - Interactive documentation with examples
+- **[Support](mailto:support@img.ly)** - Contact IMG.LY support

package/assets/docs/guide/to-v1-19.md

@@ -0,0 +1,315 @@
+> This is one page of the CE.SDK Vanilla JS/TS documentation. For a complete overview, see the [Vanilla JS/TS Documentation Index](https://img.ly/docs/cesdk/js.md). For all docs in one file, see [llms-full.txt](./llms-full.txt.md).
+
+**Navigation:** [Upgrading](./upgrade.md) > [To v1.19](./to-v1-19.md)
+
+---
+
+Version v1.19 of CreativeEngineSDK and CreativeEditorSDK introduces structural changes to many of the current design blocks, making them more composable and more powerful. Along with this update, there are mandatory license changes that require attention. This comes with a number of breaking changes. This document will explain the changes and describe the steps you need to take to adapt them to your setup.
+
+## **License Changes**
+
+The `license` parameter is now required for CreativeEngineSDK and CreativeEditorSDK. This means that you will need to update your license parameter in the `CreativeEngine.init` and `CreativeEditorSDK.create` configuration object properties. There is also a new `userId`, an optional unique ID tied to your application's user. This helps us accurately calculate monthly active users (MAU). Especially useful when one person uses the app on multiple devices with a sign-in feature, ensuring they're counted once. Providing this aids in better data accuracy.
+
+## **Graphic Design Block**
+
+A new generic `Graphic` design block with the type id `//ly.img.ubq/graphic` has been introduced, which forms the basis of the new unified block structure.
+
+## **Shapes**
+
+Similar to how the fill of a block is a separate object which can be attached to and replaced on a design block, we have now introduced a similar concept for the shape of a block.
+
+You use the new `createShape`, `getShape` and `setShape` APIs in order to define the shape of a design block. Only the new `//ly.img.ubq/graphic` block allows for its shape to be changed with these APIs.
+
+The new available shape types are:
+
+- `//ly.img.ubq/shape/rect`
+- `//ly.img.ubq/shape/line`
+- `//ly.img.ubq/shape/ellipse`
+- `//ly.img.ubq/shape/polygon`
+- `//ly.img.ubq/shape/star`
+- `//ly.img.ubq/shape/vector_path`
+
+The following block types are now removed in favor of using a `Graphic` block with one of the above mentioned shape instances:
+
+- `//ly.img.ubq/shapes/rect`
+- `//ly.img.ubq/shapes/line`
+- `//ly.img.ubq/shapes/ellipse`
+- `//ly.img.ubq/shapes/polygon`
+- `//ly.img.ubq/shapes/star`
+- `//ly.img.ubq/vector_path`
+
+(The removed type ids use the plural “shapes” and the new shape types use the singular “shape”)
+
+This structural change means that the shape-specific properties (e.g. the number of sides of a polygon) are not available on the design block any more but on the shape instances instead. You will have to add calls to `getShape` to get the instance id of the shape instance and then pass that to the property getter and setter APIs.
+
+Also remember to change property key strings in the getter and setter calls from the plural `shapes/…` to the singular `shape/…` to match the new type identifiers.
+
+## **Image and Sticker**
+
+Previously, `//ly.img.ubq/image` and `//ly.img.ubq/sticker` were their own high-level design block types. They do not support the fill APIs nor the effects APIs.
+
+Both of these blocks are now removed in favor of using a `Graphic` block with an image fill (`//ly.img.ubq/fill/image`) and using the effects APIs instead of the legacy image block’s numerous effects properties.
+
+At its core, the sticker block has always just been an image block that is heavily limited in its capabilities. You can not crop it, nor apply any effects to it. In order to replicate this difference as closely as possible in the new unified structure, more fine-grained scopes have been added. You can now limit the adopter’s ability to crop a block and to edit its appearance.
+
+Note that since these scopes only apply to a user of the editor with the “Adopter” role, a “Creator” user will now have all of the same editing options for both images and for blocks that used to be stickers.
+
+## **Scopes**
+
+The following is the list of changes to the design block scopes:
+
+- (Breaking) The permission to crop a block was split from `content/replace` and `design/style` into a separate scope: `layer/crop`.
+- Deprecated the `design/arrange` scope and renamed
+  `design/arrange/move` → `layer/move`
+  `design/arrange/resize` → `layer/resize`
+  `design/arrange/rotate` → `layer/rotate`
+  `design/arrange/flip` → `layer/flip`
+- Deprecated the `content/replace` scope. For `//ly.img.ubq/text` blocks, it is replaced with the new `text/edit` scope. For other blocks it is replaced with `fill/change`.
+- Deprecated the `design/style` scope and replaced it with the following fine-grained scopes: `text/character`, `stroke/change`, `layer/opacity`, `layer/blendMode`, `layer/visibility`, `layer/clipping`, `appearance/adjustments`, `appearance/filter`, `appearance/effect`, `appearance/blur`, `appearance/shadow`
+- Introduced `fill/change`, `stroke/change`, and `shape/change` scopes that control whether the fill, stroke or shape of a block may be edited by a user with an "Adopter" role.
+- The deprecated scopes are automatically mapped to their new corresponding scopes by the scope APIs for now until they will be removed completely in a future update.
+
+## **Kind**
+
+While the new unified block structure both simplifies a lot of code and makes design blocks more powerful, it also means that many of the design blocks that used to have unique type ids now all have the same generic `//ly.img.ubq/graphic` type, which means that calls to the `findByType` cannot be used to filter blocks based on their legacy type ids any more.
+
+Simultaneously, there are many instances in which different blocks in the scene which might have the same type and underlying technical structure have different semantic roles in the document and should therefore be treated differently by the user interface.
+
+To solve both of these problems, we have introduced the concept of a block “kind”. This is a mutable string that can be used to tag different blocks with a semantic label.
+
+You can get the kind of a block using the `getKind` API and you can query blocks with a specific kind using the `findByKind` API.
+
+CreativeEngine provides the following default kind values:
+
+- `image`
+- `video`
+- `sticker`
+- `scene`
+- `camera`
+- `stack`
+- `page`
+- `audio`
+- `text`
+- `shape`
+- `group`
+
+Unlike the immutable design block type id, you can change the kind of a block with the new `setKind` API.
+
+It is important to remember that the underlying structure and properties of a design block are not strictly defined by its kind, since the kind, shape, fill and effects of a block can be changed independent of each other. Therefore, a user-interface should not make assumptions about available properties of a block purely based on its kind.
+
+> **Note:** **Note**Due to legacy reasons, blocks with the kind "sticker" will continue to not allow
+> their contents to be cropped. This special behavior will be addressed and replaced
+> with a more general-purpose implementation in a future update.
+
+​
+
+## **Asset Definitions**
+
+The asset definitions have been updated to reflect the deprecation of legacy block type ids and the introduction of the “kind” property.
+
+In addition to the “blockType” meta property, you can now also define the `“shapeType”` ,`“fillType”` and `“kind”` of the block that should be created by the default implementation of the applyAsset function.
+
+- `“blockType”` defaults to `“//ly.img.ubq/graphic”` if left unspecified.
+- `“shapeType”` defaults to `“//ly.img.ubq/shape/rect”` if left unspecified
+- `“fillType”` defaults to `“//ly.img.ubq/fill/color”` if left unspecified
+
+Video block asset definitions used to specify the `“blockType”` as `“//ly.img.ubq/fill/video“`. The `“fillType”` meta asset property should now be used instead for such fill type ids.
+
+## **Automatic Migration**
+
+CreativeEngine will always continue to support scene files that contain the now removed legacy block types. Those design blocks will be automatically replaced by the equivalent new unified block structure when the scene is loaded, which means that the types of all legacy blocks will change to `“//ly.img.ubq/graphic”`.
+
+Note that this can mean that a block gains new capabilities that it did not have before. For example, the line shape block did not have any stroke properties, so the `hasStroke` API used to return `false`. However, after the automatic migration its `Graphic` design block replacement supports both strokes and fills, so the `hasStroke` API now returns `true` . Similarly, the image block did not support fills or effects, but the `Graphic` block does.
+
+## List of all Removed Block Type IDs
+
+- `//ly.img.ubq/image`
+- `//ly.img.ubq/sticker`
+- `//ly.img.ubq/shapes/rect`
+- `//ly.img.ubq/shapes/line`
+- `//ly.img.ubq/shapes/ellipse`
+- `//ly.img.ubq/shapes/polygon`
+- `//ly.img.ubq/shapes/star`
+- `//ly.img.ubq/vector_path`
+
+## **UI Configuration**
+
+The configuration options for the legacy blocks have also been removed under `config.ui.elements.blocks` and a new configuration option for the `ly.img.ubq/graphic` block type have been introduced which will then define which UI controls to enable for graphic blocks (crop, filters, adjustments, effects, blur). This new configuration option follows the same structure as before.
+
+Here is a list of the deprecated block configuration options:
+
+- `//ly.img.ubq/image`
+- `//ly.img.ubq/fill/video`
+- `//ly.img.ubq/shapes/rect`
+- `//ly.img.ubq/shapes/line`
+- `//ly.img.ubq/shapes/star`
+- `//ly.img.ubq/shapes/polygon`
+- `//ly.img.ubq/shapes/ellipse`
+- `//ly.img.ubq/vector_path`
+
+## Translations
+
+Some of the translation keys related to Scopes and Placeholder-Settings have been also updated:
+
+- Removed the following keys:
+  - `scope.content.replace`
+  - `scope.design.arrange`
+  - `scope.design.style`
+- Renamed the following keys:
+  - `scope.design.arrange.flip` is now `scope.layer.flip`
+  - `scope.design.arrange.move` is now `scope.layer.move`
+  - `scope.design.arrange.resize` is now `scope.layer.resize`
+  - `scope.design.arrange.rotate` is now `scope.layer.rotate`
+- Added the following keys:
+  - `component.placeholder.appearance.description`
+  - `component.placeholder.appearance`
+  - `component.placeholder.arrange.description`
+  - `component.placeholder.arrange`
+  - `component.placeholder.disableAll`
+  - `component.placeholder.enableAll`
+  - `component.placeholder.fill.description`
+  - `component.placeholder.fill`
+  - `component.placeholder.general.description`
+  - `component.placeholder.general`
+  - `component.placeholder.shape.description`
+  - `component.placeholder.shape`
+  - `component.placeholder.stroke.description`
+  - `component.placeholder.stroke`
+  - `component.placeholder.text.description`
+  - `component.placeholder.text`
+  - `scope.appearance.adjustments`
+  - `scope.appearance.blur`
+  - `scope.appearance.effect`
+  - `scope.appearance.filter`
+  - `scope.appearance.shadow`
+  - `scope.fill.change`
+  - `scope.layer.blendMode`
+  - `scope.layer.opacity`
+  - `scope.shape.change`
+  - `scope.stroke.change`
+  - `scope.text.character`
+  - `scope.text.edit`
+
+## **Types and API Signatures**
+
+To improve the type safety of our APIs, we have moved away from using the `DesignBlockType` enum and replaced with a set of types. Those changes have affected the following APIs:
+
+- `CESDK.engine.block.create()`
+- `CESDK.engine.block.createFill()`
+- `CESDK.engine.block.createEffect()`
+- `CESDK.engine.block.createBlur()`
+- `CESDK.engine.block.findByType()`
+- `CESDK.engine.block.getType()`
+
+> **Note:** **Note**The `create`, `findByType`, and `getType` APIs will no longer accept the IDs of
+> the deprecated legacy blocks and will throw an error when those are passed
+
+## **Code Examples**
+
+This section will show some code examples of the breaking changes and how it would look like after migrating.
+
+```js
+/** Block Creation */
+
+// Creating an Image before migration
+const image = cesdk.engine.block.create('image');
+cesdk.engine.block.setString(
+  image,
+  'image/imageFileURI',
+  'https://domain.com/link-to-image.jpg'
+);
+
+// Creating an Image after migration
+const block = cesdk.engine.block.create('graphic');
+const rectShape = cesdk.engine.block.createShape('rect');
+const imageFill = cesdk.engine.block.createFill('image');
+cesdk.engine.block.setString(
+  imageFill,
+  'fill/image/imageFileURI',
+  'https://domain.com/link-to-image.jpg'
+);
+cesdk.engine.block.setShape(block, rectShape);
+cesdk.engine.block.setFill(block, imageFill);
+cesdk.engine.block.setKind(block, 'image');
+
+// Creating a star shape before migration
+const star = cesdk.engine.block.create('shapes/star');
+cesdk.engine.block.setInt(star, 'shapes/star/points', 8);
+
+// Creating a star shape after migration
+const block = cesdk.engine.block.create('graphic');
+const starShape = cesdk.engine.block.createShape('star');
+const colorFill = cesdk.engine.block.createFill('color');
+cesdk.engine.block.setInt(starShape, 'shape/star/points', 8);
+cesdk.engine.block.setShape(block, starShape);
+cesdk.engine.block.setFill(block, colorFill);
+cesdk.engine.block.setKind(block, 'shape');
+
+// Creating a sticker before migration
+const sticker = cesdk.engine.block.create('sticker');
+cesdk.engine.setString(
+  sticker,
+  'sticker/imageFileURI',
+  'https://domain.com/link-to-sticker.png'
+);
+
+// Creating a sticker after migration
+const block = cesdk.engine.block.create('graphic');
+const rectShape = cesdk.engine.block.createShape('rect');
+const imageFill = cesdk.engine.block.createFill('image');
+cesdk.engine.block.setString(
+  imageFill,
+  'fill/image/imageFileURI',
+  'https://domain.com/link-to-sticker.png'
+);
+cesdk.engine.block.setShape(block, rectShape);
+cesdk.engine.block.setFill(block, imageFill);
+cesdk.engine.block.setKind(block, 'sticker');
+
+/** Block Creation */
+```
+
+```js
+/** Block Exploration */
+
+// Query all images in the scene before migration
+const images = cesdk.engine.block.findByType('image');
+
+// Query all images in the scene after migration
+const images = cesdk.engine.block.findByType('graphic').filter((block) => {
+  const fill = cesdk.engine.block.getFill(block);
+  return (
+    cesdk.engine.block.isValid(fill) &&
+    cesdk.engine.block.getType(fill) === '//ly.img.ubq/fill/image'
+  );
+});
+
+// Query all stickers in the scene before migration
+const stickers = cesdk.engine.block.findByType('sticker');
+
+// Query all stickers in the scene after migration
+const stickers = cesdk.engine.block.findByKind('sticker');
+
+// Query all Polygon shapes in the scene before migration
+const polygons = cesdk.engine.block.findByType('shapes/polygon');
+
+// Query all Polygon shapes in the scene after migration
+const polygons = cesdk.engine.block.findByType('graphic').filter((block) => {
+  const shape = cesdk.engine.block.getShape(block);
+  return (
+    cesdk.engine.block.isValid(shape) &&
+    cesdk.engine.block.getType(shape) === '//ly.img.ubq/shape/polygon'
+  );
+});
+
+/** Block Exploration */
+```
+
+---
+
+## More Resources
+
+- **[Vanilla JS/TS Documentation Index](https://img.ly/docs/cesdk/js.md)** - Browse all Vanilla JS/TS documentation
+- **[Complete Documentation](./llms-full.txt.md)** - Full documentation in one file (for LLMs)
+- **[Web Documentation](./js.md)** - Interactive documentation with examples
+- **[Support](mailto:support@img.ly)** - Contact IMG.LY support