Hmm, maybe that 'start using font' doesn't actually load the font resource into memory until it's actually needed to be used? I think I have my script editor using these fonts by default already (can't check right now).
Of course SourceCode Pro family is entirely monospaced!
The idividual file size limit for a file in a GitHub repo, I thought, was 100MBs (I think only that OpenGL file of Chromium CEF are that big, I have them zipped in the IDE repo), unless they've changed it. Maybe the 25MBs is the limit is only for the web interface? I'm using GitDesktop (the official UI app) to sync my repos (which I don't do often enough).Source Code Pro is a monospaced sans serif typeface created by Paul D. Hunt for Adobe Systems. It is the second open-source font family from Adobe, distributed under the SIL Open Font License. Wikipedia
I don't know, for 'Guides' without using the Browser Widget, I think a simple stack interface that pulls content from a folder full of text (or .md) files with any images included, that gets placed on the card on the fly, or maybe generate a nice PDF manual from it, either may be a better way to go with the Guides than everything stuff into a large stack file like that. For static content PDF has the advantage that they can often be nicely compress with LZW/JPG.
As you know I'm biased about 'Guides' because I want Extension modules to continue to be able to add to the 'Guides' when they're installed, the package format supports this when you include an Docs folder, with a some readme.md text and some images in it, it gets packaged into the '.lce' file (the zip compressed package format).
But I have grown to like the simple .md text/page formatting as well. The markdown is in a format that displays very well on gitHub btw, it's actually the default format for making GitHub Pages (project web sites). The simplistic tagging makes it easy enough to write script to translate it into other styled text formats for placing into a field or into a web page or whatever.
BTW, I just installed XUbuntu 22.x on my sons really-old ASUS chrome-book style netbook thing, and had it running the RC3 .appImage downloaded from the GitHub Repo, the Browser Dictionary seems like it's OK on that (its a bit sluggish but it's an old underpowered Celeron-sort-of CPU so everything lags a bit).