863811 - [Meta] Separate save and publish actions in Webmaker tools

Status: RESOLVED WONTFIX

(Webmaker Graveyard :: General, defect)

Description

[Mike Beltzner [:beltzner, not reading bugmail]]

Bug 860364 requires support for a user flow in which content generated in Webmaker tools can be saved but not published. For details, see bug 860364 comment 14 

From bug 860364 comment 15 humph writes:

---------------
Save: we put your project data in a database, keyed on email.  That email may or may not be a Webmaker user.  We need to think about what our endpoints that depend on a Persona ID will do if you hit them without having a Persona paired to your email.

Publish: we take some project in the DB and push it to S3, doing any post-processing (i.e., sanitize HTML, etc).  Publishing always implies that you're a Webmaker user, and that we have a target sub-domain where this thing is going to live.
---------------

This meta will be used to track the bugs in the Popcorn Maker and Thimble components required to achieve this.

Comment 1

[Mike Beltzner [:beltzner, not reading bugmail]]

(changing blocking requirement)

Comment 2

[Mike Beltzner [:beltzner, not reading bugmail]]

Brett / Cassie: is this a blocker? I'm not sure where we landed on how tightly integrated save vs. publish is on our first time use case where someone tries to save something without having their Persona created yet.

Comment 4

[Pomax]

do we still want to do this? Otherwise we can close this ticket.

Comment 5

[Brett Gaylor [:brett]]

close it

Comment 6

[Mike Beltzner [:beltzner, not reading bugmail]]

WONTFIX for now, not a priority anymore.

Comment 7

[Jacob [:Jacob]]

Curious why this has been dropped.

I feel like this is an important function if we want users to start building personal pages that they are proud of instead of gallery littered with half baked drafts that become published every time you want to save your progress.