Research the Tag Editing Approach about planktos HOT 4 OPEN

High Level Design Overview:

In order to make the engineering of tag editing easier, we need to separate Planktos into multiple components: lib, service worker, tag editor, and CLI. The flexibility that Planktos offers users is currently abstracted away into the service worker component, which we provide opinionated implementations of e.g. resiliency for static websites and CDN for video. Since there are now multiple paths to intercepting requests for static resources, we need to introduce the onIntercept event handler, which users can customize in order to serve different use cases. This event handler will run upon rendering the page or in the service worker upon intercepting a network call, allowing the user to customize the behavior of Planktos without having to consider the way that the call was actually intercepted.

The tag editing component is going to require editing the user's HTML in the build phase, dynamic rendering of edited tags (can be disabled if WebTorrent isn't supported), and execution of the user defined onIntercept event handler. Additionally, we are going to utilize this build phase to include the code for dynamic rendering and the SW install script.

from planktos.

I'm going to start out with the parse5 HTML parser: https://github.com/inikulin/parse5

It is used in Angular and Polymer, so its probably pretty stable.

from planktos.

Tags that need to be edited: <audio>, <base>, <iframe>, <img>, <link>, <object>, <picture>, <source>, <track>, <video>

from planktos.

Resources:

• Example of how to render WebTorrent files/streams to the DOM (webtorrent/webtorrent#879 (comment))

from planktos.