I wouldn't imagine (unless you're building a dynamic table) that the attributes specifically would be helpful but it is more about application and usage. In terms of your application, that's more on you to work through and figure out. Without any knowledge of what you're building and the different functional areas, it's challenging to provide advice because the use-cases are so broad. In my case, I pass in table headings and data to construct a table. Another component may pass in an attribute to show/hide a sub-component, etc.
As a current example, I'm building a page component to display a list of product feedback recommendations but I may want to reuse this component structure elsewhere, so I'll have an attribute for passing in data, which could take many different forms e.g. API data, data from different database tables, etc. I also want an attribute to title the component on the page with a specific label, etc. Now, I could just put this in statically but then the web component is no longer reusable in the sense that data is not dynamic and I have to manually adjust each new instance of the component. Does that make sense?
@Tom Ireland
.jpeg/public)