Markdown for me not working tried many things - 2.2.2 update issue?

Tried both Markdown and HTML formatted .md files

tried paste as plain text

tried adding line breaks

not working

I tried to include here but article is too big


Can’t upload demo project either…

All since the update having issues…

Tried to restarting the computer

Checked registration

Uploaded the website six times didn’t work in any of the times

Uploaded to the cloud to share for people to use and see

Here is online link:

No headers
No line breaks

Tried to upload file to elements cloud - failed

From Gemini:

The culprit isn’t your text—it is the CSS styling engine (Tailwind CSS) that RapidWeaver Elements uses under the hood.

By default, Tailwind applies a “CSS Reset” to your entire website. This intentionally strips out all default browser spacing and sizing. It makes all headings (<h2>, <h3>) the exact same size as regular text, and it removes all the empty space between paragraphs (<p>). It does this so developers have a blank slate, but it makes raw blog posts look like a giant, unformatted wall of text.

To fix this, you need to tell Elements to apply “article styling” to that specific block of content.

Here is how to solve it:

  1. In the left-hand menu of Elements, look under your Pages structure and click on the Post layout page (this is the master template page that designs how your individual blog posts look, right above your CMS items).
  2. On that layout screen, select the component that is outputting your Markdown body content.
  3. Look at your Inspector/Settings panel on the right side of the screen. You are looking for a toggle or setting called Prose, Rich Text, or Typography. Enable it.
  4. Alternative: If Elements just gives you a field to type in a custom CSS class for that component, simply type the word prose into the class field.

The prose class is Tailwind’s magic command that instantly restores all the proper font sizes for headings, spacing for paragraphs, and styling for lists. Once you apply that to your content container on the layout page, your entire article will instantly pop into the correct formatting!

We’ve not had any other reports of this, and it appears to be working as expected here, so we’ll need a few more details to investigate further.

To help us resolve issues, please follow our how to get help guide.

In the meantime, you can also download previous builds here to see if the issue persists.


As a side note, AI-generated troubleshooting suggestions can sometimes be a bit off the mark. To help us diagnose things accurately, it’s best to stick to details from your own setup and what you’re seeing directly.

tried switching themes and entering line breaks

it is ‘working’ this second

no headers only bolded or italics

Question: does this only happen with newly created blog posts, or also with existing ones?

I couldn’t notice any changes with my existing blog posts.

Do you have any additional Tailwind typography plugins installed?

I think it’s a mess - for me - keep forgetting to make paste as plain text - but even then it doesn’t work for me - get a big block of text

Need to add line breaks

Don’t have any tailwind extensions

Out of curiosity, what are you using to create your .md files??

I research on iPhone often times and put snippets into notes

Then go edit on main computer - then copy and paste into a duplicated .md file

Which program do you do your editing with??

If you are generating these articles in AI then AI has a tendency to inject weird artifacts in its output. This could be causing issues when copying the AI generated text and pasting into a third-party text editor.

If the above is your workflow, perhaps try pasting in plain text in a text editor like BBEdit and then clean it up a bit to remove any weird AI artifacts, before trying to paste it into Elements.

See also: Markdown Editors

Thank you…

Hopefully fixed it:

Made a keyboard shortcut with: Paste as Plain Text

Command + V

Now - anytime I copy from notes or other it should strip away the rich text formatting… yes?