dotfiles VS awestore

git clone --recurse-submodules https://github.com/ChocolateBread799/dotfiles ~/dotfiles ln -s ~/.dotfiles/awesome ~/.dotfiles/img ~/.dotfiles/rofi ~/.dotfiles/picom.conf ~/.config/

[I tried to see at least if the icons are part of a pack so you could install it in your popOS, turns out they are all custom. The repo is here, if you want to check it out.]

ChocolateBread799's dotfiles - first of these configs whose dev found out about Dribbble it seems, prompting the knockoff neumorphic trend. Also of the JavaCafe01 vein of configurations (using the same organizational paradigm) as it seems JavaCafe01 deduced how to use Rubato and those who join the cool kids Discord channel are hip to the knowledge the rest of us, without need for socializing in the AwesomeWM crowd (I am over 30, I can barely tolerate having one friend and a gf, let alone people as interested in Awesome as I am). Rubato is in the configuration but the short examination I performed in preparing this for you, I could not find an implementation example, so not sure how actually helpful this maybe.

Look to this https://github.com/ChocolateBread799/dotfiles/blob/main/config/awesome/notifs/init.lua

Awestore - Rubato implementations often reference Awestore (specifically compatibility with it), which was last week's popular AwesomeWM animation framework until Rubato's tantra was read to the above configurations. Nonetheless, its got better documentation, sort of, and is worth a gander as it may make more sense to you or be more helpful to your purposes.

As far as compositing and animating, Awesome itself is NOT a compositor. You will need a separate compositor like picom for things like shadows, background blur, and true transparency. There are forks of picom that also implement window animations but I have not personally tried them. Simple animations can be implemented in Awesome with libraries like rubato or awestore but it's a fairly manual process of changing a window's x and/or y coordinates on a regular interval.