- v6.0.1 June 11, 2012 - Fixed plugin generation tests
- v6.0.0 June 11, 2012 - Breaking changes that may affect you - Removed `documentsPath`, `filesPath`, `layoutsPath` configuration options for their array based alternatives `documentsPaths`, `filesPaths`, `layoutsPaths` - Removed `require` from `templateData` as it needs to be specified in your project otherwise it has the wrong paths - Removed `database`, `collections`, `blocks` from `templateData` for their helper based alternatives `getDatabase()`, `getCollection('collectionName')`, `getBlock('blockName')` - Removed `String::startsWith`, `String::finsihesWith`, `Array::hasCount`, `Array::has` as we never used them - Removed `DocPad::documents` and `templateData.documents`, now use `getCollection('documents')` - New features - Differential rendering - Extendable CLI - Template helpers - Other changes - Better error handling - Moved to Joe for unit testing
…re thorough testing.
…ut how layouts should now work. The problem is that we need to make the decision of whether or not to parse special directories /^_/.test(dirName). Parsing would allow us to watch those files, however can complicate the workflow as they all get added to @database. Whereas if we don't parse them, then they are entirely handled by plugins - which is probably desirable… It is a tough call, and not sure how to proceed.
- v5.0.5 April 14, 2012 - Added `.npmignore` file - Added `document.contentType` and `document.contentTypeRendered` - Fixed `document.contentRendered` on files that do not have layouts - Added tests for: - Checking that `ignored: true` documents are properly ignored - That ignored common pattern files/dirs are properly ignored - That attributes are being applied properly