mirror of
https://github.com/nodejs/node.git
synced 2024-11-29 23:16:30 +01:00
3b2e9d2648
It seems like a good idea on the face of it, but lowWaterMarks are actually not useful, and in practice should always be set to zero. It would be worthwhile for writers if we actually did some kind of writev() type of thing, but actually this just delays calling write() and the overhead of doing a bunch of Buffer copies is not worth the slight benefit of calling write() fewer times. |
||
|---|---|---|
| .. | ||
| feature | ||
| module | ||
| npm | ||
| release | ||
| Uncategorized | ||
| video | ||
| vulnerability | ||
| README.md | ||
| v0.9.9.md | ||
title: README.md status: private
How This Blog Works
Each .md file in this folder structure is a blog post. It has a
few headers and a markdown body. (HTML is allowed in the body as well.)
The relevant headers are:
- title
- author
- status: Only posts with a status of "publish" are published.
- category: The "release" category is treated a bit specially.
- version: Only relevant for "release" category.
- date
- slug: The bit that goes on the url. Must be unique, will be generated from the title and date if missing.
Posts in the "release" category are only shown in the main lists when
they are the most recent release for that version family. The stable
branch supersedes its unstable counterpart, so the presence of a 0.8.2
release notice will cause 0.7.10 to be hidden, but 0.6.19 would
be unaffected.
The folder structure in the blog source does not matter. Organize files here however makes sense. The metadata will be sorted out in the build later.