mirror of
https://github.com/hanzo-docs/team.git
synced 2026-10-30 18:59:50 +00:00
zeekay
d61c5f219e
- Standalone Fumadocs (Next 16 static export) app, same stack as hanzo-docs org - 79 pages ported from upstream Huly docs, fully rebranded to Hanzo Team - Removed lead/inventory; added Account & billing (orgs/workspaces, usage, agents) - Login updated to Continue with Hanzo (hanzo.id) + Google/GitHub + email - CF Pages deploy workflow (org CF creds) -> docs.hanzo.team
47 lines
3.4 KiB
Plaintext
47 lines
3.4 KiB
Plaintext
---
|
||
title: Cards vs. Documents
|
||
description: Learn when to use Cards and when to use Documents.
|
||
---
|
||
|
||
You can use Cards to completely replace [Documents](/docs/knowledge-management/documents) in your workspace — or use them both simultaneously for different purposes. Let’s take a look at the key similarities and differences between Documents and Cards.
|
||
|
||
#### Similarities
|
||
|
||
- Content is created with the same text editor
|
||
- Activity section records change history and includes area for commenting
|
||
- Set roles, permissions and privacy at the space level
|
||
|
||
#### Differences
|
||
|
||
There are a few important differences between Cards and Documents, which are summarized in the table below:
|
||
|
||
| **Feature** | **Documents** | **Cards** |
|
||
|--------------------------|---------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|
|
||
| **Attributes** | Attributes are defined by the system (title, content, created by, etc.) and cannot be changed | In addition to the default attributes defined by the system, you can also define as many **custom attributes** as you want |
|
||
| **Sorting and filtering**| Cannot be sorted or filtered by attributes | Can be sorted and filtered by attributes |
|
||
| **Attachments** | No designated area for file attachments (you can only send attachments with a comment in the Activity section) | Designated area for attachments |
|
||
| **Organizational structure** | Nested, where documents can be nested within other documents | Organized by Type, where Cards of the same Type are grouped together |
|
||
| **Relations** | Can be linked together in a 1:1 relation through @ mentions and backlinks | Can be linked through parent-child relations, and using References and Relations defined on their Type |
|
||
|
||
> **Note:** While our initial implementation of Cards is focused on knowledge management, Cards will also serve as the foundation for many other features on the platform, including process management and threads. With Cards, you'll be able to build your own custom applications within Hanzo Team, such as a CRM, CMS, project management system and more. Stay tuned for more updates soon!
|
||
|
||
---
|
||
|
||
#### Okay, that was a lot of information … so which should I choose?
|
||
|
||
Let’s keep it simple!
|
||
|
||
##### Use **Cards** if:
|
||
|
||
- You need to add custom attributes to your docs, like “client”, “document type” or “status”
|
||
- You need to be able to sort and filter your content by attributes
|
||
- You need to define specific _relations_ between types of entities; for example: `Contract ←→ Client`
|
||
- You plan to build processes and workflows around your Cards in the future
|
||
|
||
##### Use **Documents** if:
|
||
|
||
- Your docs organization is simple, where the nested document structure is sufficient
|
||
- You need to jot down some quick notes, without needing to store them in a structured format
|
||
|
||
Of course, the best way to find out which system is right for you is to try them both and see what works. Happy exploring! 🚀
|