Add backend API for design persistence #4

Closed
opened 2026-06-22 14:58:57 +00:00 by Mark · 2 comments
Owner

All design data is in-memory or localStorage. For production:

  • REST API for design CRUD
  • User authentication
  • Cloud storage for PES files and thumbnails
  • Export history

Decision needed: Node/Express, Python/FastAPI, or serverless?

All design data is in-memory or localStorage. For production: - REST API for design CRUD - User authentication - Cloud storage for PES files and thumbnails - Export history Decision needed: Node/Express, Python/FastAPI, or serverless?
Author
Owner

Auto-triage: needs decompose

Marked triage-approved + needs-decompose. decompose-executor will pick this up and break it into implementable sub-issues.

## Auto-triage: needs decompose Marked `triage-approved` + `needs-decompose`. decompose-executor will pick this up and break it into implementable sub-issues.
Author
Owner

Auto-triage: needs decompose

Marked triage-approved + needs-decompose. decompose-executor will pick this up and break it into implementable sub-issues.

## Auto-triage: needs decompose Marked `triage-approved` + `needs-decompose`. decompose-executor will pick this up and break it into implementable sub-issues.
Mark 2026-06-27 05:46:03 +00:00
Sign in to join this conversation.
No description provided.