Medium migration flow about matters-server HOT 3 CLOSED

I think we only need to upload real posts, and no need to include comments. In addition, uploading the packed files should be more user-friendly...

from matters-server.

Great summary!

I think the core functionality as well as the PoC should be allowing user to upload multiple html files and turns them into drafts. So that it is general and robust, instead of medium.com specific and messy. If we need to simplify user interaction, we can think of a solution on top of this, preferably on the frontend.

In my opinion, picking html files instead of uploading the same pack is not that much of a burden if the user really needs this functionality, especially when html files are easily previewed everywhere. We can frame this feature as a general html upload functionality, and medium.com specific instruction can live in landing page.

If we go with this design, I think we should be able to skip intermediary storage (s3 or postgres) entirely, and just hold the html string in queue, process it, then write to draft table.

There's one small issue with design though,

editor has an upload button on the right sidebar.

if we allow multiple file upload, logically the upload entrance should be in draft page, as we discussed before. What do you think @gyuetong ?

from matters-server.

We've shipped the feature. Close it.

from matters-server.