dotfiles VS polybar-scripts

For starting several container with a shortcut you want layouts. You can dump a workspace into a json layout file (see https://i3wm.org/docs/layout-saving.html) which will get you a file that looks like https://github.com/cwebster2/dotfiles/blob/main/.config/i3/workspace-1.json . The important bit is the swallows key that defines what things each node will eat. You can then make a script that loads the layout into a workrspace and the apps you want, which will then populate the layout. I think this will get you the behavior you are looking for.

If you have the build dependencies installed, this script builds nightly. https://github.com/cwebster2/dotfiles/blob/main/bin/update-nvim.sh

This doesn't directly answer your question, but probably has the pieces here for you to put together. I use this script for polybar using openweather API, there are a couple variations of this script in the repo too if you want more examples. Openweather API seems to work well though, you could probably modify it for you use case.

Yes, credits to the respective author. https://github.com/polybar/polybar-scripts/tree/master/polybar-scripts/easteregg-pornhub

https://github.com/polybar/polybar-scripts is a good resource for scripts, Google is a good resource for a lot of stuff. If you want simple see my dots I just show temp and conditions

I can offer this: polybar-scripts/battery-combined-udev

On a related note, there is a Github repo of common Polybar scripts (which is also available as an AUR package, polybar-scripts-git). It looks like you independently arrived at virtually the same script used for the updates-pacman-aurhelper module example.

Using the instructions from this site: https://github.com/polybar/polybar-scripts/tree/master/polybar-scripts/system-gpu-optimus

I do use Pipewire and this https://github.com/polybar/polybar-scripts/pull/320/commits/3cfaa589a2f22c5269d16732d035c9f0fee60ff3 for Polybar