Skip to content

Finalize post publishing/draft process #52

@begedin

Description

@begedin

For new posts

  1. User starts typing
  2. Periodically, the post is saved to the API as draft
  3. API transforms markdown into html, sets it to post body, returns post with body filled in
  4. Ember can show preview using body field in separate tab/pane
  5. Once user clicks publish, the final version of the post is saved in the published state

For edited post

  1. User clicks edit on existing post
  2. Periodically, the post is saved to the API as a separate draft
  3. API transforms markdown into html, sets it to post body, returns post with body filled in
  4. Ember can show preview using body field in separate tab/pane
  5. Once user clicks publish, the original version of the post has changes saved.

Questions

  1. What does the API do with the drafts once publish is done - might require issue on API side.
  2. How does the API figure out which original post the draft of an edit belongs to? It could be doable by identifying via number, but I'm not sure. There is no unique index on the number field at the moment, so it is possible.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions