When can we expect Markdown formatting to work in Elements?
We have no plans to integrate it directly into the WYSIWYG editor as this would break the loo and feel. However if you need to use Markdown in certain areas, you can use the CMS for single pieces of content. Perhaps this would work for you.
Doesn’t work particularly well in the CMS either. Lists and line breaks.
You could on a doubleclick in the displayed Markdown open a window with the actual Markdown.
Could you please explain how Markdown would disrupt the look and feel of Elements?
We’ve worked REALLY hard to keep the editor WYSIWYG, if we allow raw markdown in the editor it’s suddenly not WYSIWYG anymore. You’d have to start flipping back and forth between edit and preview all the time to see if it’s how you want it to look. That is a terrible way to design, if you want to work that way you can go back to Classic and Stacks 
However… we could do a separate area where you edit the raw markdown (the same way we do custom components), and we may end up doing that, but first, we have A LOT of other more important work to do… like improving the Typography area and our CMS markdown rendering…
2 Likes
I think this is extremely shortsighted as in this day and age there is nothing stopping you from having and option to “hide” the markdown so that it displays as it would in Preview. There are plenty of markdown editors that support something like, like Bear, and it works really well and is WYSYWIG.
I still have not seen any info on how you plan to fully support Markdown in the typography component. Maybe once I have a clear understanding of the plan for it I might change my opinion.
I’m not sure why you would encourage me to go back to Classic, seems you have been trying hard lately to do the opposite!
When will we finally see something on this front. It has been talked about a lot but there has been no movement on improving the typography component, and it really needs it.
1 Like
probably not until the marketplace is finished and fully working. with some luck and patience, maybe by christmas …
It’s still on the list, but we’ve had to prioritise the Elements Store.
Once we’ve got the store up and running, you should see more of these features/enhancements being added to the main app 
Fwiw, I agree with focusing on Typography and the CMS markdown rendering. I say that because the site I just built is 95% CMS content (the dream/goal is to move editing that content out of Elements so my team members can edit …. others probably have similar needs for clients).
Yes, that’s exactly the long-term plan for the CMS 
We want to make it so content can be fully managed outside of Elements, letting team members or clients edit text, images, and posts directly, without needing to open the project. It’ll make collaborative workflows much smoother and allow Elements to stay focused purely on design and structure!
1 Like