mirror of https://github.com/nodejs/node.git
61ccaf9a97
Conflicts: ChangeLog deps/uv/ChangeLog deps/uv/include/uv-darwin.h deps/uv/src/unix/fsevents.c deps/uv/src/unix/process.c deps/uv/src/version.c doc/api/addons.markdown doc/api/cluster.markdown doc/api/http.markdown lib/http.js lib/tls.js src/node_crypto.cc src/node_http_parser.cc src/node_version.h src/pipe_wrap.cc src/v8abbr.h src/v8ustack.d test/simple/test-http-pipeline-flood.js |
||
|---|---|---|
| .. | ||
| Uncategorized | ||
| feature | ||
| module | ||
| npm | ||
| release | ||
| video | ||
| vulnerability | ||
| README.md | ||
| favicon.ico | ||
| v0.9.9.md | ||
README.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.