Declined Suggested 12/2/2021 by Dennis Branscombe
19
votesMarkdown Support
While it'd be nice to have markdown support throughout the system as a whole, I think immediate benefits could be seen in just the knowledge base.
Alex
1/28/2023 11:02 AM
Tech
We'd love more ideas on how you see it. A system-wite setting "enable markdown"? A switch in the WYSIWYG editor?
fa
3/27/2024 12:42 PM
A switch in the WYSIWYG editor would be fantastic
cc
7/22/2024 7:19 PM
Markdown is the most well-supported standard for documentation markup and it's widely used across many different IT and CS domains. It would immediately make it easier to import notes from other projects using it.
Both the ticketing system and the knowledge base would benefit from this. I'd personally prefer a solution that defaulted all text input to Markdown, as the existing WYSIWYG system sometimes performs strangely when working with tabs and bullet points. Additionally, writing is more fluid when working with a basic markup script instead of having to click on buttons every time I want to add a new button. With Markdown, there's no need to worry about the behavior of the WYSIWYG interface from the user perspective, as Jitbit would just need to render Markdown as HTML. That said, it would be helpful to produce a "display" view of the rendered text before sending/saving text.
Off the top of my head, I can imagine that some features, like masking, might be annoying to support in Jitbit with Markdown. These could be potentially mitigated by adopting angled brackets to mark features that need to be parsed separately from the Markdown text.
Both the ticketing system and the knowledge base would benefit from this. I'd personally prefer a solution that defaulted all text input to Markdown, as the existing WYSIWYG system sometimes performs strangely when working with tabs and bullet points. Additionally, writing is more fluid when working with a basic markup script instead of having to click on buttons every time I want to add a new button. With Markdown, there's no need to worry about the behavior of the WYSIWYG interface from the user perspective, as Jitbit would just need to render Markdown as HTML. That said, it would be helpful to produce a "display" view of the rendered text before sending/saving text.
Off the top of my head, I can imagine that some features, like masking, might be annoying to support in Jitbit with Markdown. These could be potentially mitigated by adopting angled brackets to mark features that need to be parsed separately from the Markdown text.
fa
7/24/2024 2:21 PM
Would it be possible to revisit this, Alex?
Martijn Korbee
9/6/2024 10:21 AM
+1 for markdown support
Log in to comment...