Page Requirements

• ability to add a single page to the archive (like echo <url> | archivebox add)
• ability to import a list of pages / feed of URLs into the archive (like archivebox add <url>)
• link to the homepage of the index /
• link to the django admin list of URLs for editing the archive /admin/
• link to the archivebox github repo & documentati

Since the data elements in the left Metadata panel in a Collection Index are searchable via the search bar above the links, it would be helpful to add something like the following to the user guide:

Search Collection Index

• Find all links from a session in a Collection by typing session:
  (session + colon, no spaces)
• After typing session: enter the session ID (can be foun

Describe the bug

The fl param isn't filtering any CDXJ API entries.

Steps to reproduce the bug

Using 2.4.0-rc5 version can't filter the output of the CDXJ API.

Expected behavior

Currently getting
https://m.preprod.arquivo.pt/wayback/cd

The README states:

Both Service Worker and Custom Element APIs are new and only supported in modern web browsers (e.g., Chrome > v67, Firefox > v63).

Since ipwb's inception, support for these two techs have become largely ubiquitous in all major browsers except for Safari/Custom Elements and some mobile browsers per CanIUse. I think this mes

One user writes:

one helpful API documentation that I have seen looks similar to the docs here: https://marketplace.zoom.us/docs/api-reference/zoom-api/webinars/webinars. It specifies all of the parameters, responses, and data (along with type) contained in those responses.

The About/Help menu does not have a tie back into this repo for users to submit bugs encountered. This might be useful, as otherwise there is no reference to the repo in the application, just an e-mail address.

warcio uses a default Content-Type value for WARC records of application/warc-record. This MIME type is not documented or specified anywhere; the WARC spec only mentions application/warc as the MIME type for WARC files and application/warc-fields for warcinfo and metadata records (though it is ambiguous on whether that is required or

The current behavior needs to be documented. Per the WARC/1.1 spec, there is no documented "right way" but identifying the current approaches would be useful and help to guide how it might be done.

After implementing Bootstrap 4 and accessibility fixes, screenshots in documentation should be updated to reflect SFM 2.3.0 release. See the User Guide in particular.

The main motivation would be an easier to read and navigate theme. We could write or port a theme to mdbook, but the docs are "just markdown" so it would also be easy to switch to mkdocs, which has a larger community and optional features/plugins.

Here's an example theme that is particularly readable; we'd want to host fonts ourselves on (eg) archive.org:

https://squidfunk.github.io/mkdocs-m

TimeGate endpoint has changed in NLA, the config file needs to be update accordingly.

$ curl -IL https://web.archive.org.au/awa/http://example.org/
HTTP/2 307 
server: nginx
date: Sat, 14 Mar 2020 14:56:01 GMT
content-length: 0
location: https://web.archive.org.au/awa/20190924232650/http://example.org/
link: <http://example.org/>; rel="original", <https://web.archive.org.au/awa/http:

The screenshot thumbnails should link to a summary page that allows inspection and onward action. Including:

• Screenshot (full length)
• Seed URL, linked to live web and to Wayback.
• Source Target ID, linked to W3ACT
• Other forms, thumbnail etc.