Unify .md & .mdx implementations #2869
jamespohalloran
started this conversation in
Ideas
Replies: 3 comments
-
@jamespohalloran I am currently facing this issue, How to get the raw string from the rich-text to use my own markdown plugin I dont want to use the Tina-Markdown Component. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Similarly, I would love to be able to mix .md and .mdx files, since the .md files are edited with an external editor (Ulysses) that can't handle .mdx extensions. |
Beta Was this translation helpful? Give feedback.
0 replies
-
This seems to generate the original markdown. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently in our docs, we have separate approaches for implementing markdown or mdx content.
For the Markdown approach, implementation is as follows:
react-tinacms-editor
cms.plugins.add(field.MarkdownFieldPlugin)
React-Markdown
(or somthing similar)For the MDX approach:
TinaMarkdown
componentThe
react-tinacms-editor
editor also uses prosemirror, while the default rich-text editor uses slate.Problems:
Should we unify the
.md
&.mdx
approaches?Should we deprecate the markdown approach, and instead encourage users use
rich-text
for the body on allbody
fields?templates
wouldn't be supported (I assume).TinaMarkdown
component as-is. Could we provide a utility for getting the raw markdown string from the response so that a user could use their existing React-Markdown plugin?Beta Was this translation helpful? Give feedback.
All reactions