0
0
mirror of https://github.com/nodejs/node.git synced 2024-12-01 16:10:02 +01:00
nodejs/doc/blog
2013-10-22 10:56:03 -07:00
..
feature blog: Update streams2 feature post to match actual doc 2013-03-06 14:19:16 -08:00
module
npm link to LevelUP modules wiki page, not level-hooks 2013-03-03 22:12:53 -08:00
release blog: Post for v0.10.21 2013-10-18 15:46:02 -07:00
Uncategorized doc: fix blog link in blog posts and README 2013-09-13 14:55:08 +02:00
video blog: s/LibUV/libuv/ 2012-09-30 15:47:27 -07:00
vulnerability blog: HTTP server DoS vulnerability details 2013-10-22 10:56:03 -07:00
favicon.ico blog: Add favicon to blog site 2013-06-14 10:26:50 -07:00
README.md website: typo fixes 2012-11-29 23:00:09 +01:00
v0.9.9.md blog: v0.9.9 is unstable, not stable 2013-02-07 10:35:35 -08:00

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:

  1. title
  2. author
  3. status: Only posts with a status of "publish" are published.
  4. category: The "release" category is treated a bit specially.
  5. version: Only relevant for "release" category.
  6. date
  7. 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.