Deploying to gh-pages from @ f7f3d27 🚀

Author: matu3ba

articles/using_zine/index.html

@@ -16,7 +16,7 @@ <h1><span class="reset_a"><a href="/">Jans Website</a></span></h1>
             <h2>Using zine</h2>
           </div>
           <div class='static_double_column3'>
-            <div><p>This is a brief experience report on usage of zine as static website generator from 20241220.</p><p>My main use cases are</p><ol><li>to utilize <code>build.zig</code> as convenient way for more complex tasks with C, C++ and Zig code</li><li>having a simple to use and functional cache system for task 1</li><li>effortless code highlighting that most of the time works</li><li>static generated website and I would appreciate ways to integrate other content and document creation solutions.</li></ol><p>I am mostly happy with the still result, but less happy with the experience and time to get there.</p><ol><li>For example, I would prefer not having to invest several hours into figuring out which CSS properties work and which not and manually twiddling with sizes and use a bespoke and simple tool to <a href="https://github.com/matu3ba/matu3ba.github.io/blob/28519f871b39c94d097c6ec8a2da2b0a33c79793/assets/style.css:242" target="_blank">generate static grids with wraparound</a> instead of figuring out that <a href="https://github.com/matu3ba/matu3ba.github.io/blob/28519f871b39c94d097c6ec8a2da2b0a33c79793/assets/style.css:222" target="_blank">flex grids dont allow wraparound</a>.</li><li>Automatic extraction of all html attribute classes for css style code for coloring would have also been nice, instead of <a href="https://github.com/matu3ba/matu3ba.github.io/blob/28519f871b39c94d097c6ec8a2da2b0a33c79793/assets/style.css" target="_blank">manually inspecting the html code to attach colors</a>.</li><li>Specifying nice colors takes time, so the few hours were expected.</li><li>Not having nested markdown lists properly working in SuperMD files is not a great experience, when finding out after converting html to markdown for the first level already.</li><li>Dumping properties form scripty instead of having to look them up and having documentation in a more editor-readable way, for example text file would also have been a nice to have.</li><li>Comments within markdown blocks (empty line, <code>[This is a comment]::</code>) are undocumented. and not supported in the editor setup.</li></ol><p>All in all, I am happy, but will fix the list issue in SuperMD files, because I believe this nudges people into not writing on edge cases and is a worse experience than plain markdown. Code polishing will also follow.</p></div>
+            <div><p>This is a brief experience report on usage of zine as static website generator from 20241220.</p><p>My main use cases are</p><ol><li>to utilize <code>build.zig</code> as convenient way for more complex tasks with C, C++ and Zig code</li><li>having a simple to use and functional cache system for task 1</li><li>effortless code highlighting that most of the time works</li><li>static generated website and I would appreciate ways to integrate other content and document creation solutions.</li></ol><p>I am mostly happy with the still result, but less happy with the experience and time to get there.</p><ol><li>For example, I would prefer not having to invest several hours into figuring out which CSS properties work and which not and manually twiddling with sizes and use a bespoke and simple tool to <a href="https://github.com/matu3ba/matu3ba.github.io/blob/28519f871b39c94d097c6ec8a2da2b0a33c79793/assets/style.css:242" target="_blank">generate static grids with wraparound</a> instead of figuring out that <a href="https://github.com/matu3ba/matu3ba.github.io/blob/28519f871b39c94d097c6ec8a2da2b0a33c79793/assets/style.css:222" target="_blank">flex grids dont allow wraparound</a>.</li><li>Automatic extraction of all html attribute classes for css style code for coloring would have also been nice, instead of <a href="https://github.com/matu3ba/matu3ba.github.io/blob/28519f871b39c94d097c6ec8a2da2b0a33c79793/assets/style.css" target="_blank">manually inspecting the html code to attach colors</a>.</li><li>Specifying nice colors takes time, so the few hours were expected.</li><li>Not having nested markdown lists properly working in SuperMD files is not a great experience. Especially, when finding out after converting html to markdown for the first level already.</li><li>Dumping properties form scripty instead of having to look them up and having documentation in a more editor-readable way, for example text file, would also have been a nice to have.</li><li>Comments within markdown blocks (empty line, <code>[This is a comment]::</code>) are undocumented and not supported in the editor setup.</li><li>The release process for common platforms should be documented. Github Pages requires <code>Build and deployment Source</code> -> <code>Deploy from branch</code> -> <code>gh-pages</code>, <code>/ (root)</code>.</li></ol><p>All in all, I am happy, but will fix the list issue in SuperMD files, because I believe this nudges people into not writing on edge cases and is a worse experience than plain markdown. Code polishing will also follow.</p></div>
           </div>
       </div>
     </div>