Skip to content

Deck export/import as a portable artifact #11

Description

@rlnorthcutt

Problem statement

A deck's contents currently aren't portable: there's no way to archive one, move it to another machine, or hand it to a client as a self-contained artifact.

What success looks like

A deck can be exported to a portable artifact and re-imported elsewhere, making "this is yours to keep" demonstrable rather than asserted.

Impacted repositories

  • omnideck

Acceptance criteria

  • A deck can be exported and re-imported on a different machine, preserving its contents.

Related

  • Extends the existing backup capability rather than building parallel infrastructure. Open question raised alongside this: could the same mechanism be used for syncing a deck between a user's own devices? Worth a design pass, not scoped into this epic yet.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    roadmapTier 1 item — triggers auto-add to the org project

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions