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
Description:
Currently, when using the Geekdoc theme in Hugo, I have to write {{< katex >}} every time I want to use LaTeX. This can be cumbersome, especially when working with many mathematical expressions. I am requesting an easier way to integrate KaTeX, such as using $$ for inline and block math.
Proposed Solution:
It would be highly beneficial if we could use $$ delimiters for KaTeX integration, similar to how other Markdown processors handle LaTeX. This would make the process more intuitive and reduce the overhead of repeatedly writing the shortcode.
This change would streamline the writing process and improve the overall user experience for those frequently incorporating mathematical expressions into their content.
Additional Information:
If there's already a way to achieve this with the current setup or if there are any workarounds, please provide guidance.
Thank you for considering this feature request.
The text was updated successfully, but these errors were encountered:
Feature Request: Easier KaTeX Integration
Description:
Currently, when using the Geekdoc theme in Hugo, I have to write
{{< katex >}}
every time I want to use LaTeX. This can be cumbersome, especially when working with many mathematical expressions. I am requesting an easier way to integrate KaTeX, such as using$$
for inline and block math.Proposed Solution:
It would be highly beneficial if we could use
$$
delimiters for KaTeX integration, similar to how other Markdown processors handle LaTeX. This would make the process more intuitive and reduce the overhead of repeatedly writing the shortcode.Examples:
Instead of writing:
We could simply write:
This change would streamline the writing process and improve the overall user experience for those frequently incorporating mathematical expressions into their content.
Additional Information:
If there's already a way to achieve this with the current setup or if there are any workarounds, please provide guidance.
Thank you for considering this feature request.
The text was updated successfully, but these errors were encountered: