dotfiles VS awestore

nuxshed's dotfiles - of the JavaCafe01 vein, in particular pursuing the knockoff Neumorphic codepen look (that isn't actually Neumorphism as no object has a 3D appearance...) but this dev's code is relatively easy to parse the tea leaves of and if you dial back the Git history, you should be able to deduce something about implementing Rubato.

This is the way I have set it up as well, mostly because I made them before i was using LuaSnip and I'm too lazy to convert them all to lua.

hover, rename, code actions are all built into neovim. I liked lspsaga's rename popup, so i tried to recreate it from scratch. For code actions. im using telescope.

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.