Explore

published doc

Rebecca: Oh, do you believe in ghosts, Ted?

Ted: I do. But more importantly, I believe they need to believe in themselves.

_Glossary

_Glossary

Item

Description

Alternative Names

Resources

Action

@Formula⁠

-based action in a doc, triggered by the user manually through a

@Button⁠

or automatically via an

@Automation⁠

Automation

Automations are rules that you give your Coda

@Doc⁠

to follow, defined by

@Formula⁠

s ,

@Table⁠

s , & row references. These rules can be set to trigger at defined times or when changes are made to a table in your doc.

⁠

https://help.coda.io/en/articles/2423860-automations-in-coda⁠

⁠

Block

⁠

@Page⁠

@Table⁠

@Formula⁠

@Pack⁠

@Button⁠

Button

A Button

@Block⁠

that executes an

@Action⁠

⁠

Doc

The Coda doc, the comprehensive digital organism made of

@Block⁠

Document, Application

Domain

The context the

@Doc⁠

refers to.

It’s the array of

@Entity⁠

describing the world where all the

@Doc⁠

‘s users live.

Context

Entity

It’s usually a noun represented as a

@Table⁠

‘s row - such Project, a Person, a Task, a Key Result - related to the

@Domain⁠

scope

Formula

⁠

Coda Formula Language⁠

that enables programmatic access to data structure/actions/packs

⁠

https://help.coda.io/en/articles/2695142-the-basics-of-coda-formulas⁠

⁠

https://help.coda.io/en/articles/1499893-named-formulas⁠

⁠

https://coda.io/formulas⁠

⁠

Front Page

It’s a

@Page⁠

built to satisfy a specific

@Functional⁠

need or

@Use Case⁠

Functional

Everything related to how the

@Doc⁠

should work from a user’s perspective as a specific work and carried out in the

@Front Page⁠

e.g. assign tasks, update OKRs, take meeting notes, manage clients, ... See also

@Use Case⁠

Helper Table

@Table⁠

designed to carry out specific needs, but not intrinsically related to a

@Domain⁠

For example: User Preferences, Templates, ...

Model

It’s the set of

@Table⁠

s containing all the structured data needed for the

@Doc⁠

⁠

Database, Data, DB, Tables

Pack

Connect with other application and/or services

⁠

https://help.coda.io/en/articles/2414769-using-coda-packs⁠

⁠

Page

A Page containing Text,

@Block⁠

Pages can be nested hierarchically to easily create logical sections.

A good practice is to distinguish between:

Content Pages:

@Front Page⁠

@Service Page⁠

Section Pages: Container of other pages

Although any Page can be both.

⁠

https://help.coda.io/en/articles/75123-using-pages-and-subpages⁠

⁠

Service

It’s the section that contains all the main

@Block⁠

s for the

@Doc⁠

Usually kept hidden or not accessible for everybody.

It contains

@Table⁠

, Configurations,

@Action⁠

s and it’s ideally the root of all the

@Service Page⁠

Engine, Admin, Backend

Service Page

It’s a

@Page⁠

used mainly as a convenience container (such a

@Table⁠

holder, or a section parent) that does not explicitly carry out

@Functional⁠

purposes

Back Page

Table

A Table

@Block⁠

It could represent an

@Entity⁠

or an

@Helper Table⁠

and displayed in multiple modes, through

@View⁠

⁠

https://help.coda.io/en/articles/772922-overview-of-tables⁠

⁠

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”

View

It is a reference to a

@Table⁠

There can be multiple Views per each

@Table⁠

It’s a good practice to keep

@Table⁠

in the

@Model⁠

section and

@View⁠

s as a way to consume their data in the

@Front Page⁠

There are no rows in this table

⁠

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.