Connect notes and structured data

A task list is not always the right place for a process note or an inventory. Hopya keeps tasks, Documents, and Tables in one hierarchy while giving each a distinct job.

Choose the resource for the job

Choose the resource for the job: reference table
Resource	Good starting use	What it is not
List	Assigned work, due dates, statuses, checklists	A generic database table
Document	Process notes, project context, decision records	An anonymous publishing system
Table	Inventories, reference records, structured registers	A task List or arbitrary SQL console

Place these under a project/folder or at workspace root where the resource permits it. Access follows workspace membership plus the resource-specific permissions—not merely its visible location in the sidebar.

Write the context in a Document

Create a Document through the hierarchy controls and write its Markdown body. Use pages for related sections and true subpages for nested material. The Pages sidebar distinguishes peers from children; deleting a page also removes its nested document subpages, so review the confirmation carefully.

Discuss the document in comments. Private image upload is available in document discussions; do not assume every task-body image feature applies to the Document body itself.

Build a Table with useful types

Build a Table with useful types: reference table
Example inventory column	Type
Item	Text
Quantity	Number
Checked	Checkbox
Category	Select; choose options at column creation
Optional dates	Date or date/time

Checkbox Empty, Checked, and Unchecked are different values. Zero and false are present data, not empty cells. Use JSON when those distinctions matter during transfer; CSV intentionally flattens some empty/null distinctions.

Filter and calculate across the data

Filter and calculate across the data: reference table
Control	Scope
Column heading	Typed ordering
Filters	Conditions combined with AND
Filtered total / Calculate	All matches, including unloaded rows
Calculations	Counts, sums/averages, date bounds, checked counts by type

Finish or cancel edits before changing view settings. Ordering/filtering may move an edited row out of the current view; clear filters before deciding it disappeared. Exports include the complete Table independently of grid filters and loaded pages.

Keep editing deliberate

Use Enter/F2 or double-click for keyboard cell editing; use explicit Save/Cancel or tap the selected cell on touch screens. A conflict retains the draft and offers reload instead of silently replacing a concurrent value.

Deleting a column permanently removes that value from all records. Deleting a Document or Table is not a soft-delete workflow. Export and back up important data before destructive changes.

Connect an existing SQL table only when needed

Live PostgreSQL, MySQL, and SQLite sources are optional. The operator allowlists destinations/files; a credential manager saves a write-only connection, then links a primary-keyed source with Table permissions.

Cell edits write back to existing source rows; primary keys/generated fields are read-only.
Source schema changes and row insertion/deletion belong in database tools.
Removing the Hopya link does not delete source data.
Uncertain commit: reload and inspect before retrying.

See live source deployment and the Table API before enabling write-back.