lukechilds
/
node
mirror of https://github.com/lukechilds/node.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
6683 Commits
131 Branches
446 Tags
325 MiB
 
 
 
 
 
 
Tree: 713b9249e1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '713b9249e1'
${ noResults }
node/doc/blog
isaacs bf561c52a5
Blog post for v0.6.20 		13 years ago
..
Uncategorized Generate static HTML blog content out of markdown 13 years ago
module Generate static HTML blog content out of markdown 13 years ago
npm blog: Minor tweaks to style and some data conversion cleanup 13 years ago
release Blog post for v0.6.20 13 years ago
video Generate static HTML blog content out of markdown 13 years ago
vulnerability Generate static HTML blog content out of markdown 13 years ago
README.md Initial blog source 13 years ago

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:

  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 supercedes 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.