Documentation data

[jonschlinkert]

One of my "design" goals for the new site is to look for opportunities to make data more reusable, whenever possible. For example, our CHANGELOG will be formatted as YAML so that it can be parsed and used in templates. This allows the changelog to be rendered as markdown, HTML, or even pulled down from the GitHub API and consumed by some other application or lib.

I also believe that - if executed well - this will make the site more accessible, scalable and maintainable.

• changelog: version (object|key), date (string), changes (associative array)
• language features (todo)

Related

• Docs API: Documentation API #3

[jonschlinkert]

@matthew-dean, your thoughts on this would be great.

Also, you mentioned a "docs API", I think this will definitely be achievable in short order. GitHub's api let's you pull down specific documents (.e.g. '/repos/less/less-docs/contents/features.json' or whatever), you just need to set the encoding (probably to utf8) and you're good to go.