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
Unfortunately the css generated by syntect includes even css related to Sublime GUI features that will never even be used in the web page, this leads to bloat of the syntax css files.
There is a Lot of bloat that could be removed from these files, but it will be very time consuming to clean these files up, care must be taken to not remove useful things from these css files.
The other issue is that I really don't care for the way the class definitions work... I would rather be able to define a pallet of colors .z-1, .z-2, .z-3, etc... with a couple modifiers for bold, italic, and underline: .z-b, .z-i, .z-u Then have a crate that does the work of figuring out how to style the element.
Before creating a new rust crate to do this, research would need to be done to make sure that a rust crate does not already exist capable of doing this.
Currently tree-sitter is being considered to replace syntect getzola/zola#1787, but I am unsure if it also generates a crazy long list of class definitions, I need to research this.
The interesting thing is that when you use the .tmTheme file directly zola already outputs pretty tidy html with direct font tags, if it could do something similar with class definitions then it would be in my opinion perfect. I have not looked at any of the code yet that does this work.
The text was updated successfully, but these errors were encountered:
Going to Close this for now, Keats is hard at work on evaluating and implementing a replacement for Syntect. This likely won't be an issue once his work is merged into Zola.
Remove unnecessary parts of syntax css
Unfortunately the css generated by syntect includes even css related to Sublime GUI features that will never even be used in the web page, this leads to bloat of the syntax css files.
There is a Lot of bloat that could be removed from these files, but it will be very time consuming to clean these files up, care must be taken to not remove useful things from these css files.
The other issue is that I really don't care for the way the class definitions work... I would rather be able to define a pallet of colors .z-1, .z-2, .z-3, etc... with a couple modifiers for bold, italic, and underline: .z-b, .z-i, .z-u Then have a crate that does the work of figuring out how to style the element.
For example, take this line taken from this page: https://abridge.netlify.app/overview-code-blocks/
const e = document.querySelector("main");
Instead of this:
<span class="z-meta z-var z-expr z-ts"><span class="z-storage z-type z-ts">const</span> <span class="z-meta z-var-single-variable z-expr z-ts"><span class="z-meta z-definition z-variable z-ts"><span class="z-variable z-other z-constant z-ts">e</span></span> </span><span class="z-keyword z-operator z-assignment z-ts">=</span> <span class="z-meta z-function-call z-ts"><span class="z-support z-variable z-dom z-ts">document</span><span class="z-punctuation z-accessor z-ts">.</span><span class="z-support z-function z-dom z-ts">querySelector</span></span><span class="z-meta z-brace z-round z-ts">(</span><span class="z-string z-quoted z-double z-ts"><span class="z-punctuation z-definition z-string z-begin z-ts">"</span>main<span class="z-punctuation z-definition z-string z-end z-ts">"</span></span><span class="z-meta z-brace z-round z-ts">)</span></span><span class="z-punctuation z-terminator z-statement z-ts">;</span>
Have something like this:
Before creating a new rust crate to do this, research would need to be done to make sure that a rust crate does not already exist capable of doing this.
Currently tree-sitter is being considered to replace syntect getzola/zola#1787, but I am unsure if it also generates a crazy long list of class definitions, I need to research this.
The interesting thing is that when you use the .tmTheme file directly zola already outputs pretty tidy html with direct font tags, if it could do something similar with class definitions then it would be in my opinion perfect. I have not looked at any of the code yet that does this work.
The text was updated successfully, but these errors were encountered: