Spike: How do we publish a content in the future?

[nollymar]

Parent Issue

No response

Task

During the implementation of the new FTM, a doubt came up: what are the right steps to publish a piece of content in the future? Consider these two scenarios:

Scenario 1:

• Create a piece of content without setting a future publish date and click Save
• Edit the piece of content and set a publish date in the future. Click Publish. If you go to the History Tab, it should have two versions and the most recent in working state.

Scenario 2:

• Create a piece of content setting a future publish date and click Save. If you go to the History Tab, it should have only one version and its state should be working.

Questions to answer on this spike:

1. How our current check-in logic handles both scenarios? Should both scenarios be published in the future?
2. Do we have a way to differentiate Scenario 1 (saved with the Publish button) from 2 (saved with the Save button)?
3. According to the logic, what are the only steps required to show a piece of content in the future? Is the working/live history relevant?

The results gathered from this research will help us make a decision about the expected behavior of the new FTM.

Proposed Objective

Same as Parent Issue

Proposed Priority

Priority 2 - Important

Acceptance Criteria

The expected output from this research is the answer obtained from the 3 questions listed above.

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[nollymar]

Agreement:
The decision about when a piece of content will be published will only depend on the publish date set. The Save and Publish buttons should behave exactly the same way in Future Time Machine. The previous content history shouldn't affect this behavior.