15. Import and export

ID	Requirement	P	Type	Ver.	M
EXP-1	Nodes shall export as images. PNG, JPG, WebP, SVG and PDF; multiple export settings per node with scale (0.5×–4× or fixed width/height) and suffix; batch export of all export settings on a page; “Export selection” dialog.	Must	functional	test	0.2
EXP-2	SVG export shall be clean. Options: outline text, include `id` attributes, simplify strokes, use absolute bounds; output is minimal and readable.	Must	functional	test	0.2
EXP-3	Pages shall export as multi-page PDF. Frames in order of position or flow, vector text with embedded subset fonts.	Should	functional	test	0.6
EXP-4	SVG and images shall import. Drop or paste SVG (to editable vectors, groups, gradients, text where possible), PNG, JPG, WebP, GIF (first frame), AVIF; multiple images placed in a row or as image fills of the selection.	Must	functional	test	0.2
EXP-5	Figma files shall import. Through the Figma REST API with a personal access token (stored in SecretStorage) given a file URL (reading `.fig` files is not in scope for 1.0, Appendix D issue 12). Nodes, components, variants, styles, variables, auto layout, images and prototype links; a report of what was approximated or skipped. Also `ud import figma`.	Should	functional	test	0.8
EXP-6	HTML pages shall import as designs. A URL or a running local page captured into frames with auto layout inferred from flex/grid, text with fonts, images and SVG; at chosen viewport widths. Uses the Browser DevTools sibling extension when installed, otherwise a headless Chromium found on the machine. Also `ud import html`.	Should	functional	test	0.8
EXP-7	Copy as code and copy as image shall exist. PNG, SVG, CSS, UDX and code snippets to the clipboard.	Should	functional	demonstration	0.2
EXP-8	Penpot and Sketch files could import.	Could	functional	test	backlog