Bugs
Closed
Naming inconsistencies between collections and views
Into Formats miniapp, we have "Views" which displays the collections exactly as they are.
And the “Collections” mini-app, which displays the collections (or, more precisely, the views from the “Formats” mini-app).
“Formats” views would be nice, but right now that doesn't seem to be the case—maybe we should reconsider the naming.
5 Comments
Sign in to comment
I'm unclear on what the issue here is. Can you reprhase?
Yes, reading it over, I understand
Into "Formats" miniapps, what is "View"?
It really seems to be “Collections”... so why call it “View” if it's the same thing?
Because it's not the same thing in our long term vision. For example, you can create a cross-space view (e.g. I want to see all tasks assigned to me). That's not a collection per se, because it's a view that's specific to only you and your vault.
But it's true, that in the beginning and for the most part, people will see it as Collections. As mentioned, we imagine that most people shouldn't be in the formats section at all, it's more for people who are trying to troubleshoot and really dive deep into their spaces.
Right now, this is the only thing that works for some of the pages: they aren't in a collection, they aren't part of the WIKI, and they aren't contacts, tasks, etc. No other miniapp besides this one lets me find them.
Overall, I think can generally ignore the Formats mini app today. We will improve it in the future, but it's not where a lot of our energy is going into because it relates to a lot of other architecture decisions. I know it doesn't make sense right now, but these details won't likely survive future iterations. This is why we primarily want cohorts to focus on certain areas, although it is nice that y'all are exploring into other parts of the app.