Memberstack targets elements using attributes, Jetboost targets using class name, and Finsweet components use both classes and attributes.
When developing my own code, I’ve been thinking through the best way to create code that won’t break later. It seems that targeting by class might be susceptible to breaking later if a client unknowingly edits the class name or deletes it.
Attributes on the other hand are hidden in Webflow and require some digging to change, thus making them (seemingly) less susceptible to breaking.
How should I be thinking about this? What are the pros/cons for each approach?