You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well, let me explain my typical use case, which acts as the foundation of my fork:
basically, when I'm converting a page, I wrote a custom css rule to get rid of all of the content I don't need (usually sidebars, menus, ads, annoying popups, accessibility menus like the one you indicated, etc.). and to stretch the main content to the 100% of the page. Firefox Style Editor and an ublock origin are the tools I employ.
This is part of the json file my fork is able to import/export.
That said, to answer your question, it's out of scope selecting which page component must go into the epub, because, well, it's subjective.
However, there's an open issue about this #8 but probably, just using the advanced tools ublock origin already exposes it's enough.
A minor issue: When attempting to save ars technica article, for example
https://arstechnica.com/space/2023/11/heres-why-this-weekends-starship-launch-was-actually-a-huge-success/
resulting epub includes a menu at the top:
and a footer at the bottom:
Both of these are not there in Firefox's reader mode.
The text was updated successfully, but these errors were encountered: