If you run a static #Jekyll website using the #MinimalMistakes theme, I once created a #cheatcheet to have the most important and frequently used features at hand. Feel free to use and share it
https://www.fabriziomusacchio.com/blog/2021-08-11-Minimal_Mistakes_Cheat_Sheet/
Just discovered how easy it is to add a simple TOC to your #Markdown #Jekyll
website
Simply add these two lines of code to your Markdown file (using the #MinimalMistakes theme + #kramdown):
* TOC
{:toc .toc_intext}
and add some appropriate #CSS commands to your _base.scss. That's it, no further plugins are requiered. See it in action here: https://www.fabriziomusacchio.com/blog/2024-01-08-ruhrmuseum/
@pixeltracker I’ve always preferred the dedicated sidebar, since that comes out of the box and doesn't require extra CSS.
In other contexts, an inline ToC can be useful, but when I have the choice, I’d always go with the nav.toc sidebar.
Does inline work better for you?
https://www.fabriziomusacchio.com/blog/2021-08-11-Minimal_Mistakes_Cheat_Sheet/#table-of-contents
@infotexture It depends on the purpose of the page. If a post is more about images, I don't use the side TOC to have more space for images. Otherwise, I use the normal TOC function of Minimal Mistakes.
@pixeltracker I wanted to thank you for this post--I have been using it for a year and a half at this point! I was recently trying to make a splash index.md page for a personal website and discovered that the kramdown and html button cheats can be modified for markdown as well:
url: "https://scratch.mit.edu"
btn_label: "Visit"
btn_class: "btn--info"
@pixeltracker this was a great post, thank you! I followed your link on related posts and wound up writing a widget that significantly improved on the logic in that article and is also plug-and-play for Minimal Mistakes. More at https://karmanivero.us/blog/related-posts-with-minimal-mistakes/