An entity is the fundamental unit of content in Capacities. Every entity in Capacities has a type (the other way around you could say that an entity always is the instance of a certain content type). There are two groups of content types: basic content types and custom content types. Each type needs a singular name, a plural name, and an icon. In addition, each type has its own set of properties. These properties define the structure of the content. They can be rearranged when in page view by dragging items in the property list. Read more about properties here.
Basic content types
Basic content types are types that are built into the app. Each user has access to them. Basic types are designed to be useful to all users and to cover the most basic use-cases first. As the app progresses and becomes more mature we will gradually add more basic types starting with the use-cases with the most demand.
Since basic content types are built into the app, we can give them a tailored design and functionality. We can make them more powerful with custom functionality. That’s their big strength.
Capacities currently includes the following basic types:
A page is a general purpose content type to write, arrange, collect and summarize text and any kind of other content. You can give it a title, a description, an icon, and a cover image. It has an area of blocks for the main content. Like any other content, you can tag it.
A web link is any bookmark or a URL from the web you want to save or link to in one of your text blocks. In Capacities, this is a first-class entity you can tag, add notes, or reuse in other content.
The image content type allows you to use images in your notes. You can use URLs, upload image files or use our integrated Unsplash search.
A tweet is a content type that allows you to store tweets and threads from twitter. You can tag it and add your personal notes to it below.
This content type is specifically for PDF files. It enables a reader view to display PDFs inside your notes. You can also tag your PDFs.
The audio content type can be used to include audio tracks in your notes. It needs an audio file or an URL to an audio file. You can also use our WhatsApp or Telegram integrations to send voice messages to your Capacities space.
This content type allows you to upload and reference files in your space. Files can be tagged, and embedded in other notes, and you can also add dedicated notes to each file.
❓ What content types would you love to see?
Custom content types
Custom content types are types that you can create for yourself. To get started just follow the tutorial on custom content types. If you want to get inspired or you want to share ideas and best practices use our
# 🎓 · showcases channel on Discord.
Besides name, icon, and properties, you can further customize their own type. This includes the following:
- The default behavior of opening a link of that type (open in preview or open as page)
In the future, further customization will be possible. This will include:
- A base design: Page, Zettel, Profile, Wiki page
- Which properties are shown on the small card and wide card
- Hide properties from the list in page view
- Hide columns in table view
- And more…
Every entity can quickly be moved to another database. You can pick a type on an entity page and specify which properties should be kept and transformed. You can also just ignore some or add multiple properties to one blocks property.
This feature also works for collections. On a collection page, use the dropdown next to the type label.
This allows you to move a collection to another database within a few clicks. It makes reorganizing your knowledge base simpler and faster. You can now conveniently start by just using pages and later organize them into people, meetings, atomic notes, and more once you need a more granular organization. 💡
🤔 Do you find this explanation unclear or feel like something is missing in the docs?
With your help we can make the docs better for everyone. So just let us know, and we’ll improve it ASAP!
📨 Did reading the docs make you think of any product improvements?
Please let us know if you have an idea for a feature, think that something is missing or see a conceptual inconsistency that could be fixed. Just post it on our feedback board and discuss it with us and other users!