mirror of
https://github.com/hanzo-docs/team.git
synced 2026-10-30 18:59:50 +00:00
- 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
72 lines
4.7 KiB
Plaintext
72 lines
4.7 KiB
Plaintext
---
|
||
title: Creating Cards
|
||
description: Learn how to create Cards.
|
||
---
|
||
|
||
<div className="rounded-box">
|
||
<h5><strong>What is a Card?</strong></h5>
|
||
<p>A Card is an instance of a Type, representing a specific piece of structured information. It follows the properties defined by its Type and can include rich text, attachments, relations, and tags, making it a flexible building block.</p>
|
||
</div>
|
||
|
||
To use Cards effectively in Hanzo Team, it’s important to first understand their relationship with Types.
|
||
|
||
Think of a **Type** as a blueprint and **Cards** as the structures built from that blueprint. If your blueprint defines a "house" as a structure with four windows and one door, then every house created from that blueprint will always have four windows and one door, regardless of color or furnishings.
|
||
|
||
If you haven't already, check out our guide on [Creating Types](/docs/cards/types/creating-types) — then return here to learn how to create Cards from the Types you've made.
|
||
|
||
## Creating a space
|
||
|
||
A space is like a container for your Cards. You can set permissions at the space level to determine who can access the Cards within that space.
|
||
|
||
To create a new space, click the `+ Create Space` button in the top left corner of the Cards module. Here, you can enter a name, select they Types that will be used in that space, and set owners, members and privacy settings. Setting the space to "Private" will prevent anyone other than the members listed from accessing the Cards in that space.
|
||
|
||
Spaces for Cards act like any other space in Hanzo Team, meaning you can leave, join and archive spaces, and global admin roles will apply. For more on managing permissions at the workspace and space level, see our guide on [Roles and Permissions](/docs/advanced-settings/roles).
|
||
|
||
## Creating Cards
|
||
|
||
Click `+ Create Card` in the top left corner of the Cards module.
|
||
|
||
The following elements make up a Card:
|
||
|
||
1. **Title** - a name for your Card
|
||
2. **Type** - the Type that defines the properties of your Card (see [Creating Types](/docs/cards/types/creating-types))
|
||
4. **Properties** - the details of your Card, as defined by the Type
|
||
5. **Rich text editor** - a collaborative text editing area that supports markdown formatting, images, tables and more
|
||
6. **Children** - an area for adding child Cards (see [Parent-child Cards](/docs/cards/parent-child-cards))
|
||
7. **Attachments** - an area for uploading files
|
||
8. **Activity** - a log of all changes made to the Card and area for commenting
|
||
|
||
> **Note:** Cards created from the `File` Type will have an additional area above the rich text editor for uploading files. To learn more about managing files with the `File` Type, see [File Types](/docs/cards/types/file-types).
|
||
|
||
Beyond these basic elements, Cards can also include:
|
||
|
||
* **[Relations](/docs/cards/relations/relations-overview)** - connections to other Cards
|
||
* **[Tags](/docs/cards/tags/tags-overview)** - optional properties that can be applied to Cards of different types
|
||
|
||
Relations and Tags are set at the Type level. In other words, when you want to create a new Relation or Tag for a Card, you'll need to define this on the Type in Settings. To see how, check out these guides on [Defining Relations](/docs/cards/relations/defining-relations) and [Creating Tags](/docs/cards/tags/creating-tags).
|
||
|
||
### Example: Creating an NPC Character Card
|
||
|
||
To create a Card, first make sure you've selected the correct Type from the left side menu, then click the `+ Create Card` button.
|
||
|
||
From here, you can enter information in all of the attributes you [defined on your Type](/docs/cards/types/creating-types). Below is an example of a Card for an NPC character in our **game design system**:
|
||
|
||
Note that this `NPC` Card has several [Relations](/docs/cards/relations/relations-overview), defined on the `Character` Type from which it was derived:
|
||
* **`Item`** - a `Character` possesses `Items`
|
||
* **`Environment`** - a `Character` exists in an `Environment`
|
||
* **`Game Narrative`** - a `Character` is included in a `Game Narrative`
|
||
|
||
## Adding Card attribbutes
|
||
|
||
To add an attribute to a Card, simply click the `+` icon next to the Type or Tag you want to add to. Adding an attribute on one Card will add the field to all existing Cards with that Type or Tag.
|
||
|
||
## Learn more
|
||
|
||
To further explore working with Cards, check out these guides:
|
||
|
||
* [Relating Cards](/docs/cards/relations/relating-cards) - Define structured relationships between Cards.
|
||
* [File Types](/docs/cards/types/file-types) - Manage images, videos, PDFs, and other media within Hanzo Team's default `File` Type.
|
||
* [Tags](/docs/cards/tags/tags-overview) - Apply additional attributes across different Types.
|
||
|
||
By understanding and structuring Cards effectively, you can build a powerful and flexible knowledge management system in Hanzo Team.
|