Your comments

PNG would also allow for transparency, which would be my main argument pro-PNG.

It caches in sessionStorage what should be visible, so if you had books enabled when you opened it and then turned it off with the page open that would persist until you closed the browser.

If the books module was never enabled, I'm not sure why the above would be happening.

It should already be doing that, it's setup to check both if the option is enabled server-side _and_ if the active user (if users are turned on) can access book shares.

Do you have any errors in your browser console (Developer Tools in Chrome)?

So the blanket answer for external metadata is "probably not". All of the book-specific stuff I'm working with is pulled from Ubooquity, so if it can't see it I might not be able to. I am, however, moving series/arc data to their own external files (these are generated elsewhere, guide to come eventually).

You could look to Calibre, it has the ability to embed some metadata. I haven't played around with it much though, I'm mostly just a comic hoarder.

And the guide is coming. I've been tweaking a lot of the tools for my own collection, but I do intend on getting a guide out eventually.

Open themScript.js, there are settings at the top. What you want is "showBookCount", set that to true.

If you built what you've been using thus far with PageBuilder, the newest version on the GitHub page will output series.json if you pass it a cvinfo file.

I'm currently putting together a script to convert folder-info.html files into series.json's.

There's a breadcrumb div in folder-info.html that's taking precedent (part of the reason I'm moving away from folder-info files per-series/arc). Try deleting folder-info.html and drop this in there instead.

series.json

But I see what you mean about having Story Arcs replace the Base with Story Arcs (since it's not really under Comics proper). I'll see what I can do.

Edit: So what I did, is for pages with a certain class (arcPage), if the second link (to the right of Comics) isn't to Story Arcs, add an additional link to Story Arcs.

That leaves my test case looking like this:

Just need to iron out a few little things before I roll another official release, but the changes are out there now.

Currently the breadcrumb nav works like so:

Series/story arc/script generated pages like Publisher/Story Arc are mostly hardcoded nav:

Base > Publisher > Series or Base > Story Arcs > Arc

If those don't exist, it's taking the current page and finding the matching link on the parent. Then doing the same with the parent's parent.

Base > Parent > Current page
This means to generate just the above, you're functionally loading 3 pages. It's somewhat ridiculous.

It'd be significantly easier if things were laid out in an actual hierarchy (/comics/Marvel/StoryArcs/Civil War) instead of (/comics/completely_unique_ID_number).

Since you're not the only one using nested story arc folders, I actually moved to generating the nav like in second example in the new templates I'm building into the theme (no more need to add folder-info.html files), but there isn't an easy way to migrate the data into the new format yet.

Since you're using it, I wanted to share what you inspired. I'm gradually moving my entire collection away from per-series folder-info.html files, and saving my metadata to JSON. Then using templates to build series/arc pages.

The templates only load if there's no folder-info present, so this shouldn't break anything you've already got setup.


This is with just your folder.jpg and json.cbr in the folder.