Decko's approach to data structure is powerful and unique. At its core it is atomic, meaning that data atoms (cards) are connected in rich and patterned ways to create larger structures.
The following features are central to structuring data on Decko:
- types - types are used to group data for special views, events, queries, etc.
- compound names - tree-like naming patterns establish field-like relationships between cards
- structure - formatting can be used to enforce naming patterns and create default displays
- CQL (the Decko Query Language) - based on types, names, and content references, CQL traverses all Decko's key card relationships
- Data First - weird as it sounds, Deckoers often enter data before they've added any structure. They then move the data into nesting or other cards, and then they establish patterns of inclusions with structure rules. Working with real data means you spot problems and opportunities much faster.
- Little Chunks - If you break your data down into bite-sized pieces, it makes it easier to arrange and re-arrange it later. You can always recombine data by including them together.