Calm Systems for Creative Work

How to design personal software that helps you think without turning every surface into a productivity dashboard.

writing.track设计工程

关于界面承诺、命令交互、阅读体验和组件系统的设计工程笔记。

把 UI/UX 选择和实现约束放在同一个阅读路径里。
read.use("calm-systems-for-creative-work")Technical context

read.context("technical")

  • Source notes
  • Component decisions
  • API / route contracts
  • Implementation review

Calm Systems for Creative Work

The point of a personal site is not to publish everything. The point is to keep important work findable, contextual, and alive.

#Make memory addressable

Writing, projects, photos, code snippets, and decisions should all have stable homes. A good structure is not bureaucracy; it is a way to make past thinking reusable.

#Reduce ceremony

Systems fail when they require too much maintenance. The content model should make the common path boring: add a file, write metadata, publish.

snippet0 lines
export const contentContract = {
  source: "mdx",
  ownership: "repository",
  syncTarget: "feishu",
};

The fancy part should be in the reading experience and retrieval layer, not in the act of adding one more useful note.

#Let beauty do work

Beauty is not decoration here. It is a compression layer for confidence. When the page feels composed, the reader assumes the system underneath has been considered too.