omp packages

@gang-of-beads/pi-web-themes0.1.1

More themes for PI WEB: Pro, PI WEB and Clay light/dark pairs, plus Classic, Night, Paper and High Contrast.

GitHub Actions Published 7 days ago MIT ~227 downloads/mo

Untested on omp

This is a pi package. No one has reported whether it works on omp yet. If you try it, add your result below.

Did it work for you?

Result

One report per person. A new report replaces your old one.

Reports 0

No reports yet.

Readme

pi-web-themes

A theme pack for PI WEB. It adds more looks to Settings → Appearance, each built from PI WEB's theme tokens through the plugin contract:

Pair (follows the system light/dark setting) Light Dark
PI WEB PI WEB Light PI WEB Dark
Clay Clay Paper Clay
Material Material Light Material Dark
Pro Pro Light Pro

Single themes: PI WEB Classic, Night, Paper, High Contrast.

Pro is the flat mono look PI WEB used to ship as its built-in appearance. On PI WEB releases whose built-in appearance is Material, the pack's Material entries give way to the built-in ones, so Material is listed once.

Every theme sets the same tokens as PI WEB's own themes, so text, borders, status colours and the label colour on accent fills keep their contrast. contrast.test.ts checks it.

Install

pi install npm:@gang-of-beads/pi-web-themes

To follow main instead of releases, install git:github.com/Gang-of-Beads/pi-web-themes. It needs PI WEB 2.202609.0 or later; earlier releases bundle their own copy of this plugin.

Then reload the PI WEB page and pick a theme in Settings → Appearance. The plugin is browser-only: no session daemon restart is needed. To turn it off, use Settings → PI WEB plugins (plugin id themes).

For local development, link the folder into PI WEB's local plugin directory instead:

ln -s "$PWD" ~/.pi-web/plugins/themes

Develop

npm install
npm run check

npm run check type-checks, runs the theme shape and contrast tests, and bundles pi-web-plugin.ts (with Lit inlined) into pi-web-plugin.js, which the package ships. The bundle is committed so that a git install works without a build step, and the check fails when it is out of date.

Releasing

Update version in package.json and package-lock.json, give CHANGELOG.md a section for it, commit, and push a matching v<version> tag. The release workflow checks the package, publishes it to npm, and creates the GitHub Release from that CHANGELOG section.

License

MIT.