Yes, all my content is currently stored as HTML. I assume Nostr requires plain text content?
As I was building cross-posting long-form content (NIP-23) to Nostr from a Drupal CMS, I was not able to find a good WYSIWYG rich text editor which outputs Markdown formatted content. CKEditor version 5 is shipped in the latest versions of Drupal which formats your text to HTML. I found the markdown_output plugin in the very rich ecosystem of CKEditor. A plugin that provides me the solution I was looking for.
It was not easy to get it to use within Drupal, but doing hard things is often more rewarding than doing a lot of easy things.
Last week I released the first beta release of the module called CKEditor5_Markdown_Editor for Drupal. With this module you can enable the Markdown output plugin in the settings of your text formatter.
The result is quite simple as you can see here:
.gif
The module: https://www.drupal.org/project/ckeditor5_markdown_editor
nostr:npub176xpl3dl0agjt7vjeccw6v5grlx8f9mhc75aazwvvqfjvq5al8uszj5asu this raises a questionmark how to cross-post your blog content to Nostr as I assume your content if formatted in HTML 🤔
#Drupal #CKEditor5 #Markdown #NIP23
Discussion
Notes (kind 1) are plain text indeed
Long-form content (kind 30023) supports Markdown, see https://github.com/nostr-protocol/nips/blob/master/23.md and that’s what I’m referring to for crossposting blog posts for example (with also other fields like an image, summary and title)