This is a Tina CMS project.
npx create-tina-app@latest- upgrade tinacms and cli to actual latest (3.6.x) in package.json
pnpm install- create one new MDX page per valid MDX that is lost or changed across loading into the editor and saving again.
- limit media manager to jpeg media type (to show that usupported file types stay browseable in the media manager)
This is a list of issues we have found. Each issue has a dedicated page that reproduces it. We consulted the supported markdown spec docs, topics that are related to those documented limitations should be under "minor issues"
Broadly, not being able to edit certain elements is not a problem but losing or breaking them is. Nested block level elements seem to be the unsupported pattern, which something we can live with - but also here it would be better if the editor retained them if not touched vs. resetting / removing. E.g. Nested Block quotes are nice to have but not a big deal.
In our body of content, the following issues can corrupt content / lose data:
- Curly Brace Escaping Lost (writes corrupt files)
- HTML Code Blocks have the wrong language tag "htmlbars"
- Code Block Infostring Lost after first space - falls under "if you can't edit it at least retain it. This one is a real issue for us.
- MDX Comments to be able to use vale linter annotations. MDX expressions are unsupported and comments are technically spoken expressions in MDX. So parser wise it could be a dead end. We'd either have to hack a comment component or Tina would move to retaining expressions across load->save but continue to not evaluating them. The latter would generally be very useful!