Yes, this is drafted by Claude - I wrote some horrible rambling monstrosity, and Claude said “no man, don’t post that.” I agreed:
Fibery does an amazing job showing you which database an entity belongs to — the colored badge at the top of every entity card is one of my favorite UI details. It helps me, as an architect, navigate instantly.
But for my editor-level users, that badge is decorative at best and confusing at worst. They can see the database name and color, but they can’t click through to the database (it’s hidden from them in the sidebar). So the badge tells them something they can’t act on.
Here’s the deeper problem: my users work primarily in docs and entity records. When they land on an entity — maybe from a link in a doc, maybe from a search result — they have no way to orient themselves. They can’t answer: “Where does this entity live? What view should I go to if I want to see others like it?”
The entity feels like it’s floating in space.
The ask: Make the database badge on entity records clickable for all users. When clicked, show a dropdown of views that include this database. Clicking a view takes you there, filtered or scrolled to the current entity if possible.
This would bridge the gap between Fibery’s database-centric visual language and the view-centric navigation that non-architect users actually experience. Right now those two systems don’t connect for most users, and it makes the platform feel disorienting to people who aren’t building it.