Building Tero Studio — Ideas to Systems

Tero Studio is built around a simple idea: writing should stay close to the tools I already use.

Architecture

The publishing path is intentionally small.

Obsidian
   ↓
RustFS
   ↓
Quartz
   ↓
Caddy
   ↓
terostudio.kr

Each component has one responsibility.

Obsidian remains the source of the writing workflow. The site does not need a separate web-based CMS.

RustFS stores and synchronizes the public content used by the builder.

The publishing system should remain replaceable. The content should not depend on the website implementation.

The builder synchronizes the source and generates a new static release.

aws s3 sync s3://obsidian/TeroStudio/ /opt/tero/source/ \
  --endpoint-url http://s3.terostudio:30292

A successful build is switched into production through the current symlink.

The next step is expanding Tero Studio beyond the journal and documenting projects such as QuantaDB.

Useful references can also be linked directly from the article, including Quartz.

Ideas become systems here.