Episode 3 · Capture, then write it up

New ideas get lost in chat threads and scratch notes. This episode captures one first, turns it into a bilingual article, and links it to your projects and CV.

1. Capture it: Catch moment

Click Catch moment at the bottom right of the dashboard or in the title bar:

• A title and a few sentences are enough. You do not have to finish the thought.
• Click Dictate to speak instead of typing. Each recording can last up to 60 seconds and is appended to the body after transcription. This needs an OpenAI key in Settings.
• Drag images or experiment videos straight in. Videos get a cover frame extracted locally.
• Changes save automatically when you stop typing; click Confirm when you are done. New moments are private and do not appear on the site.
• Confirming opens the moment straight away. It is saved in the language you wrote; Sync zh → en in the left rail drafts the other language in one click (OpenAI key needed).

The CLI equivalent:

then edit content/resources/moment/gem-bench-accepted/parts/body/en.md.

2. Write the article

There are two ways in:

• Write it directly: click Write blog, or switch the Catch moment sheet to its article tab at the top.
• Grow it from a moment: open the moment, move the pointer next to FILES at the top left, click the gear that appears, and choose Relations. Convert to blog turns the moment into an article; New blog or New project under Create from this moment makes a new one and records that the moment evolved into it. From the CLI:

When you write, use the first two sentences to say what changed and why it matters, then list the evidence, and end with what you cannot claim yet.

Select some text and three actions appear: Optimize expression polishes the wording, Agent local edit rewrites that passage from your instruction, and Comment issue leaves a note to come back to. The first two need an OpenAI key.

3. Chinese and English side by side

• The en / zh switch at the top right of the editor changes language, and a missing language can be drafted for you. A button at the bottom right switches between the formatted view and the Markdown source.
• After editing one language, you can carry the change into the other. The difference is shown paragraph by paragraph and only saved once you confirm.
• To add a language from the CLI:

4. Link it to projects and your CV

At the bottom of the Relations page, pick a Target type (Blog or Project) and a resource, then click Link reference. Existing links are listed under Linked content. From the CLI:

The common relation types are evolved_into, documents, references, supersedes, and part_of. Once linked, the article, the project page, and your CV point to the same source instead of three hand-maintained copies.

5. Check

Move on once content lint reports 0 fatal. Everything you change in the desktop app is saved as Markdown, the same files the CLI edits.

Checkpoint

• one private moment;
• one article written in both languages and linked to its project;
• no fatal issues from silan content lint.

The next episode puts it online.