Hey @bixfrankonis – I tested it, and I see the markdowns are getting exported in HTML. I think that is how it works, but let me check once with the team for confirmation on how it works in behind. We will get back to you as soon as we have some info to share.
Hi there – I appreciate your patience in waiting for a response. I’m now here to clarify how we manage Markdown content.
As you’ve rightly observed, when content is exported, it is indeed generated in HTML format. This HTML version is saved in the post_content column of our database. The reason behind this is to ensure that even if someone chooses to discontinue the use of Jetpack, their content formatting will remain intact, and it will continue to display properly in its intended format.
However, we understand the importance of preserving the original Markdown content. For this purpose, we also save a copy of the raw Markdown in a separate column in the posts table called post_content_filtered. This means that if users ever need to access the Markdown version of their content, they can retrieve it from there. It’s stored as a safeguard, ensuring that both the HTML and Markdown representations are available for future use.
If you have any further questions or if there’s anything specific you’d like to know about this process or any other aspect of our system, please feel free to ask. We’re here to help and ensure that your experience with our platform is as smooth as possible!
Thread Starter
Anonymous User 17976131
(@anonymized-17976131)
Ah, thanks! Out of curiosity, is that how, if you have Markdown for Classic Editor enabled, when you go to edit an existing post you wrote that way, it brings up the Markdown, not the HTML? It’s checking for something in post_content_filtered first?
-
This reply was modified 2 years, 7 months ago by
Anonymous User 17976131.
Hi there – yes, if you have Jetpack installed, then it will bring Markdown first, and if you have Jetpack not installed, it will switch to HTML so that your content doesn’t break.
