@imgly/codesign-mcp 0.1.5 → 0.1.6

package/assets/docs/guide/colors.md

@@ -1,9 +1,12 @@
-> 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).
+> This is one page of the CE.SDK Node.js documentation. For a complete overview, see the [Node.js Documentation Index](https://img.ly/docs/cesdk/node.md). For all docs in one file, see [llms-full.txt](./llms-full.txt.md).
 
 **Navigation:** [Guides](./guides.md) > [Colors](./colors.md)
 
 ---
 
+
+
+
 ---
 
 ## Related Pages
@@ -16,13 +19,15 @@
 - [Create a Color Palette](./colors/create-color-palette.md) - Build reusable color palettes to maintain consistency and streamline user choices.
 - [Replace Individual Colors](./colors/replace.md) - Selectively replace specific colors in images using CE.SDK's Recolor and Green Screen effects to swap colors or remove backgrounds.
 - [Adjust Colors](./colors/adjust.md) - Fine-tune images and design elements by adjusting brightness, contrast, saturation, exposure, and other color properties using CE.SDK's adjustments effect system.
+- [Extract Dominant Colors (Node.js)](./colors/extract-colors.md) - Read the most prominent colors from the rendered appearance of a block with the CE.SDK engine in Node.js.
 - [Color Conversion](./colors/conversion.md) - Learn how to convert colors between color spaces in CE.SDK. Convert sRGB, CMYK, and spot colors programmatically for screen display or print workflows.
 
+
 ---
 
 ## More Resources
 
-- **[Vanilla JS/TS Documentation Index](https://img.ly/docs/cesdk/js.md)** - Browse all Vanilla JS/TS documentation
+- **[Node.js Documentation Index](https://img.ly/docs/cesdk/node.md)** - Browse all Node.js 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
+- **[Web Documentation](./node.md)** - Interactive documentation with examples
+- **[Support](mailto:support@img.ly)** - Contact IMG.LY support

package/assets/docs/guide/compatibility.md

@@ -1,4 +1,4 @@
-> 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).
+> This is one page of the CE.SDK Node.js documentation. For a complete overview, see the [Node.js Documentation Index](https://img.ly/docs/cesdk/node.md). For all docs in one file, see [llms-full.txt](./llms-full.txt.md).
 
 **Navigation:** [Compatibility & Security](./compatibility.md)
 
@@ -8,20 +8,22 @@ CE.SDK provides robust compatibility and security features across platforms.
 Learn about supported browsers, frameworks, file formats, language support,
 and how CE.SDK ensures secure operation in your applications.
 
+
+
 ---
 
 ## Related Pages
 
-- [Browser Support](./browser-support.md) - Find out which browsers and versions fully support CE.SDK features, including editing and video capabilities.
 - [System Compatibility](./compatibility.md) - Learn how device performance and hardware limits affect CE.SDK editing, rendering, and export capabilities.
 - [File Format Support](./file-format-support.md) - See which image, video, audio, font, and template formats CE.SDK supports for import and export.
 - [Security](./security.md) - Learn how CE.SDK keeps your data private with client-side processing, secure licensing, and GDPR-compliant practices.
 
+
 ---
 
 ## More Resources
 
-- **[Vanilla JS/TS Documentation Index](https://img.ly/docs/cesdk/js.md)** - Browse all Vanilla JS/TS documentation
+- **[Node.js Documentation Index](https://img.ly/docs/cesdk/node.md)** - Browse all Node.js 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
+- **[Web Documentation](./node.md)** - Interactive documentation with examples
+- **[Support](mailto:support@img.ly)** - Contact IMG.LY support

package/assets/docs/guide/concepts/architecture.md

@@ -1,4 +1,4 @@
-> 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).
+> This is one page of the CE.SDK Node.js documentation. For a complete overview, see the [Node.js Documentation Index](https://img.ly/docs/cesdk/node.md). For all docs in one file, see [llms-full.txt](./llms-full.txt.md).
 
 **Navigation:** [Concepts](./concepts.md) > [Architecture](./concepts/architecture.md)
 
@@ -10,9 +10,9 @@ CE.SDK is built around the **CreativeEngine**—a single-threaded core runtime t
 
 ## The CreativeEngine
 
-The _Engine_ is the central coordinator. All operations—creating content, manipulating blocks, rendering, and exporting—flow through it. Initialize it once and access everything else through its API namespaces.
+The *Engine* is the central coordinator. All operations—creating content, manipulating blocks, rendering, and exporting—flow through it. Initialize it once and access everything else through its API namespaces.
 
-The _Engine_ manages:
+The *Engine* manages:
 
 - **One active scene** containing all design content
 - **Six API namespaces** for different domains of functionality
@@ -22,7 +22,7 @@ The _Engine_ manages:
 
 ## Content Hierarchy
 
-CE.SDK organizes content in a tree: _Scene_ → _Pages_ → _Blocks_.
+CE.SDK organizes content in a tree: *Scene* → *Pages* → *Blocks*.
 
 - **Scene**: The root container. One scene per engine instance. Supports both static designs and time-based video editing.
 - **Pages**: Containers within a scene. Artboards for static designs, time-based compositions for video editing.
@@ -36,23 +36,23 @@ The engine exposes six API namespaces. Here's how they interconnect:
 
 ### Scene API (`engine.scene`)
 
-Creates and manages the content hierarchy. Works with the _Block API_ to populate scenes with content and the _Event API_ to notify when structure changes.
+Creates and manages the content hierarchy. Works with the *Block API* to populate scenes with content and the *Event API* to notify when structure changes.
 
 ### Block API (`engine.block`)
 
-The most-used API. Creates, modifies, and queries blocks. Every visual element flows through here. Blocks reference _Assets_ loaded through the _Asset API_ and can contain _Variables_ managed by the _Variable API_.
+The most-used API. Creates, modifies, and queries blocks. Every visual element flows through here. Blocks reference *Assets* loaded through the *Asset API* and can contain *Variables* managed by the *Variable API*.
 
 ### Asset API (`engine.asset`)
 
-Provides content to the _Block API_. Registers asset sources (images, videos, stickers, templates) and handles queries. When you add an image to a block, the _Asset API_ resolves it and the _Block API_ applies it.
+Provides content to the *Block API*. Registers asset sources (images, videos, stickers, templates) and handles queries. When you add an image to a block, the *Asset API* resolves it and the *Block API* applies it.
 
 ### Variable API (`engine.variable`)
 
-Enables data-driven designs. Define variables at the scene level; reference them in text blocks with `{{variableName}}` syntax. When variable values change, affected blocks update automatically—coordinated through the _Event API_.
+Enables data-driven designs. Define variables at the scene level; reference them in text blocks with `{{variableName}}` syntax. When variable values change, affected blocks update automatically—coordinated through the *Event API*.
 
 ### Editor API (`engine.editor`)
 
-Controls application state: edit modes, undo/redo history, user roles, and permissions. The _Editor API_ determines what operations the _Block API_ can perform based on current role and scope settings.
+Controls application state: edit modes, undo/redo history, user roles, and permissions. The *Editor API* determines what operations the *Block API* can perform based on current role and scope settings.
 
 ### Event API (`engine.event`)
 
@@ -69,7 +69,7 @@ A typical flow shows the interconnection:
 5. **Editor API** controls what users can modify
 6. **Event API** notifies your UI of every change
 
-Each API focuses on one domain but works through the others. The _Engine_ coordinates these interactions.
+Each API focuses on one domain but works through the others. The *Engine* coordinates these interactions.
 
 ## Scene Capabilities
 
@@ -78,22 +78,24 @@ CE.SDK scenes support a range of capabilities:
 - **Static designs**: Social posts, print materials, graphics. Blocks positioned spatially.
 - **Time-based content**: Duration, playback time, and animation. Blocks arranged across time.
 
-The scene configuration determines which _Block API_ properties and _Editor API_ capabilities are available. See [Scenes](./concepts/scenes.md) for details.
+The scene configuration determines which *Block API* properties and *Editor API* capabilities are available. See [Scenes](./concepts/scenes.md) for details.
 
 ## Integration Patterns
 
 CE.SDK runs in two contexts:
 
 - **Browser**: The engine renders to a canvas element. Append `engine.element` to your DOM. Use with the built-in UI or build your own.
-- **Headless**: No rendering, just processing. Use for server-side exports, automation, and batch operations. See [Headless Mode](./concepts/headless-mode/browser.md).
+- **Headless**: No rendering, just processing. Use for server-side exports, automation, and batch operations. See [Headless Mode](./concepts/headless-mode.md).
 
 Both contexts use the same six APIs—only rendering differs.
 
+
+
 ---
 
 ## More Resources
 
-- **[Vanilla JS/TS Documentation Index](https://img.ly/docs/cesdk/js.md)** - Browse all Vanilla JS/TS documentation
+- **[Node.js Documentation Index](https://img.ly/docs/cesdk/node.md)** - Browse all Node.js 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
+- **[Web Documentation](./node.md)** - Interactive documentation with examples
+- **[Support](mailto:support@img.ly)** - Contact IMG.LY support

package/assets/docs/guide/concepts/assets.md

@@ -1,4 +1,4 @@
-> 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).
+> This is one page of the CE.SDK Node.js documentation. For a complete overview, see the [Node.js Documentation Index](https://img.ly/docs/cesdk/node.md). For all docs in one file, see [llms-full.txt](./llms-full.txt.md).
 
 **Navigation:** [Concepts](./concepts.md) > [Assets](./concepts/assets.md)
 
@@ -6,100 +6,52 @@
 
 Understand the asset system—how external media and resources like images, stickers, or videos are handled in CE.SDK.
 
-![Assets example showing asset source and applied content](https://img.ly/docs/cesdk/./assets/browser.hero.webp)
-
 > **Reading time:** 5 minutes
 >
 > **Resources:**
 >
 > - [Download examples](https://github.com/imgly/cesdk-web-examples/archive/refs/tags/release-$UBQ_VERSION$.zip)
-> - [View source on GitHub](https://github.com/imgly/cesdk-web-examples/tree/release-$UBQ_VERSION$/guides-concepts-assets-browser)
-> - [Open in StackBlitz](https://stackblitz.com/github/imgly/cesdk-web-examples/tree/v$UBQ_VERSION$/guides-concepts-assets-browser)
-> - [Live demo](https://img.ly/docs/cesdk/examples/guides-concepts-assets-browser/)
+>
+> - [View source on GitHub](https://github.com/imgly/cesdk-web-examples/tree/release-$UBQ_VERSION$/guides-concepts-assets-server-js)
+>
+> - [Open in StackBlitz](https://stackblitz.com/github/imgly/cesdk-web-examples/tree/v$UBQ_VERSION$/guides-concepts-assets-server-js)
 
-Images, videos, audio, fonts, stickers, and templates—every premade resource you can add to a design is what we call an _Asset_. The editor gets access to these Assets through _Asset Sources_. When you apply an Asset, CE.SDK creates or modifies a Block to display that content.
+Images, videos, audio, fonts, stickers, and templates—every premade resource you can add to a design is what we call an *Asset*. The editor gets access to these Assets through *Asset Sources*. When you apply an Asset, CE.SDK creates or modifies a Block to display that content.
 
-```typescript file=@cesdk_web_examples/guides-concepts-assets-browser/browser.ts reference-only
-import type {
-  AssetQueryData,
-  AssetResult,
+```typescript file=@cesdk_web_examples/guides-concepts-assets-server-js/server-js.ts reference-only
+import CreativeEngine, {
   AssetSource,
+  AssetQueryData,
   AssetsQueryResult,
-  EditorPlugin,
-  EditorPluginContext
-} from '@cesdk/cesdk-js';
-import packageJson from './package.json';
-
-import {
-  BlurAssetSource,
-  ColorPaletteAssetSource,
-  CropPresetsAssetSource,
-  DemoAssetSources,
-  EffectsAssetSource,
-  FiltersAssetSource,
-  PagePresetsAssetSource,
-  StickerAssetSource,
-  TextAssetSource,
-  TextComponentAssetSource,
-  TypefaceAssetSource,
-  UploadAssetSources,
-  VectorShapeAssetSource
-} from '@cesdk/cesdk-js/plugins';
-import { DesignEditorConfig } from './design-editor/plugin';
+  AssetResult
+} from '@cesdk/node';
+import { config } from 'dotenv';
+
+// Load environment variables from .env file
+config();
 
 /**
- * CE.SDK Plugin: Assets Concepts Guide
+ * CE.SDK Server Example: Assets Concepts Guide
  *
  * Demonstrates the core concepts of the asset system:
  * - What assets are and how they differ from blocks
  * - Creating and registering asset sources
  * - Querying and applying assets
  */
-class Example implements EditorPlugin {
-  name = packageJson.name;
-
-  version = packageJson.version;
-
-  async initialize({ cesdk }: EditorPluginContext): Promise<void> {
-    if (!cesdk) {
-      throw new Error('CE.SDK instance is required for this plugin');
-    }
-    await cesdk.addPlugin(new DesignEditorConfig());
-
-    // Add asset source plugins
-    await cesdk.addPlugin(new BlurAssetSource());
-    await cesdk.addPlugin(new ColorPaletteAssetSource());
-    await cesdk.addPlugin(new CropPresetsAssetSource());
-    await cesdk.addPlugin(
-      new UploadAssetSources({ include: ['ly.img.image.upload'] })
-    );
-    await cesdk.addPlugin(
-      new DemoAssetSources({
-        include: [
-          'ly.img.templates.blank.*',
-          'ly.img.templates.presentation.*',
-          'ly.img.templates.print.*',
-          'ly.img.templates.social.*',
-          'ly.img.image.*'
-        ]
-      })
-    );
-    await cesdk.addPlugin(new EffectsAssetSource());
-    await cesdk.addPlugin(new FiltersAssetSource());
-    await cesdk.addPlugin(new PagePresetsAssetSource());
-    await cesdk.addPlugin(new StickerAssetSource());
-    await cesdk.addPlugin(new TextAssetSource());
-    await cesdk.addPlugin(new TextComponentAssetSource());
-    await cesdk.addPlugin(new TypefaceAssetSource());
-    await cesdk.addPlugin(new VectorShapeAssetSource());
-
-    await cesdk.actions.run('scene.create', {
-      page: {
-        sourceId: 'ly.img.page.presets',
-        assetId: 'ly.img.page.presets.print.iso.a6.landscape'
-      }
-    });
-    const engine = cesdk.engine;
+async function main(): Promise<void> {
+  // Initialize the headless Creative Engine
+  const engine = await CreativeEngine.init({
+    baseURL: process.env.IMGLY_LOCAL_ASSETS_URL
+    // license: process.env.CESDK_LICENSE,
+  });
+
+  try {
+    // Create a scene with a page
+    const scene = engine.scene.create();
+    const page = engine.block.create('page');
+    engine.block.appendChild(scene, page);
+    engine.block.setWidth(page, 800);
+    engine.block.setHeight(page, 600);
 
     // An asset is a content definition with metadata
     // It describes content that can be added to designs
@@ -145,14 +97,32 @@ class Example implements EditorPlugin {
     });
     console.log('Found assets:', results.total);
 
+    // Narrow a query with structured predicates. The top-level array is
+    // an implicit AND of its entries.
+    const happyStickers = await engine.asset.findAssets('my-assets', {
+      page: 0,
+      perPage: 10,
+      filter: [
+        // Either tag matches (combinators nest arbitrarily).
+        {
+          or: [
+            { property: 'tags', equals: 'happy' },
+            { property: 'tags', equals: 'celebratory' }
+          ]
+        },
+        // Exclude archived items.
+        { not: { property: 'meta.kind', equals: 'archived' } }
+      ]
+    });
+    console.log('Filtered stickers:', happyStickers.total);
+
     // Apply an asset to create a block in the scene
     if (results.assets.length > 0) {
       const blockId = await engine.asset.apply('my-assets', results.assets[0]);
       console.log('Created block:', blockId);
 
       // Center the sticker on the page
-      const page = engine.scene.getCurrentPage();
-      if (page && blockId) {
+      if (blockId) {
         const pageWidth = engine.block.getWidth(page);
         const pageHeight = engine.block.getHeight(page);
         // SVG is 62x58, scale to fit nicely
@@ -190,13 +160,19 @@ class Example implements EditorPlugin {
     engine.asset.assetSourceContentsChanged('uploads');
 
     unsubscribe();
+
+    console.log('Assets guide completed successfully.');
+    console.log('Created custom asset source and applied sticker asset.');
+  } finally {
+    // Always dispose the engine to free resources
+    engine.dispose();
   }
 }
 
-export default Example;
+main().catch(console.error);
 ```
 
-This guide covers the core concepts of the Asset system. For detailed instructions on inserting specific media types, see the [Images](./insert-media/images.md), [Videos](./insert-media/videos.md), and [Shapes & Stickers](./insert-media/shapes-or-stickers.md) guides.
+This guide covers the core concepts of the Asset system: what assets are, how to create asset sources, and how to query and apply assets programmatically.
 
 ## Assets vs Blocks
 
@@ -244,23 +220,23 @@ Key properties include:
 Asset sources provide assets to the editor. Each source has an `id` and implements a `findAssets()` method that returns paginated results.
 
 ```typescript highlight-asset-source
-// Asset sources provide assets to the editor
-// Each source has an id and a findAssets() method
-const customSource: AssetSource = {
-  id: 'my-assets',
-
-  async findAssets(query: AssetQueryData): Promise<AssetsQueryResult> {
-    // Return paginated results matching the query
-    return {
-      assets: [stickerAsset],
-      total: 1,
-      currentPage: query.page,
-      nextPage: undefined
+    // Asset sources provide assets to the editor
+    // Each source has an id and a findAssets() method
+    const customSource: AssetSource = {
+      id: 'my-assets',
+
+      async findAssets(query: AssetQueryData): Promise<AssetsQueryResult> {
+        // Return paginated results matching the query
+        return {
+          assets: [stickerAsset],
+          total: 1,
+          currentPage: query.page,
+          nextPage: undefined
+        };
+      }
     };
-  }
-};
 
-engine.asset.addSource(customSource);
+    engine.asset.addSource(customSource);
 ```
 
 The `findAssets()` callback receives query parameters (`page`, `perPage`, `query`, `tags`, `groups`) and returns a result object with `assets`, `total`, `currentPage`, and `nextPage`.
@@ -282,30 +258,64 @@ console.log('Found assets:', results.total);
 
 Results include pagination info. Loop through pages until `nextPage` is undefined to retrieve all matching assets.
 
+### Filtering by property
+
+The optional `filter` parameter narrows a query with structured predicates against the resolved asset. All entries in the top-level array must match (implicit AND). Each entry is either a property predicate (`{ property, contains?, equals? }`) or a logical combinator (`{ and: [...] }`, `{ or: [...] }`, `{ not: ... }`). Combinators nest.
+
+```typescript highlight-filter-assets
+// Narrow a query with structured predicates. The top-level array is
+// an implicit AND of its entries.
+const happyStickers = await engine.asset.findAssets('my-assets', {
+  page: 0,
+  perPage: 10,
+  filter: [
+    // Either tag matches (combinators nest arbitrarily).
+    {
+      or: [
+        { property: 'tags', equals: 'happy' },
+        { property: 'tags', equals: 'celebratory' }
+      ]
+    },
+    // Exclude archived items.
+    { not: { property: 'meta.kind', equals: 'archived' } }
+  ]
+});
+console.log('Filtered stickers:', happyStickers.total);
+```
+
+The `property` field is a dot-path against the resolved asset: `label`, `tags`, `id`, `groups`, or `meta.<key>`. Use `equals` for categorical or single-value fields and `contains` for free-text or list-encoded values. Both operators are case-insensitive. On a string array (`tags`, `groups`), the predicate matches if any element matches.
+
+> **\`not\` against a missing key:** A predicate evaluates to `false` on an asset that lacks the targeted field, so `not { property: 'meta.legacy', equals: 'true' }` matches every asset where `meta.legacy !== 'true'` **and** every asset that lacks `meta.legacy` entirely. If you need "field is present and not equal to x," combine with a presence check: `and: [{ property: 'meta.legacy', contains: '' }, { not: { ... } }]`.
+
+> **\`meta\` values are flat strings:** The engine stores every `meta.<key>` value as a flat string. `equals: 'true'` matches the literal string `"true"`; if a meta value was originally serialized as a number or boolean, stringify it the same way before comparing. For multi-valued data, prefer separate `tags` / `groups` elements over comma-separated `meta` values so `equals` can be element-exact.
+
+`filter` and the legacy `tags` / `groups` / `excludeGroups` fields can be combined — they are AND-combined before pagination. Prefer `filter` for anything beyond a plain case-sensitive include/exclude list (substring matches, `meta.<key>`, `or` / `not` combinators); reach for the legacy fields only when you want their case-sensitive exact-match semantics.
+
+Malformed filters reject the returned promise with the engine's parse-error message (for example, `"Unknown asset property '…'"` or `"Asset property filter must have exactly one of 'contains' or 'equals'."`).
+
 ## Applying Assets
 
 Use `apply()` to create a new block from an asset:
 
 ```typescript highlight-apply-asset
-// Apply an asset to create a block in the scene
-if (results.assets.length > 0) {
-  const blockId = await engine.asset.apply('my-assets', results.assets[0]);
-  console.log('Created block:', blockId);
-
-  // Center the sticker on the page
-  const page = engine.scene.getCurrentPage();
-  if (page && blockId) {
-    const pageWidth = engine.block.getWidth(page);
-    const pageHeight = engine.block.getHeight(page);
-    // SVG is 62x58, scale to fit nicely
-    const stickerWidth = 62;
-    const stickerHeight = 58;
-    engine.block.setWidth(blockId, stickerWidth);
-    engine.block.setHeight(blockId, stickerHeight);
-    engine.block.setPositionX(blockId, (pageWidth - stickerWidth) / 2);
-    engine.block.setPositionY(blockId, (pageHeight - stickerHeight) / 2);
-  }
-}
+    // Apply an asset to create a block in the scene
+    if (results.assets.length > 0) {
+      const blockId = await engine.asset.apply('my-assets', results.assets[0]);
+      console.log('Created block:', blockId);
+
+      // Center the sticker on the page
+      if (blockId) {
+        const pageWidth = engine.block.getWidth(page);
+        const pageHeight = engine.block.getHeight(page);
+        // SVG is 62x58, scale to fit nicely
+        const stickerWidth = 62;
+        const stickerHeight = 58;
+        engine.block.setWidth(blockId, stickerWidth);
+        engine.block.setHeight(blockId, stickerHeight);
+        engine.block.setPositionX(blockId, (pageWidth - stickerWidth) / 2);
+        engine.block.setPositionY(blockId, (pageHeight - stickerHeight) / 2);
+      }
+    }
 ```
 
 The method returns the new block ID, which you can use to position and configure the block.
@@ -315,21 +325,21 @@ The method returns the new block ID, which you can use to position and configure
 Local sources store assets in memory and support dynamic add/remove operations. Use these for user uploads or runtime-generated content:
 
 ```typescript highlight-local-source
-// Local sources support dynamic add/remove operations
-engine.asset.addLocalSource('uploads', ['image/svg+xml', 'image/png']);
+    // Local sources support dynamic add/remove operations
+    engine.asset.addLocalSource('uploads', ['image/svg+xml', 'image/png']);
 
-engine.asset.addAssetToSource('uploads', {
-  id: 'uploaded-1',
-  label: { en: 'Heart Sticker' },
-  meta: {
-    uri: 'https://cdn.img.ly/assets/v3/ly.img.sticker/images/emoticons/imgly_sticker_emoticons_love.svg',
-    thumbUri:
-      'https://cdn.img.ly/assets/v3/ly.img.sticker/images/emoticons/imgly_sticker_emoticons_love.svg',
-    blockType: '//ly.img.ubq/graphic',
-    fillType: '//ly.img.ubq/fill/image',
-    mimeType: 'image/svg+xml'
-  }
-});
+    engine.asset.addAssetToSource('uploads', {
+      id: 'uploaded-1',
+      label: { en: 'Heart Sticker' },
+      meta: {
+        uri: 'https://cdn.img.ly/assets/v3/ly.img.sticker/images/emoticons/imgly_sticker_emoticons_love.svg',
+        thumbUri:
+          'https://cdn.img.ly/assets/v3/ly.img.sticker/images/emoticons/imgly_sticker_emoticons_love.svg',
+        blockType: '//ly.img.ubq/graphic',
+        fillType: '//ly.img.ubq/fill/image',
+        mimeType: 'image/svg+xml'
+      }
+    });
 ```
 
 ## Source Events
@@ -337,24 +347,26 @@ engine.asset.addAssetToSource('uploads', {
 Subscribe to asset source lifecycle events for reactive UIs:
 
 ```typescript highlight-source-events
-// Subscribe to asset source lifecycle events
-const unsubscribe = engine.asset.onAssetSourceUpdated((sourceId) => {
-  console.log('Source updated:', sourceId);
-});
+    // Subscribe to asset source lifecycle events
+    const unsubscribe = engine.asset.onAssetSourceUpdated((sourceId) => {
+      console.log('Source updated:', sourceId);
+    });
 
-// Notify that source contents changed
-engine.asset.assetSourceContentsChanged('uploads');
+    // Notify that source contents changed
+    engine.asset.assetSourceContentsChanged('uploads');
 
-unsubscribe();
+    unsubscribe();
 ```
 
 Call `assetSourceContentsChanged()` after modifying a source to notify subscribers.
 
+
+
 ---
 
 ## More Resources
 
-- **[Vanilla JS/TS Documentation Index](https://img.ly/docs/cesdk/js.md)** - Browse all Vanilla JS/TS documentation
+- **[Node.js Documentation Index](https://img.ly/docs/cesdk/node.md)** - Browse all Node.js 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
+- **[Web Documentation](./node.md)** - Interactive documentation with examples
+- **[Support](mailto:support@img.ly)** - Contact IMG.LY support