In theory, you could use an API Resource to represent the Navbar, since the Resource itself could be anything (e.g. an array), but then what do you gain - you are effectively passing an Array to the Resource, when returns an Array (from toArray method).
How do you intend to pass the Resource down the pipe (as a response)?
Correct! Will be passing an array to Resource. And then was planning to put some checks inside Resource like if a user has an admin role add or hide particular attribute. Not sure it is the correct way of doing it. What do you suggest?
Thinking more about it. Resource would be only useful in case there is a collection to pass to a Resource?
I don't see how the Response class would really benefit you. You could do all of that in your own class; maybe even consider implementing the Responsable interface (if relevant). This will allow you to keep all of the logic associated with the navbar together. Check out this blog post for some context - that will not always be directly applicable, but should provide some insights.