You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the experience of writing <kbd> elements and nested <kbd> elements for keystrokes when documenting key bindings are causing headaches.
Can we introduce some of the currently using markup for <kbd> and port them into markdown-it by looking up the rehype, remark and micromark communities?
The text was updated successfully, but these errors were encountered:
This would be great, since when trying to use markdown-it-kbd and bi-directional-links at the same time - the latter starts cluttering the log with attempts to parse kbd as bi-directional syntax.
In Nolebase, I directly use <kbd data-macos-keyboard-key="command">command</kbd> + <kbd data-keyboard-key="space">space</kbd> markup along with the CSS styles I manually tweaked for VitePress to make it possible to attach icons and logos for the keys.
These are the known markups I know for sure to look into:
Currently the experience of writing
<kbd>
elements and nested<kbd>
elements for keystrokes when documenting key bindings are causing headaches.Can we introduce some of the currently using markup for
<kbd>
and port them intomarkdown-it
by looking up therehype
,remark
andmicromark
communities?The text was updated successfully, but these errors were encountered: