Blog style preview: from a note to an article
A test article for previewing English typography, heading navigation, code, tables, and links between articles.
This is a style preview, intended to show what reading the blog feels like. The text is here only to demonstrate the layout and can be replaced or removed later.
Why keep a space for writing
Everyday notes capture thinking as it happens: a question that is still taking shape, a command that fixes an error, or an idea worth pursuing. They do not need to become articles the moment they are written down.
A public article goes one step further. It explains the background and fills in the context so that someone encountering the problem for the first time can follow along.
First understand what you did. Then write clearly about the experience.
Chinese and English
Chinese is the original. The English version is translated once the Chinese text is ready, preserving its voice, judgments, and technical details as closely as possible. The language links below the title connect the two versions of an article.
Connections between articles
Some ideas deserve an article of their own, with links from other articles where they are useful. For example, this reference preview demonstrates a further reading path. Expand the article map at the bottom of this page to see the connection.
Explain a practical experience
Start with a specific problem
Describe what you wanted to solve, the environment you used, and how you decided whether the result was correct. Readers need to know when a procedure applies.
- Describe the problem.
- Provide the necessary steps and explanations.
- State what you verified and what remains uncertain.
Commands and code
Short commands such as git status can appear within a sentence. Longer examples belong in a code block:
from pathlib import Path
notes = sorted(Path("notes").glob("*.md"))
for note in notes:
print(note.stem)
Code uses a monospaced font, and long lines can scroll horizontally within the block.
Compare choices in a table
| Content | Where it belongs | When to organize it |
|---|---|---|
| Temporary ideas and leads | Private notes | When they become part of ongoing work |
| Reusable methods | Long-term notes | When the same kind of problem comes up again |
| An experience with a clear structure | Public blog | When the background, process, and conclusion are ready |
Leave room for reading
An article does not have to be long. A clear problem, a trustworthy account of the process, and a measured conclusion can make a record worth reading.
What to write next
- A key judgment made during a technical task.
- A specific question prompted by a paper.
- A workflow that has held up in regular use.
Further reading
Continue to Linking articles together, or switch to 中文 to compare the Chinese layout.
Article map
Arrows point from a citing article to the article it references. Select a node to read it; translations are shown separately.