Add markdown-to-rich-text extension

[vegetablesB]

Description

Screencast

Checklist

• [x] I read the extension guidelines
• [x] I read the documentation about publishing
• [x] I ran npm run build and tested this distribution build in Raycast
• [x] I checked that files in the assets folder are used by the extension itself
• [x] I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Congratulations on your new Raycast extension! :rocket:

We're currently experiencing high demand and limited capacity. As a result, extension reviews might take longer than usual to get the initial review. Please expect an initial review within 5-10 business days.

Once the PR is approved and merged, the extension will be available on our Store.

Sorry for the inconvenience

[koinzhang]

Looks similar to these two https://www.raycast.com/aravindballa/markdown-this https://www.raycast.com/skyline-123/markdown-to-plain-text

[vegetablesB]

Looks similar to these two https://www.raycast.com/aravindballa/markdown-this https://www.raycast.com/skyline-123/markdown-to-plain-text

The result is different. For markdown text:

# Welcome to StackEdit!
[raycast](https://www.raycast.com/)

The result is:

[mil3na]

Hi! Thank you for your contribution! My name is Milena and I will be reviewing it today.

As said before, this extension does something very similar to pre-existing ones. Maybe you could improve one of the existing ones with the content of your extension. I believe there is no need for multiple extensions to manipulate markdown.

[vegetablesB]

Hi!

Thank you for your contribution! My name is Milena and I will be reviewing it today.

As said before, this extension does something very similar to pre-existing ones. Maybe you could improve one of the existing ones with the content of your extension. I believe there is no need for multiple extensions to manipulate markdown.

Hi Milena,

Thank you for your feedback and for reviewing my PR.

I understand the concern about having multiple extensions that seem to handle Markdown in similar ways. However, my "Markdown to Rich Text" extension is different from the existing ones, and I’d like to explain how:

Key Differences

1. Output Format:

   • Markdown to HTML: Converts Markdown into HTML code, useful for web development and content management.
   • Markdown to Plain Text: Strips Markdown formatting, providing plain text without any styling.
   • Markdown to Rich Text: Converts Markdown into styled text that retains formatting like bold, italics, headings, and lists. This can be directly pasted into applications that support rich text, such as word processors or email clients.

2. Use Cases:

   • HTML: Ideal for developers or those working with web content.
   • Plain Text: Suitable for those needing unformatted, clean text.
   • Rich Text: Perfect for users who need formatted text for documents, presentations, or emails, keeping the visual style without needing HTML or losing the formatting.

3. User Experience:

   • Each extension serves different needs. "Markdown to Rich Text" provides an option for users who want their Markdown content converted into a format that maintains styling and can be pasted directly into rich text fields.

Reason for Development

I created this extension because I couldn't find any existing tool that converted Markdown directly to Rich Text. I believe it fills a gap by offering a straightforward way to maintain the visual formatting of Markdown content in a rich text format.

I hope this explanation clarifies the unique value of the "Markdown to Rich Text" extension. It aims to make life easier for users who need this specific functionality. I look forward to any further feedback you might have.

[mil3na]

Thank you for your explanation. I decided to give it a chance for seeing how different these extensions are, however, I'm confused about the usage. Using the command directly pastes the content of my clipboard on my frontmost app. No preview, no option to chose if I want it on my clipboard or pasted. The action panel still says that the main action is "Open Command" and nothing else.

In order to make it happen to the Store, I would need this extension to be more clear on what is doing and giving me the options you promised on the README. Let me know if you need any help.

[vegetablesB]

Thank you for your explanation. I decided to give it a chance for seeing how different these extensions are, however, I'm confused about the usage. Using the command directly pastes the content of my clipboard on my frontmost app. No preview, no option to chose if I want it on my clipboard or pasted. The action panel still says that the main action is "Open Command" and nothing else.

In order to make it happen to the Store, I would need this extension to be more clear on what is doing and giving me the options you promised on the README. Let me know if you need any help.

Hi Milena,

Thank you for your detailed feedback.

I understand there was some confusion about the usage. The "Markdown to Rich Text" extension is designed to streamline the process by automatically converting Markdown text and pasting it directly into the current application. This approach is intended to save time and effort for users who need quick formatting, without additional steps or options.

I have updated the README to make this functionality clearer. And updated the shotHUD message to ensure users know what to expect. If you have any suggestions on how to further improve the user experience or if there's anything specific you think should be added, please let me know.

Thank you for your support!

Here is a short video for usage:

https://github.com/raycast/extensions/assets/44360183/79f0df54-7be2-43f3-8393-a39d33faac44

[mil3na]

Thanks for the video. My last suggestion would be to rename the command to the actual action that it does: Convert Clipboard To Rich Text. That way, it is clear to the user that the input is the clipboard and it will be converted. Then, after the action is successful, the HUD will make clear where the output is. What do you think?

[vegetablesB]

Convert Clipboard To Rich Text

Hi,

Thanks for your feedback! I agree, your suggestion to rename the command to "Convert Clipboard To Rich Text" does make more sense. It clearly conveys the function of the command.

I've updated the package.json to reflect that change and also adjusted the showHUD message to be more informative.

Command name change

showHUD Message

[raycastbot]

This pull request has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊

[github-actions[bot]]

Published to the Raycast Store: https://raycast.com/ning_cao_cabeza/markdown-to-rich-text

[raycastbot]

:tada: :tada: :tada:

Such a great contribution deserves a reward, but unfortunately we couldn't find your Raycast account based on your GitHub username (@vegetablesB). Please link your GitHub account to your Raycast account to receive your credits and soon be able to exchange them for some swag.