| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Hey, |
Sorry, something went wrong.
|
Thanks — both done. One repo per plugin. Each plugin now lives in its own repository and the
They share a design system, which stays in a monorepo I develop in; a release On the naming, I'd like to check the premise before renaming, because four
Navigation and System are keys only — they work on a Pedal. The middle three So rather than put "Stream Deck +" in every name, I've made each plugin say
The long descriptions spell out which half needs a Plus. That tells a Mini or |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Six plugins for the Stream Deck +, built as one family in a shared design
language (near-black ground, one accent per plugin, words rather than icons
for anything that has gone wrong):
Each has been used on real hardware (Stream Deck +, app 1.5.0-beta.15), carries
manifest.json, attribution.json, a thumbnail, a README and GPL-3.0, and
ships with a deck-free test suite.
One thing worth flagging: the six entries share a repository URL
The plugins live in one repository, and each release is a tag whose commit
tree is that single plugin — manifest.json at the root, the shared design
system vendored in, no symlinks. That works because the store installs a
commit's archive rather than a repository, and the entries differ by hash
while the store keys everything else on the manifest id. Installing was
verified end to end by extracting archive/<sha>.zip into the plugins
directory.
The cost is that scripts/find_outdated.py compares each entry's hash against
the repository's newest default-branch commit, so these six will always look
outdated to it. If you would rather have one repository per plugin, say so and
I will split them and re-open — it is a mechanical change on my side.
Release tags for reference: