I wish that Objects could be Extended by additional properties (so that we can have Object "People" with visible properties Name, Email, Notes for example and Extend it by Collection "People/Musicians" with some additional fields , like Band, etc, visible only for "People/Musicians"..). Or maybe Extendable tags (subTags) may do this.
This was a very useful video. Many users starting their Cap journey often fails to understand the practical differences between tags and collections. I figured it out just a week ago and since then I have ensured a balance between them. I was overusing tags and while with queries tags were also subgrouping the objects, but it was making the tag list too much overwhelming and Collection labels has a better UI. Thank you, Beth, for always demonstrating with real examples. I am curious about those circular masked/framed profile images. While mine shows circular profile images after opening as they the default page layout is selected as profile, but the images look too messy in wall and gallery view. Please tell me how did you manage to get them circular? 🤩
Beth, I'm a Pro user and I don't have the option to use AI in creating tags or collections. This is something that only avaliable for Believers for now?
U already showed this in ur yt channel! love u so.. im Seeing this limit compared to a different app.. object types should probably not be a method of organization. So I do not understand the purpose of collections compared to tags. almost encourages a limited form of thinking, where object types are seen anything like folders. We should just stick to tags, collections do not do anything different or better than tags I don't think.
That's what I need! I'm just getting to know capacities, you released the video on time! Go on, you are very cool, capacities team💪
Thank you!
I wish that Objects could be Extended by additional properties (so that we can have Object "People" with visible properties Name, Email, Notes for example and Extend it by Collection "People/Musicians" with some additional fields , like Band, etc, visible only for "People/Musicians"..). Or maybe Extendable tags (subTags) may do this.
Thank you so much for this helpful and accurate clarificatin that helps me a lot in setting up my new capacities instance.
Glad it was helpful!
Just what I needed, thanks!
This was a very useful video. Many users starting their Cap journey often fails to understand the practical differences between tags and collections.
I figured it out just a week ago and since then I have ensured a balance between them. I was overusing tags and while with queries tags were also subgrouping the objects, but it was making the tag list too much overwhelming and Collection labels has a better UI.
Thank you, Beth, for always demonstrating with real examples.
I am curious about those circular masked/framed profile images.
While mine shows circular profile images after opening as they the default page layout is selected as profile, but the images look too messy in wall and gallery view.
Please tell me how did you manage to get them circular? 🤩
Thank you! I show the content preview in the small card view :)
very useful video. thx
Beth, I'm a Pro user and I don't have the option to use AI in creating tags or collections. This is something that only avaliable for Believers for now?
All paid users have access to it- have you turned AI on for your space?
notification squad!
U already showed this in ur yt channel! love u so.. im Seeing this limit compared to a different app.. object types should probably not be a method of organization. So I do not understand the purpose of collections compared to tags. almost encourages a limited form of thinking, where object types are seen anything like folders. We should just stick to tags, collections do not do anything different or better than tags I don't think.
You can certainly stick to tags if that's what works for you!
All I need is Capacities + Anytype
There must be an easier way to integrate a person into sentences I type in my notes. All I can do is type /person and then name. Annoying.
If the person already exists @{name} will work :)