We're scoping out some ways we can make this happen and one of the things we're considering is adding a new "markdown" module field type. That way, if you wanted to write blog posts in markdown, you could add a markdown module as your blog content area.
I would love to hear your thoughts about whether this would be viable for your workflow!
Thank you as always for your continued feedback, it helps us build a great product.
We are constantly evaluating and re-evaluating our priorities and roadmap to deliver as much value to our customers as possible. The request for markdown support is an interesting one. Based on the comments and use cases you all have listed, we are reviewing this request and its feasibility among other priorities on our roadmap. At this time I don’t have any details around timing or delivery, but thanks to the comments and votes on this post we’re actively looking into what it would take to solve this problem.
Lack of markdown support in blog post is creating a massive barrier to entry for my organisation. Soon 4 years will have passed since this idea was first proposed, and seen from the outside, little has happened. Can you please share details that would prevent us from looking at competing services? Thanks.
Any progress on this? I am writing a blog currently with lots of equations and code and without markdown, it is incredibly tedious and borderline not worth it.
Thanks for continuing to upvote and comment on this idea! To provide an update, this is not currently planned, but it is a great idea, and I will continue to keep this idea updated as we are constantly re-evaluating and re-prioritizing feature updates.
Re-emphasizing the Need for Markdown Support in HubSpot
Hello HubSpot Team,
I'm writing to revive a request that has been previously submitted, but unfortunately, has not yet made it into the development pipeline:
Markdown support for blog content and rich-text fields within HubSpot.
Markdown is widely used by developers, technical writers, and content creators because of its simplicity and flexibility. It allows for a straightforward writing and editing experience, where the focus remains on the content rather than the formatting. While the rich-text editor is certainly useful for those unfamiliar with Markdown, there are a few significant reasons why including Markdown support would greatly enhance HubSpot's usability:
Efficiency: Markdown syntax is simple, straightforward, and quick to use. This reduces the time spent formatting, especially when compared to HTML or WYSIWYG interfaces.
Consistency: Markdown helps maintain uniformity in content presentation across different platforms. This is particularly important when incorporating code snippets, as Markdown ensures they are accurately represented and readable.
Compatibility: Markdown is a universal language that's supported by various platforms. Content written in Markdown can be easily transferred across different systems without losing its formatting.
Distraction-free writing: Markdown allows writers to focus on their content without being distracted by formatting buttons and options.
Proposal: I propose the addition of a switch button in the rich-text editors that allows users to write and preview content in Markdown. This would not only maintain the existing functionality for those who prefer the rich-text interface but also offer a much-needed tool for technical writers and content editors who prefer Markdown.
Thank you for considering this request. By incorporating Markdown support into HubSpot, we can cater to a wider user base, streamline the content creation process, and enhance the overall user experience.
As a content manager who was excited to have our company integrate Hubspot with our website, I have to say I am seriously disappointed to know I cannot use Markdown to write and format my blogs with Hubspot. What I thought was an upgrade is feeling like a downgrade.
You've been getting comments asking for blog markdown support for 6 years. Any more progress on this?
This would be excellent. Version control of HTML is a pain but Markdown is easy. To allow integration of Markdown would be a huge step forward. (As well as allowing us full HTML in our KB and anchors to begin with a number)
I'd be interested to understand the logic behind not supporting markdown. Makes me wonder if Hubspot will abandon this entire feature set and just focus on the CRM side. Not having markdown support is pretty aggregious.
