I’m new to ArchiveWeb.Page and am a bit flabbergasted at how this tool differs from tools I’ve traditionally used for archiving web pages. I understand there are many users that wish to record every page exactly as viewed (those mostly rely on screenshots), e.g. for legal documentation purposes, but my primary goal is creating an archive of a self-contained site that will soon be gone. So when I am navigating around the pages of this site, I have zero interest in getting the same page captured over and over again, and IMHO the tool should record which URLs I have already captured and should NOT capture them again when the same page is linked to from multiple places or the page just gets revisited by back navigation. I’m not interested in capturing user interactions with the site, I’m interested in archiving the site, in an as complete but lean/efficient way as possible. Currently not only the same pages keep getting re-captured, but even the JS and CSS resources occur dozens of times in the archive, inflating it enormously.
Traditional tools such as Adobe Acrobat’s web capture or other older web crawler tools also usually offered automation options such as “auto-capture all local links from this page”, where “local” could mean on the same server or those staying within the same path or no more than 2 levels up etc. - again I’m missing such efficiency options here in ArchiveWeb.Page.
Any suggestions for what I might do differently, or do I need to look for different tools?