Current Problem:
Users currently find it difficult to apply Markdown formatting (like bold, italics, etc.) because there are no direct keyboard shortcuts to toggle these styles. This reduces productivity and makes the editing process slower, especially for users who rely on keyboard navigation.
Proposed Solution:
Implement keyboard shortcuts to directly toggle Markdown rich text formats. Specifically requested shortcuts include:
Command + B (or Ctrl + B on Windows/Linux) → Toggle bold
Command + I (or Ctrl + I on Windows/Linux) → Toggle italics
Additional shortcuts for other common Markdown elements (e.g., headers, lists, code blocks, links)
Benefits:
- Faster content creation
- Improved user experience for power users
- Better alignment with standard text editor behavior
- Reduced reliance on manual Markdown syntax typing
Example Use Case:
A user typing a documentation file can press Cmd+B to instantly wrap selected text in bold without manually typing the asterisks or switching to a toolbar.
Suggested Implementation:
- Detect selected text and wrap it with the appropriate Markdown syntax
- Allow users to customize or disable shortcuts if needed
- Ensure compatibility across platforms (macOS, Windows, Linux)
Current Problem:
Users currently find it difficult to apply Markdown formatting (like bold, italics, etc.) because there are no direct keyboard shortcuts to toggle these styles. This reduces productivity and makes the editing process slower, especially for users who rely on keyboard navigation.
Proposed Solution:
Implement keyboard shortcuts to directly toggle Markdown rich text formats. Specifically requested shortcuts include:
Command + B(orCtrl + Bon Windows/Linux) → Toggle boldCommand + I(orCtrl + Ion Windows/Linux) → Toggle italicsAdditional shortcuts for other common Markdown elements (e.g., headers, lists, code blocks, links)
Benefits:
Example Use Case:
A user typing a documentation file can press
Cmd+Bto instantly wrap selected text in bold without manually typing the asterisks or switching to a toolbar.Suggested Implementation: