Giving InfinitePIP a clearer front door

By May, InfinitePIP needed a clearer way to explain itself outside the application. The May 14 commit added a project site, styling, a favicon and a desktop screenshot. The commit message was short, so I checked the changed files rather than treating the message as a complete description of the work.

A picture-in-picture tool is easier to understand when you can connect it to an actual desktop task. Keep a reference visible, watch an application while you work elsewhere, or frame a small part of a larger display. The site work gave that explanation somewhere to live.

It also helps separate the product idea from the implementation history. Someone looking for the app shouldn't need to work out why there is a deprecated Python folder next to the Electron application before understanding what the floating views do.

This particular commit changed the website assets. It didn't establish a new capture engine or prove a freshly signed application release. That's a useful distinction in the chronology because the Git default branch stops here, while the local working tree contains substantial later application work.

If we only read the latest commit date, we would miss the August interface and security changes and the September packaging and upload records. The project site is one milestone, and those later records are another.

For this stage, the progress was straightforward: InfinitePIP had a more complete presentation around the workflow already taking shape in the app. The next work would concentrate on making that workflow easier to navigate, package and verify across the supported desktop targets.