A few questions about this plugin

Hello Thomas,

I found this very interesting plugin

Thank you. If you like this plugin please remember to rate it in the Reviews section. This helps the plugin downloads and its future development.

Would it be possible for you to export earlier posts/pages etc. to Markdown documents? That would save folks like me a ton of time, because I had to change plugin for my Markdown-work and as a result all content is now in raw HTML.

This is definitely possible and I have added a ticket for this.

How do I easily update a published post and the document, if I at some point need to edit a post that I loaded via a document? Should I update both document and post or just the document to get it all updated?

The correct method (to keep in sync the two versions of the article) is to update the document from the Documents menu, edit the corresponding post, and then load the updated document by using the Load Markdown section.

If using the “Submit Markdown” option when creating a new post, will this text automatically be saved as a document?

No, the Submit Markdown section adds in the edited post the Gutenberg blocks generated from the provided Markdown text.

Are there plans for incorporating the different parsers like those in the import markdown plugin, so there can be changed Markdown variant via the options?

Yes, this is possible. I added a ticket for this.

Please that at the moment I can’t guarantee about the implementation of these features or provide you a release date. A Pro version of this plugin is also in development and some of these feature may be added in the Pro version.

Let me know if you have other questions.

• This reply was modified 2 years, 11 months ago by DAEXT.

Hi @daext t

Thanks for your quick reply.

daext wrote:
No, the Submit Markdown section adds in the edited post the Gutenberg blocks generated from the provided Markdown text.

Ok, I get that, it would be great if the plugin did one of two things:
1. If the user entered text via the submit-box this text could be stored with the post. by doing so it would be very easy to update the post without loading documents into the post editor, and this could speed up the workflow for me and other people. It would also be nice if the converted content from the block editor could show up somewhere inside the post screen.
2. If the first suggestion is impossible, I would suggest creating a document when the submit button is clicked, and the title should then be the post_title. That might help users like me who work exclusive in Markdown.

I get the idea behind the document structure, but it would be really nice if these things could come together some more. I do almost all my work in Markdown, so this plugin looks very promising. I will for sure follow the updates and test it.

Another note:
For the documentation it would be great to have a FAQ or some documentation on your official website, just so questions like mine could be answered from that place. What does the options section do? Haven’t found any references to this anywhere.

Best regards Thomas

Hello Thomas,

thank you for all the details.

Best Regards.