[Feature] Allow setting a home/main page

[Alch-Emi]

Context

Archived websites and online projects often have a large number of pages essential to the archive. Currently, very single one of these pages is shown in the "Pages" list, sorted by name or date, with no pages given special treatment.

Most websites will have a page which acts as an index, table of contents, or starting point for exploring the site. This home page is generally included in archives, and typically is a wonderful starting point for a user exploring the archive. Unfortunately, users are greeted with the aforementioned comprehensive list of every page, which often makes it hard to find the home page, much less the page you're looking for.

The WACZ specification includes the mainPageUrl (v1.1.1) / home (v1.2.0 and later) attribute in the datapackage.json file, which offers a way to record a single entrypoint into an archive. Currently, this attribute is never included in the output wacz, and is ignored when importing a wacz.

What change would you like to see?

As someone who uses ArchiveWeb.Page to create offline copies of small, single websites and online projects, I want to be able to mark an entrypoint for an archive.

As someone who uses ArchiveWeb.Page to explore archives, I want to quickly be able to begin exploring an archive in an intuitive manor.

Requirements

• At least one way to mark a page as the home page for the archive
• If present, the marked page should be given special consideration in the UI to make it easy to find
  • listed above the other pages?
  • opened when the archive is opened?
• If an archive has a marked page, that page should be recorded in mainPageUrl/home in the exported wacz (with respect to the current supported wacz version)
• When importing a wacz, the home/mainPageUrl attribute should be read and marked in the resulting collection.
  • Special consideration for importing a wacz with a home page into an archiving session that already has a home page?

Todo

No response

[Alch-Emi]

I figure this is probably already in the pipeline, given that webrecorder both writes the spec and this software, but I wanted to create an issue for it so that there's a place to track progress and discuss implementation. I'm also a little bit curious about implementing this myself, but I'd like to hear more on what sorts of UI/UX designs the maintainers would be willing to accept.