acc currently pulls/pushes configuration from/to Adobe Campaign with local source files. The roadmap covers how it will evolve into a complete development interface.

Planned features include bidirectional sync (acc instance push) and a VS Code extension for first-class IDE support. Hot reload (acc instance watch) is available in early access.

Roadmap

The overall direction is to evolve the CLI from a pull-oriented extraction tool into a complete development interface for Adobe Campaign:

  • local-first workflow
  • bidirectional sync
  • scriptable and CI-friendly operations

Deployment & Synchronization

  • acc instance push
    • Enable deployment of local metadata to Adobe Campaign instances. Comparable to sf project deploy start, with support for:
      • selective deployment
      • diff-based updates
      • safe overwrite strategies
  • acc instance watch => AVAILABLE in 1.6.4 (early access, test in a sandbox first)
    • Continuous synchronization between local files and the remote instance. Inspired by shopify theme dev, with:
      • file system watchers
      • incremental updates
      • near real-time feedback loop
    • Limits today: only the files configured with decompose are watched, and only text values are pushed (XML elements with child elements are skipped with a warning)
  • Pre-deployment validation => AVAILABLE in 1.7.3
    • Validate configuration and metadata before push:
      • schema validation (AJV)
      • structural consistency checks
      • early failure detection

Developer Experience

  • VS Code extension
    • Provide first-class IDE integration:
      • command palette integration
      • inline validation feedback
      • configuration editing support
      • improved navigation of Campaign artifacts

SDK Coverage & Feature Parity

  • Extended acc-js-sdk integration
    • Expose a broader surface of SDK capabilities directly in the CLI:
      • package import/export
      • file upload/download
      • instance-level operations
      • automation-friendly commands