Episode 3 - Write the private article
Write up the result selected in Episode 1 as a private article. The goal is not perfect prose; it is a valid page that states the change, evidence, and uncertainty clearly enough to review.
1. Create the article
silan blog new new-research-resultThe command creates:
content/resources/blog/new-research-result/
parts/body/meta.toml
parts/body/en.mdTo add Chinese:
silan blog add-lang new-research-result zhThe new article remains private. Creating, editing, linting, or indexing it does not publish it.
2. Write four things first
Open:
content/resources/blog/new-research-result/parts/body/en.mdReplace the generated body with a small reviewable version:
## The current result in one clear sentence
State what changed and why another researcher should care.
### Evidence
- Primary source: <paper, data, benchmark, release, archive, or repository>
- What it supports: <the exact claim>
- What it does not support: <the uncertainty boundary>
### What changes next
Name the project page, résumé statement, or previous explanation that may
need an update after review.Do not begin with the entire project history. A reader should understand the new information in the first two sentences.
3. Validate what the system sees
silan content lint
silan index sync
silan blog show new-research-resultRead the sequence literally:
- lint checks whether the source is valid;
- sync rebuilds the local index;
- show prints the article as the system parsed it.
Fix fatal issues before continuing. Non-fatal missing information can remain if it is outside this update.
4. Keep provenance concrete
For the first update, the Evidence section is enough: name the paper, release, dataset, archive, or repository and state exactly what it supports.
The public v1.0 release uses the earlier idea and update content kinds. Current silan.tech screenshots may show update renamed to moment, but that name exists only on the main branch and requires a source build. Because this guide uses the public release, keep using update as the content kind.
Review checkpoint
Before Episode 4, confirm:
- the first two sentences state the result and its value;
- the evidence is named or linked;
- the uncertainty is stated;
- no credential or private note remains;
silan content lintreports0 fatal;- the article is still private.
Episode 4 changes the publication state, renders a local preview when Docker is available, and explains what is still required for a production URL.
No comments yet