shortcodes kept in resultant markdown - is it possible?

[cp-bwg]

Hi there - I am using this to generate md (ultimately mdx) files for my posts for use in migrating over to astro. I want to keep the shortcodes in the content in their place in the markdown. I know that some plugins give some nasty content that is hard to parse, but I have my own shortcodes that I would like to retain as acorn notation, or the actual full shortcode output into the resultant markdown, so we can post process to map those into components.

for example, when this is found in the content:

<!-- wp:shortcode -->
[sc name="usage-based-pricing-video"]
<!-- /wp:shortcode -->

we'd like

[sc name="usage-based-pricing-video"]

to remain in the markdown your code generates.

Possible with flags or params?

[lonekorean]

Possibly related to this issue. Sounds like there's a more general need to preserve square brackets.

Also the mention about "ultimately mdx" sounds like a +1 for a .mdx flag.

I'll try to look into these soon!

[Lewiscowles1986]

Hi 👋 I helped make a plugin for WordPress that renders shortcodes, along with some of the core contributors when Gutenberg was being released in 2017 and I maintained it for a while later.

https://github.com/CODESIGN2/gutenberg-shortcode-preview-block is where the latest version lived. The most important parts for this would be having a site url, or a rest api url. Then you could just take the backend and have it render the HTML (ugly AF) and try to markdown-ify what you can of that.

Personally I became way less interested in the project once I realised that shortcodes are so dynamic, that they dont really fit into anything outside of an iframe.

Some control scripts, add styling, which may conflict with your own styling, and others use dynamic code to perform actions, which by their nature are not cleanly convertable to static content.

Even given all this, I wanted to see if this project has approached shortcodes, and offer a link in-case it's helpful at all for how to get the HTML out of them.