*structure rules control cards' type and content. Like all rules, structure rules apply to a specific set of cards.  Changing a *structure rule will impact every card in the set.  Structure rules can be seen and edited in a card's dashboard (or "cardboard"), which is accessed via the ellipses icon (space_dashboard ) in a card's menu.

Nests in structures

Consider again our example of the recipe form card:

Recipe+*type+*structure

RichText :

{{+preparation time | labeled}}

{{+serves | labeled}}

{{+diet | labeled | link}}

{{+tags | labeled | link}}

{{+ingredients|titled}}

{{+preparation|titled}}

{{+discussion|titled; show:comment_box}}

help edit space_dashboard

{{+preparation time | labeled}}

{{+serves | labeled}}

{{+diet | labeled | link}}

{{+tags | labeled | link}}

{{+ingredients|titled}}

{{+preparation|titled}}

{{+discussion|titled; show:comment_box}}

Looking at that card, you'll notice lots of nesting, like {{+ingredients|titled}}.  Here's how this works:

• The double curly brackets ({{) represent a nest, meaning that the recipe card nests the ingredient card inside it.
• The "+" before "ingredients" indicates that this is a contextual name. meaning the name of the nested card depends on the context of the nesting card.  For example, if I make a recipe called "Lobster Bisque", then its ingredient list will be named "Lobster Bisque+ingredients".
• The "titled" refers to the view of the nested card.  When you see the ingredients card inside the recipe, it will be in titled view.

The important pattern to understand is that these structured nests establish naming patterns. All the cards that contain information about ingredients will have names that begin with the recipe name and end with "+ingredients".  

See also

• nesting
• compound names
• contextual names
• views
• virtual cards