Reference for beginner?

HI all-
BRAND NEW beginner to Hazel. I'm using Photosync app to backup iphone images to my new UGREEN NAS (DXP4800plus) for both my wife and me, then trying to rename the images, move and combine them into a joint Archive folder, including a "J" or "S" suffix in the image name to identify if a particular image came from me or my wife's phone. I'm struggling to use Hazel successfully to rename the images/vids and then move them, what seems like a simple process.

Other than a cumbersome (though comprehensive) Hazel User Guide, where is everyone learning how to use hazel?? (Basic logic used when dealing with folders/subfolders/moving while keeping a folder structure, why nothing happens when I run a rule, etc., etc.) I'm not finding any posted Youtube content even close to the the 6.2.1 version I purchased...

Even if the videos you find are a little out of date, I don't think for the things you need, much has changed on that front.

That said, what specifically are you running into problems with? Can you post the rules you have so far?

"That said, what specifically are you running into problems with? Can you post the rules you have so far?"

I can't find a way to post rules (Hazel 6.1.2)... Is there a straight forward way to do this?

Meanwhile, while what I THOUGHT was a simple process with 3 rules to rename image files by date created and adding a suffix based on the monitored file name (e.g., "JT Raw" folder is photographs by JT....so, add suffix "JT" to the image name), it has taken many hours with AI help to get this entire process to work.

As a tiny example, "Kind is folder," "run rules on folder."
WHICH rules will be run on WHICH folder and WHEN? What is the logic behind a simple sub folder structure of "2026" and then sub-sub folder "2026 05"? AI tried to explain how this kind of rule will begin one the first folder, then...something to do with "no images in this folder, so it automatically goes to the next subfolder" type thing--which makes sense. But then there is something about once the rule is satisfied, it stops running. There were many other "little" things that made the entire process NOT work. (Argh!)

I just kept changing rules and then testing to see what happened. For many hours, nothing would happen. "This is because Hazel stopped at this point," blah blah blah. Overall, the rules I needed and ended up using were not very intuitive to me--but then, I'm NOT a Computer/IT kinda guy! (I DO have a Masters degree in Structural Engineering though...so I know a tiny bit). At least when I'd FINALLY get SOME sort of output, I could make basic adjustments to get the output I needed...

Thx for any words!