[packaging-on-the-web] Multiple pages in a package (#28)

There are good use cases for packaging in locations where Web is still behind a slow or intermittent connection. Packaging can be used for alternative distribution of web content - via local sharing (ShareIt etc), on memory cards, from local servers, and so on. Simply capturing a set of articles or pages and then using them offline as reference material can be very useful when data plans are limited and expensive.
[Here is a doc](https://docs.google.com/document/d/1Uiid7eEGPmnV9tUGZjuLDBIy4gcDbZJf2TbJgkc-5g4/edit?usp=sharing) with some desired properties and use cases for such conditions.

One of the interesting capabilities is for the package to contain multiple pages, potentially from varied origins. There are 2 elements likely needed for that:

- some sort of index at the beginning of a package, that allows 'random' access to resources w/o unpacking the potentially large package into parts or some local file system. Mulitiple pages and resources (and perhaps a couple of movies) can result in a package that is prohibitively expensive to 'unpack', especially on a mobile device.

- a notion of a 'main page' that is opened when user 'opens' a package - in case it is loaded in some way to the device and is 'opened' by a browser. 



---
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/packaging-on-the-web/issues/28