Add support for HTML books

[paypur]

I think I'm pretty close to being done, so here's what I have. There's definitely even more that can be done, like the tooltips we talked about, but that will have to be for later.

Preview: https://paypur.github.io/docs/books/1.20/
Tinkers' PR: SlimeKnights/TinkersConstruct#5456
Mantle PR: SlimeKnights/Mantle#231

Notes

• PageContent's should override toHTML
• The auto-generated HTML is not very readable but I'm not sure if you care because you shouldn't manually edit it
• CSS is written assuming scale = 2, but this should be easy to change
• The old images are still there for comparing
• All images have been index with 8-bit color (if possible) then losslessly compressed
• Exporting has been split off into /mantle book export_html
• The book "chapters" feel kinda redundant now that we can just link to a specific page on an image
• Non Tinker's books might need to be updated to work with this

Still TODOs

• Fix ContentListings overflowing
• Compress the .png's
• Remove unnecessary HTML?? (like newlines)
• Add back the previous page layout for old versions
• Fix issues on mobile
• Rebase before we merge

[KnightMiner]

Something important to note: I don't want to replace the existing picture based books with HTML ones. I would rather have both. The reason is the image ones are way more likely to be stable on the chance the HTML updater breaks in the future, and are way more likely to be accurate across devices.

You will likely want a separate home page for HTML books vs image books, with links between the two as relevant.

[paypur]

Would it be better for the HTML books to be the primary, and the image books to be the fallback in case of any issues?

[KnightMiner]

Neither is really primary or fallback. They are just different pages. The book index can link them both:

Icon
Title
HTML / Images

Key thing is I want to have both. I find images works very nicely on mobile notably.

[KnightMiner]

What is the purpose of spacing? Name is a little generic for how specific of a number it provides.

[paypur]

it was just easier to change the css than a style when figure out how much padding I needed

[KnightMiner]

Well, if its worth keeping name it something like book-spacing. If its no longer needed then lets clean it up.

tbh, anything that common shows up is probably worth a class over a style as that allows us to fix it without regenerating all the files.

[KnightMiner]

This can probably be replaced with CSS that just makes a 16x16 bit of padding. Though low priority to swap out.

[KnightMiner]

The reason for the weird book paths is meant as a sort of cache buster for images. However, on the HTML pages that is not needed as those are not cached in the same way (if they are cached, doesn't matter where you fetch this from).

I guess the hard part is we don't really have another string to suggest the location to fetch these from. I'm inclined to say add a second string like include.book.html since that will save effort updating books in the future. The HTML can then just be stored under _book/tinkers/1.20/encyclopedia and alike. The _ before book ensures Jekyll doesn't generate pages for each html file, since they will not be usable directly.

[KnightMiner]

this file needs to be scss to use sassy css features. Jekyll will compile that to CSS so you still reference it as .css elsewhere.

[paypur]

what scss features does it use? looks like plain css to me

[KnightMiner]

Put this file in _sass and just include it in slimeknights.scss, like we do with treeview.

[KnightMiner]

Should also change the extension to scss as I believe its using scss features.