I do not want this website to remain a simple container for articles and images. In the long run, it may become a public personal knowledge system or an open research lab: a place where questions, experiments, evidence, decisions, and tools from real projects can connect and remain open to revision.

The problem is that a “complete knowledge system” can easily become a design project with no natural finish line. Before there is real content and a real reading path, decisions about automated synchronization, relationship models, permissions, or knowledge graphs are mostly based on assumptions. A complete-looking architecture does not prove that the site is useful.

Start with something that can be opened

The V0.1 goal is intentionally direct: build a site that people can open, read, and maintain. That gives us concrete questions to test:

  • Can a visitor understand what this lab records?
  • Can Chinese and English entries stay clearly connected?
  • Are guides, projects, experiments, and tools easy to distinguish?
  • Is a long entry comfortable to read on desktop and mobile?
  • Do the home page, archive, and feed reflect a content update without duplicate editing?

These questions only become answerable when the website exists. Real pages reveal whether titles wrap badly, metadata overwhelms the content, bilingual routes feel natural, and the content model is stable enough for continued work. Those observations are more useful than a system diagram built without usage.

What V0.1 deliberately leaves out

This version does not connect to Notion. It does not include automated synchronization, a working email subscription backend, paid access, or a complex relationship layer. These possibilities are not rejected; they are postponed until there is evidence that they solve a real maintenance or reader problem.

If local Markdown becomes difficult to maintain, then another content source may be worth evaluating. If readers need a reliable way to follow revisions, a subscription system can become a real priority. If recurring relationships emerge across entries, a richer relationship model can be designed around observed patterns.

Let the site constrain the future system

Building the site first does not mean abandoning systems thinking. A usable site creates better constraints for it: which fields the interface actually uses, which content types recur, where translation fallbacks are needed, and which updates belong in RSS.

V0.1 is therefore not a miniature version of a finished knowledge system. It is a foundational test of content organization, bilingual structure, and reading experience. The conclusions remain exploratory and will be revised as the site is used.