structure - Decko

Forms are content patterns. Every day we encounter lots of formatted information: weather forecasts, sports cards, restaurant menus, user profile pages, tax documents and nutrition labels each have their own pattern of what information is included, and how it is laid out. These patterns help you compare and contrast information visually, and to notice missing information.

Decko lets you create forms and apply them to Set of cards, so they contain the same kinds of information with the same structure. It does so using two Setting: *structure and *default

Example

Open these two Recipe cards, and you'll see they have the same structure:

Chilaquiles+preparation time

30 minutes

Chilaquiles+serves

4

Chilaquiles+Diet

conventional

Chilaquiles+tag

Chile

Chicken

Chilaquiles+ingredients

Tortilla
Tomatos
Chile
Chicken (optional)
Cheese
Cream

Chilaquiles+preparation

Place the tortillas in a pan with oil until they are really crunchy
Prepare the salsa (placing tomato in a pan with oil, onion and chile)

Chilaquiles+discussion

Testing out discussion

Carnitas+preparation time

10 minutes

Carnitas+serves

4

Carnitas+Diet

conventional

Carnitas+tag

pork

meat

mexican

Carnitas+ingredients

Pork

Water

Salt

Lime

Carnitas+preparation

Put the pork in a pan and cover (barely) with water. Sprinkle liberally with salt. Cook on medium flame until the liquid is reduced to a small amount that barely covers the bottom of the pan. Be sure to turn the pieces of pork halfway through.

Pull the pork out and shred/pull. Return to the pan and squeeze in the juice of two limes.

Cook until the pork starts to crisp.

Carnitas+discussion

You'll also see the same pattern when you create a new Recipe card.

Here's the structure rule that is used to template Recipes:

{{+preparation time | labeled}}

{{+serves | labeled}}

{{+diet | labeled | link}}

{{+tags | labeled | link}}

{{+ingredients|titled}}

{{+preparation|titled}}

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

You'll notice the structure nests cards with recipe information like preparation and cook time, number served, ingredients, etc. When someone edits a recipe, they can edit those nested cards. (See sample recipe edit form.)

How To

*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 ( ) in a card's menu.

Nests in structures

Consider again our example of the recipe form card:

{{+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 names. 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 views 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".

Tips

Checkboxes, radio buttons, and other form elements can be added using Pointer.
You can add help text that shows up when nested cards are created or edited.

Discussion

Tickets relevant to structure