you
can indeed decorate instance, static and class methods if you find it necessary and it will work
that said, one reason there's likely not much content on it is bc we typically recommend against OOP patterns within "prefect-specific" usage unless forced to adhere to some existing constraints that necessitate it because pure functions square better with prefect's runtime philosophy (dynamic graph of function calls) and OOP often creates more complexity than necessary. that's not to say you shouldn't use OOP code within or around your workflows or that you can't ignore my recommendation and have things work out great 🙂 im just giving context on the lack of OOP-forward examples