Share
Explore
_Glossary
Item
Description
Alternative Names
Resources
1
Action
A -based action in a doc, triggered by the user manually through a or automatically via an
@Formula
@Button
@Automation
2
Automation
Automations are rules that you give your Coda to follow, defined by s , s , & row references. These rules can be set to trigger at defined times or when changes are made to a table in your doc.
@Doc
@Formula
@Table
3
Block
s, s, s, s, s
@Page
@Table
@Formula
@Pack
@Button
4
Button
A Button that executes an
@Block
@Action
5
Doc
The Coda doc, the comprehensive digital organism made of s
@Block
Document, Application
6
Domain
The context the refers to.
@Doc
It’s the array of describing the world where all the ‘s users live.
@Entity
@Doc
Context
7
Entity
It’s usually a noun represented as a ‘s row - such Project, a Person, a Task, a Key Result - related to the scope
@Table
@Domain
8
Formula
9
Front Page
It’s a built to satisfy a specific need or
@Page
@Functional
@Use Case
10
Functional
Everything related to how the should work from a user’s perspective as a specific work and carried out in the s
@Doc
@Front Page
e.g. assign tasks, update OKRs, take meeting notes, manage clients, ... See also
@Use Case
11
Helper Table
A designed to carry out specific needs, but not intrinsically related to a .
@Table
@Domain
For example: User Preferences, Templates, ...
12
Model
It’s the set of s containing all the structured data needed for the
@Table
@Doc
Database, Data, DB, Tables
13
Pack
Connect with other application and/or services
14
Page
A Page containing Text, s
@Block
Pages can be nested hierarchically to easily create logical sections.
A good practice is to distinguish between:
@Front Page
@Service Page
Although any Page can be both.
15
Service
It’s the section that contains all the main s for the .
@Block
@Doc
Usually kept hidden or not accessible for everybody.
It contains , Configurations, s and it’s ideally the root of all the s
@Table
@Action
@Service Page
Engine, Admin, Backend
16
Service Page
It’s a used mainly as a convenience container (such a holder, or a section parent) that does not explicitly carry out purposes
@Page
@Table
@Functional
Back Page
17
Table
A Table
@Block
It could represent an or an and displayed in multiple modes, through s
@Entity
@Helper Table
@View
18
Use Case
The definition of a functionality and how it should be accomplished.
It usually implies some data, decisions and actions.
For instance: “changing the status of a Project. Or “Notify all the overdue Tasks”
19
View
It is a reference to a .
@Table
There can be multiple Views per each .
@Table
It’s a good practice to keep in the section and s as a way to consume their data in the s
@Table
@Model
@View
@Front Page
There are no rows in this table
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.