@imgly/codesign-mcp 0.1.5 → 0.1.6

package/assets/docs/guide/automation/data-merge.md

@@ -1,117 +1,104 @@
-> 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) > [Automate Workflows](./automation.md) > [Data Merge](./automation/data-merge.md)
 
 ---
 
-Generate personalized designs from a single template by merging external data into CE.SDK templates using text variables and placeholder blocks.
-
-![Data Merge example showing personalized business card design](https://img.ly/docs/cesdk/./assets/browser.hero.webp)
+Generate personalized designs at scale using CE.SDK's headless Node.js API to batch process templates with external data.
 
 > **Reading time:** 10 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-automation-data-merge-browser)
-> - [Open in StackBlitz](https://stackblitz.com/github/imgly/cesdk-web-examples/tree/v$UBQ_VERSION$/guides-automation-data-merge-browser)
-> - [Live demo](https://img.ly/docs/cesdk/examples/guides-automation-data-merge-browser/)
-
-Data merge generates multiple personalized designs from a single template by replacing variable content with external data. Use it for certificates, badges, team cards, or any design requiring consistent layout with varying content.
-
-```typescript file=@cesdk_web_examples/guides-automation-data-merge-browser/browser.ts reference-only
-import type { EditorPlugin, EditorPluginContext } from '@cesdk/cesdk-js';
-
-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';
-import packageJson from './package.json';
+>
+> - [View source on GitHub](https://github.com/imgly/cesdk-web-examples/tree/release-$UBQ_VERSION$/guides-automation-data-merge-server-js)
+>
+> - [Open in StackBlitz](https://stackblitz.com/github/imgly/cesdk-web-examples/tree/v$UBQ_VERSION$/guides-automation-data-merge-server-js)
+
+Data merge generates multiple personalized designs from a single template by replacing variable content with external data. Server-side processing enables batch operations for certificates, badges, team cards, or any design requiring consistent layout with varying content.
+
+```typescript file=@cesdk_web_examples/guides-automation-data-merge-server-js/server-js.ts reference-only
+import CreativeEngine from '@cesdk/node';
+import { config } from 'dotenv';
+import { writeFileSync, mkdirSync, existsSync } from 'fs';
+
+// Load environment variables
+config();
 
 /**
- * CE.SDK Plugin: Data Merge Guide
+ * CE.SDK Server Guide: Data Merge
  *
- * Demonstrates merging external data into templates:
- * - Setting text variables with engine.variable.setString()
- * - Finding variables with engine.variable.findAll()
- * - Finding blocks by name with engine.block.findByName()
- * - Updating image content in placeholder blocks
- * - Exporting personalized designs
+ * Demonstrates batch processing of personalized designs:
+ * - Loading templates with text variables
+ * - Setting variable values from data records
+ * - Finding and updating placeholder blocks by name
+ * - Exporting personalized designs to PNG
+ * - Processing multiple records in a batch
  */
-class Example implements EditorPlugin {
-  name = packageJson.name;
 
-  version = packageJson.version;
+// Initialize CE.SDK engine in headless mode
+const engine = await CreativeEngine.init({
+  baseURL: process.env.IMGLY_LOCAL_ASSETS_URL
+  // license: process.env.CESDK_LICENSE, // Optional (trial mode available)
+});
 
-  async initialize({ cesdk }: EditorPluginContext): Promise<void> {
-    if (!cesdk) {
-      throw new Error('CE.SDK instance is required for this plugin');
+try {
+  // Sample data records for the merge operation
+  // In production, this data would come from a CSV, database, or API
+  const dataRecords = [
+    {
+      name: 'Alex Smith',
+      title: 'Creative Developer',
+      email: 'alex.smith@example.com',
+      photoUrl: 'https://img.ly/static/ubq_samples/sample_1.jpg'
+    },
+    {
+      name: 'Jordan Lee',
+      title: 'Product Designer',
+      email: 'jordan.lee@example.com',
+      photoUrl: 'https://img.ly/static/ubq_samples/sample_2.jpg'
+    },
+    {
+      name: 'Taylor Chen',
+      title: 'UX Engineer',
+      email: 'taylor.chen@example.com',
+      photoUrl: 'https://img.ly/static/ubq_samples/sample_3.jpg'
     }
+  ];
 
-    await cesdk.addPlugin(new DesignEditorConfig());
+  // Prepare output directory
+  const outputDir = './output';
+  if (!existsSync(outputDir)) {
+    mkdirSync(outputDir, { recursive: true });
+  }
 
-    // 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: { width: 800, height: 400, unit: 'Pixel' }
-    });
+  // Store exported blobs for batch processing results
+  const outputs: { name: string; blob: Blob }[] = [];
 
-    const engine = cesdk.engine;
+  // Process each data record
+  for (const record of dataRecords) {
+    // Create a fresh scene for each record
+    engine.scene.create('VerticalStack', {
+      page: { size: { width: 800, height: 400 } }
+    });
     const page = engine.block.findByType('page')[0];
 
-    // Sample data to merge into the template
-    const sampleData = {
-      name: 'Alex Smith',
-      title: 'Creative Developer',
-      email: 'alex.smith@example.com',
-      photoUrl: 'https://img.ly/static/ubq_samples/sample_1.jpg'
-    };
+    // Set text variables from the data record
+    engine.variable.setString('name', record.name);
+    engine.variable.setString('title', record.title);
+    engine.variable.setString('email', record.email);
 
-    // Create a profile photo block with a semantic name
+    // Create the template layout with placeholder blocks
+
+    // Create a profile photo block on the left
     const photoBlock = engine.block.create('graphic');
     engine.block.setShape(photoBlock, engine.block.createShape('rect'));
     const photoFill = engine.block.createFill('image');
     engine.block.setString(
       photoFill,
       'fill/image/imageFileURI',
-      sampleData.photoUrl
+      record.photoUrl
     );
     engine.block.setFill(photoBlock, photoFill);
     engine.block.setWidth(photoBlock, 150);
@@ -121,7 +108,7 @@ class Example implements EditorPlugin {
     engine.block.setName(photoBlock, 'profile-photo');
     engine.block.appendChild(page, photoBlock);
 
-    // Create a text block with variable placeholders
+    // Create a text block with variable bindings
     const textBlock = engine.block.create('text');
     const textContent = `{{name}}
 {{title}}
@@ -134,273 +121,257 @@ class Example implements EditorPlugin {
     engine.block.setPositionY(textBlock, 140);
     engine.block.appendChild(page, textBlock);
 
-    // Set the variable values from data
-    engine.variable.setString('name', sampleData.name);
-    engine.variable.setString('title', sampleData.title);
-    engine.variable.setString('email', sampleData.email);
-
-    // Discover all variables in the scene
+    // Verify which variables exist in the scene
     const variables = engine.variable.findAll();
-    console.log('Variables in scene:', variables);
+    // eslint-disable-next-line no-console
+    console.log(`Processing ${record.name}, variables:`, variables);
 
     // Check if the text block references any variables
     const hasVariables = engine.block.referencesAnyVariables(textBlock);
-    console.log('Text block has variables:', hasVariables);
-
-    // Find blocks by their semantic name
-    const [foundPhotoBlock] = engine.block.findByName('profile-photo');
-    if (foundPhotoBlock) {
-      console.log('Found profile-photo block:', foundPhotoBlock);
-
-      // Update the image content
-      const fill = engine.block.getFill(foundPhotoBlock);
-      engine.block.setString(
-        fill,
-        'fill/image/imageFileURI',
-        'https://img.ly/static/ubq_samples/sample_2.jpg'
-      );
-    }
+    // eslint-disable-next-line no-console
+    console.log(`Text block has variables: ${hasVariables}`);
 
-    // Export the personalized design
+    // Export the personalized design to PNG
     const blob = await engine.block.export(page, { mimeType: 'image/png' });
-    console.log('Exported PNG blob:', blob.size, 'bytes');
 
-    // Create a download link for the exported image
-    const url = URL.createObjectURL(blob);
-    console.log('Download URL created:', url);
+    // Save the result
+    const filename = record.name.toLowerCase().replace(/\s+/g, '-');
+    const buffer = Buffer.from(await blob.arrayBuffer());
+    writeFileSync(`${outputDir}/${filename}.png`, buffer);
 
-    // Select the text block to show the variable values
-    engine.block.select(textBlock);
-
-    console.log(
-      'Data merge guide initialized. Try changing variable values in the console.'
-    );
+    outputs.push({ name: record.name, blob });
+    // eslint-disable-next-line no-console
+    console.log(`✓ Exported ${filename}.png`);
   }
-}
 
-export default Example;
+  // eslint-disable-next-line no-console
+  console.log(
+    `\n✓ Batch complete: ${outputs.length} designs exported to ${outputDir}/`
+  );
+} finally {
+  // Always dispose the engine to free resources
+  engine.dispose();
+}
 ```
 
-This guide covers how to prepare templates with variables, set values from data, and export personalized designs.
+This guide covers how to prepare data, build templates with variables, and process multiple records in a batch workflow.
 
-## Initialize the Editor
+## Initialize the Engine
 
-We start by initializing CE.SDK with a Design scene and setting up the page dimensions for our template.
+We start by initializing the headless Creative Engine. In production, you would typically pass your license key.
 
 ```typescript highlight=highlight-setup
-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: { width: 800, height: 400, unit: 'Pixel' }
+// Initialize CE.SDK engine in headless mode
+const engine = await CreativeEngine.init({
+  baseURL: process.env.IMGLY_LOCAL_ASSETS_URL
+  // license: process.env.CESDK_LICENSE, // Optional (trial mode available)
 });
-
-const engine = cesdk.engine;
-const page = engine.block.findByType('page')[0];
 ```
 
-## Prepare Sample Data
+## Prepare Data Records
 
-In a real application, data comes from a CSV file, database, or API. Here we define a sample record with the fields we want to merge into the template.
+Data typically comes from a CSV file, database query, or API response. Here we define sample records with the fields we want to merge into the template.
 
 ```typescript highlight=highlight-sample-data
-// Sample data to merge into the template
-const sampleData = {
-  name: 'Alex Smith',
-  title: 'Creative Developer',
-  email: 'alex.smith@example.com',
-  photoUrl: 'https://img.ly/static/ubq_samples/sample_1.jpg'
-};
+// Sample data records for the merge operation
+// In production, this data would come from a CSV, database, or API
+const dataRecords = [
+  {
+    name: 'Alex Smith',
+    title: 'Creative Developer',
+    email: 'alex.smith@example.com',
+    photoUrl: 'https://img.ly/static/ubq_samples/sample_1.jpg'
+  },
+  {
+    name: 'Jordan Lee',
+    title: 'Product Designer',
+    email: 'jordan.lee@example.com',
+    photoUrl: 'https://img.ly/static/ubq_samples/sample_2.jpg'
+  },
+  {
+    name: 'Taylor Chen',
+    title: 'UX Engineer',
+    email: 'taylor.chen@example.com',
+    photoUrl: 'https://img.ly/static/ubq_samples/sample_3.jpg'
+  }
+];
 ```
 
-Each data record contains field names that map to template variables and placeholder blocks.
+Each record contains field names that map to template variables and placeholder blocks.
 
-## Create Template Layout
+## Batch Processing Loop
 
-We build the template by creating blocks and assigning semantic names. The profile photo block uses `setName()` so we can find and update it later.
+We iterate through each data record, creating a fresh scene for each personalized output. This ensures variable values from previous records don't carry over.
 
-```typescript highlight=highlight-create-template
-// Create a profile photo block with a semantic name
-const photoBlock = engine.block.create('graphic');
-engine.block.setShape(photoBlock, engine.block.createShape('rect'));
-const photoFill = engine.block.createFill('image');
-engine.block.setString(
-  photoFill,
-  'fill/image/imageFileURI',
-  sampleData.photoUrl
-);
-engine.block.setFill(photoBlock, photoFill);
-engine.block.setWidth(photoBlock, 150);
-engine.block.setHeight(photoBlock, 150);
-engine.block.setPositionX(photoBlock, 50);
-engine.block.setPositionY(photoBlock, 125);
-engine.block.setName(photoBlock, 'profile-photo');
-engine.block.appendChild(page, photoBlock);
+```typescript highlight=highlight-batch-loop
+// Process each data record
+for (const record of dataRecords) {
+  // Create a fresh scene for each record
+  engine.scene.create('VerticalStack', {
+    page: { size: { width: 800, height: 400 } }
+  });
+  const page = engine.block.findByType('page')[0];
 ```
 
-Using semantic names like `profile-photo` makes it easy to locate and modify blocks when processing different data records.
+For each record, we create a new scene with the appropriate dimensions for our template design.
 
-## Add Text with Variables
+## Set Variable Values
 
-Text variables use double curly brace syntax: `{{variableName}}`. We create a text block with variable placeholders for name, title, and email.
+We use `engine.variable.setString()` to define the value for each variable. When a variable is set, all text blocks referencing that variable update automatically.
 
-```typescript highlight=highlight-create-text-with-variables
-// Create a text block with variable placeholders
-const textBlock = engine.block.create('text');
-const textContent = `{{name}}
-{{title}}
-{{email}}`;
-engine.block.replaceText(textBlock, textContent);
-engine.block.setWidthMode(textBlock, 'Auto');
-engine.block.setHeightMode(textBlock, 'Auto');
-engine.block.setFloat(textBlock, 'text/fontSize', 32);
-engine.block.setPositionX(textBlock, 230);
-engine.block.setPositionY(textBlock, 140);
-engine.block.appendChild(page, textBlock);
+```typescript highlight=highlight-set-variables
+// Set text variables from the data record
+engine.variable.setString('name', record.name);
+engine.variable.setString('title', record.title);
+engine.variable.setString('email', record.email);
 ```
 
-Variables in text blocks automatically display their values when set through the Variable API.
+Variable values persist within the current scene. Creating a new scene clears previous variable bindings.
 
-## Set Variable Values
+## Build the Template
 
-We use `engine.variable.setString()` to define the value for each variable. When a variable is set, all text blocks referencing that variable update automatically.
+We create the template layout with placeholder blocks. The profile photo block gets a semantic name using `setName()`. Text blocks use variable placeholders with double curly brace syntax: `{{variableName}}`.
 
-```typescript highlight=highlight-set-variables
-// Set the variable values from data
-engine.variable.setString('name', sampleData.name);
-engine.variable.setString('title', sampleData.title);
-engine.variable.setString('email', sampleData.email);
+```typescript highlight=highlight-create-template
+    // Create the template layout with placeholder blocks
+
+    // Create a profile photo block on the left
+    const photoBlock = engine.block.create('graphic');
+    engine.block.setShape(photoBlock, engine.block.createShape('rect'));
+    const photoFill = engine.block.createFill('image');
+    engine.block.setString(
+      photoFill,
+      'fill/image/imageFileURI',
+      record.photoUrl
+    );
+    engine.block.setFill(photoBlock, photoFill);
+    engine.block.setWidth(photoBlock, 150);
+    engine.block.setHeight(photoBlock, 150);
+    engine.block.setPositionX(photoBlock, 50);
+    engine.block.setPositionY(photoBlock, 125);
+    engine.block.setName(photoBlock, 'profile-photo');
+    engine.block.appendChild(page, photoBlock);
+
+    // Create a text block with variable bindings
+    const textBlock = engine.block.create('text');
+    const textContent = `{{name}}
+{{title}}
+{{email}}`;
+    engine.block.replaceText(textBlock, textContent);
+    engine.block.setWidthMode(textBlock, 'Auto');
+    engine.block.setHeightMode(textBlock, 'Auto');
+    engine.block.setFloat(textBlock, 'text/fontSize', 32);
+    engine.block.setPositionX(textBlock, 230);
+    engine.block.setPositionY(textBlock, 140);
+    engine.block.appendChild(page, textBlock);
 ```
 
-Variable values persist throughout the engine session. Setting a variable to a new value updates all references immediately.
+Using semantic names and variables makes templates reusable across different data records.
 
-## Discover Variables
+## Verify Variables
 
 Use `engine.variable.findAll()` to discover which variables exist in the scene. Use `engine.block.referencesAnyVariables()` to check if a specific block contains variable references.
 
-```typescript highlight=highlight-discover-variables
-// Discover all variables in the scene
-const variables = engine.variable.findAll();
-console.log('Variables in scene:', variables);
+```typescript highlight=highlight-check-variables
+    // Verify which variables exist in the scene
+    const variables = engine.variable.findAll();
+    // eslint-disable-next-line no-console
+    console.log(`Processing ${record.name}, variables:`, variables);
 
-// Check if the text block references any variables
-const hasVariables = engine.block.referencesAnyVariables(textBlock);
-console.log('Text block has variables:', hasVariables);
+    // Check if the text block references any variables
+    const hasVariables = engine.block.referencesAnyVariables(textBlock);
+    // eslint-disable-next-line no-console
+    console.log(`Text block has variables: ${hasVariables}`);
 ```
 
-This is useful when loading existing templates to determine which data fields are required.
+This is useful for validating that data fields match template requirements before processing.
 
-## Find and Update Placeholder Blocks
+## Export Each Design
 
-Use `engine.block.findByName()` to locate blocks by their semantic name. Once found, you can update properties like image content by modifying the fill URI.
+After merging data into the template, export the personalized design using `engine.block.export()`. We save each result to the file system with a unique filename.
 
-```typescript highlight=highlight-find-by-name
-// Find blocks by their semantic name
-const [foundPhotoBlock] = engine.block.findByName('profile-photo');
-if (foundPhotoBlock) {
-  console.log('Found profile-photo block:', foundPhotoBlock);
+```typescript highlight=highlight-export
+    // Export the personalized design to PNG
+    const blob = await engine.block.export(page, { mimeType: 'image/png' });
 
-  // Update the image content
-  const fill = engine.block.getFill(foundPhotoBlock);
-  engine.block.setString(
-    fill,
-    'fill/image/imageFileURI',
-    'https://img.ly/static/ubq_samples/sample_2.jpg'
-  );
-}
-```
+    // Save the result
+    const filename = record.name.toLowerCase().replace(/\s+/g, '-');
+    const buffer = Buffer.from(await blob.arrayBuffer());
+    writeFileSync(`${outputDir}/${filename}.png`, buffer);
 
-This pattern works well for updating profile photos, logos, or other image placeholders in templates.
+    outputs.push({ name: record.name, blob });
+    // eslint-disable-next-line no-console
+    console.log(`✓ Exported ${filename}.png`);
+```
 
-## Export the Design
+You can export to PNG, JPEG, WebP, or PDF formats. For high-volume processing, consider writing to cloud storage or a CDN.
 
-After merging data into the template, export the personalized design using `engine.block.export()`.
+## Cleanup Resources
 
-```typescript highlight=highlight-export
-// Export the personalized design
-const blob = await engine.block.export(page, { mimeType: 'image/png' });
-console.log('Exported PNG blob:', blob.size, 'bytes');
+Always dispose of the engine when batch processing completes. Using a `finally` block ensures cleanup happens even if an error occurs during processing.
 
-// Create a download link for the exported image
-const url = URL.createObjectURL(blob);
-console.log('Download URL created:', url);
+```typescript highlight=highlight-cleanup
+// Always dispose the engine to free resources
+engine.dispose();
 ```
 
-You can export to PNG, JPEG, WebP, or PDF formats. For batch processing, collect blobs in an array or write directly to a file system.
+This frees memory and other resources held by the engine instance.
 
 ## Troubleshooting
 
 ### Variables Not Rendering
 
-If variable placeholders show instead of values:
+If variable placeholders show instead of values in exported images:
 
 - Verify the variable name matches exactly (case-sensitive)
 - Use `engine.variable.findAll()` to check which variables are defined
-- Ensure `engine.variable.setString()` was called before rendering
+- Ensure `engine.variable.setString()` was called before export
+- Create a new scene for each record to avoid stale variable state
 
-### Block Not Found
+### Export Failures
 
-If `findByName()` returns an empty array:
+If exports fail for individual records:
 
-- Check the block name was set with `engine.block.setName()`
-- Verify the name string matches exactly (case-sensitive)
-- Ensure the block exists in the current scene
+- Wrap the export call in a try-catch to handle errors gracefully
+- Log the record data to identify problematic inputs
+- Verify image URLs in data records are accessible from the server
+- Check that the page block exists after scene creation
 
-### Image Not Updating
+### Memory Issues
 
-If placeholder images don't update:
+If processing many records causes memory issues:
 
-- Get the fill block first with `engine.block.getFill()`
-- Use the correct property path: `fill/image/imageFileURI`
-- Verify the image URL is accessible and valid
+- Dispose and recreate the engine periodically for very large batches
+- Process records in smaller chunks
+- Monitor memory usage during batch operations
 
 ## API Reference
 
-| Method                                           | Description                                 |
-| ------------------------------------------------ | ------------------------------------------- |
-| `engine.variable.setString(name, value)`         | Set a text variable's value                 |
-| `engine.variable.getString(name)`                | Get a text variable's value                 |
-| `engine.variable.findAll()`                      | List all variable names in the scene        |
-| `engine.variable.remove(name)`                   | Remove a variable                           |
-| `engine.block.findByName(name)`                  | Find blocks by their semantic name          |
-| `engine.block.setName(block, name)`              | Set a block's semantic name                 |
-| `engine.block.replaceText(block, text)`          | Replace text content in a text block        |
-| `engine.block.referencesAnyVariables(block)`     | Check if block contains variable references |
-| `engine.block.getFill(block)`                    | Get the fill block of a design block        |
-| `engine.block.setString(block, property, value)` | Set a string property value                 |
-| `engine.block.export(block, options)`            | Export a block to an image format           |
+| Method | Description |
+|--------|-------------|
+| `engine.variable.setString(name, value)` | Set a text variable's value |
+| `engine.variable.getString(name)` | Get a text variable's value |
+| `engine.variable.findAll()` | List all variable names in the scene |
+| `engine.variable.remove(name)` | Remove a variable |
+| `engine.block.findByName(name)` | Find blocks by their semantic name |
+| `engine.block.findByType(type)` | Find blocks by their type |
+| `engine.block.setName(block, name)` | Set a block's semantic name |
+| `engine.block.replaceText(block, text)` | Replace text content in a text block |
+| `engine.block.referencesAnyVariables(block)` | Check if block contains variable references |
+| `engine.block.getFill(block)` | Get the fill block of a design block |
+| `engine.block.setFill(block, fill)` | Set the fill block of a design block |
+| `engine.block.setString(block, property, value)` | Set a string property value |
+| `engine.block.export(block, options)` | Export a block to an image format |
+| `engine.scene.create(layout, options)` | Create a new scene with specified layout |
+| `engine.dispose()` | Dispose the engine and free resources |
+
+
 
 ---
 
 ## 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