Browse / Content & marketing / canva-template-workspace

canva-template-workspace

mukund-groovy

Portable, self-contained workflow folder for Canva template cloning.

Open mukund-groovy/canva-template-workspace → Checked against the four rules.

Built for Claude Code

ships .claude CLAUDE.md and nothing for other agents.

In its own words

README.mdmukund-groovy/canva-template-workspace

Portable, self-contained workflow folder for Canva template cloning.

Use this when you want any AI/tool/person to follow one consistent structure with no path guessing. All required clone engine scripts now live inside canva-template-workspace/scripts/canva/.

What You Need

  • editor-page.full.html from Canva editor (captured after load; one reload strategy recommended when rate-limited).
  • Design ID from Canva URL (/design/ DESIGN_ID /...).

If editor-page.full.html is truncated, keep editor-page.reconstructed.html in the same source folder; the runner auto-falls back to it.

Quick Start

One-Line Agent Command (Recommended)

Use this when you do not want to pass long options each time:

canva-template-workspace/agent.config.json

Staged Workflow Commands

If you want manual stage control from chat:

  • Add entry only (no clone yet):
  • Clone/extract only (downloads JSON/assets):
  • Generate only (from existing extracted data):
  • Full pipeline in one shot:
Dashboard

Every agent run auto-updates:

  • canva-template-workspace/dashboard.html

This single dashboard file shows all design entries with:

  • status (pending, cloning, cloned, generating, success, failed, duplicate)
  • source URL
  • input HTML path
  • weighted score/quality-gate result (global RMSE + edge-weighted RMSE)
  • output HTML path
  • workspace summary path
  • last error (if failed)

Quoting 42% of the README. Read the rest on GitHub ↗

Read from the repository's git tree on 2026-08-17.