Databases & Views

Dokyo databases let you store structured data with typed properties. The same data can be displayed as a table, kanban board, list, calendar, or chart, and you can filter and sort each view independently.

A Dokyo database is a collection of records (rows) with typed properties (columns). Unlike a plain table, the same underlying data can be viewed in several ways, and each view can have its own filters and sorting.

Starting from a template

New database — from the sidebar's menu, the collapsed sidebar rail, or the workspace home screen — opens a picker of ready-made databases rather than an empty grid: task tracker, project roadmap, content calendar, sales pipeline, bug tracker, and reading list. Each arrives with its properties, a handful of sample rows, and the views that make sense for that data, so you can switch between a board and a calendar and immediately see the point. Sample dates are relative to the day you create it.

Property types

Each column has a type that controls how its values are entered and displayed:

  • Text and Number
  • Select and Multi-select for tags and categories
  • Date, with an optional end date for ranges
  • Checkbox
  • URL, Email, and Phone, each rendered as a usable link
  • Page to link one or more pages from your workspace to a row
  • Formula for values computed from the row's other properties

A property's type can be changed later; Dokyo converts the existing values where it can.

Views

Display the same records in whichever way fits the task:

  • Table view: a spreadsheet-like grid, ideal for editing many fields at once.
  • Kanban view: cards grouped into columns by a select property, great for workflows and task boards.
  • List view: a clean, compact list of records.
  • Calendar view: records placed on a month grid by one of their date properties.
  • Chart view: visualize your data with charts to spot trends.

A database can hold as many views as you like, side by side in a tab bar. The first view is the table Dokyo creates with the database and stays a table; every view you add afterwards can be any of the types above.

Filters and sorts

Each view can apply its own filters (show only records that match conditions) and sorts (order records by one or more properties). This lets the same database power a "My open tasks" list and a "Completed this week" chart at the same time.

Embedding databases in pages

You can embed a database directly inside a page with the /database slash command, so structured data lives alongside your documents and notes. This one starts empty on purpose: when you are embedding a table into prose you are already writing, your own columns beat a template's.

Need help generating or summarizing content in your workspace? See the AI Assistant, which can also create databases, properties, and views for you.