NEWS.md (8237 bytes)
1 Legend: 2 * Site-Breaking Change: 3 A change that will break most config files or coleslaw installations. 4 It is expected to effect all users but should require only minor 5 user effort to resolve. 6 * Incompatible Change: 7 A change to Coleslaw's exported interface. Plugins or Themes that have 8 not been upstreamed are effected and may require minor effort to fix. 9 10 ## Changes for 0.9.7 (2014-11-25): 11 12 * **New Plugin**: Support for [embedded gfycats](http://gfycat.com/) 13 has been added. See the [plugin use][plg-use] docs for further details. 14 * **Enhancement**: UTF-8 support has been made more portable and 15 added to the Wordpress import plugin. (Thanks @cmstrickland!) 16 * **Enhancement**: Filenames are now included in errors from the 17 content loader. (via @PuercoPop) 18 * **Enhancement**: Coleslaw now handles **deploy-dir**, **repo**, 19 and **staging-dir** config options more gracefully. Previously, 20 various errors could be encountered if directory options lacked 21 a trailing slash. 22 * Several portability fixes were made to CCL's encoding handling 23 and usage in the post-receive script. 24 * An initarg bug was fixed in the directory-does-not-exist condition. 25 * Some namespacing bugs in the Static Pages plugin have been fixed. 26 27 ## Changes for 0.9.6 (2014-09-27): 28 29 * **SITE-BREAKING CHANGE**: Coleslaw now defaults to a "basic" deploy 30 instead of the previous symlinked, timestamped deploy strategy. 31 To retain the previous behavior, add `(versioned)` to your config's 32 `:plugins` list. 33 * **Incompatible Change**: Custom themes will be broken by a change 34 to URL handling. Previously, we were hand-constructing URLs in the 35 templates. All site objects now store their URL in an instance slot. 36 In general, hrefs should be of the form `<a href="{$config.domain}/{$obj.url}"> ...</a>`. 37 * **Incompatible Change**: The interface of the `add-injection` function 38 has changed. If you have written a plugin which uses `add-injection` 39 you should update it to conform to the [new interface][plg-api]. 40 * **New Plugin**: Support for [twitter summary cards][ts-cards] on blog 41 posts has been added thanks to @PuercoPop. 42 * **Docs**: Improved README and Theming docs. New Config File docs. 43 * Changes to `:routing` would previously break links in the templates 44 but now work seamlessly due to the updated URL handling. 45 * Loading content is more robust when empty lines or metadata are passed. 46 Thanks to @PuercoPop for the bug report and preliminary fix. 47 * The config `:repo` option is now deprecated as its value has become 48 a required argument to `coleslaw:main`. The value passed to `main` 49 will override the config value going forward. 50 * Improved handling of directories and error-reporting when they 51 don't exist is available thanks to @PuercoPop. 52 * The templates are now HTML5 valid thanks to @Ferada. 53 * Fixed a bug where RSS/Atom tag feeds were being published multiple times. 54 55 ## Changes for 0.9.5 (2014-06-13): 56 57 * **New Plugin**: Incremental builds, cutting runtime for generating 58 medium to large sites roughly in half! 59 * **New Plugin**: A Twitter plugin to tweet about your new posts. Thanks to @PuercoPop! 60 * Config options for the HTML lang and charset attributes. Thanks to @ryumei! 61 * Coleslaw now exports a `get-updated-files` function which can be 62 used to get a list of file-status/file-name pairs that were changed 63 in the last git push. There is also an exported `find-content-by-path` 64 function to retrieve content objects from the above file-name. These 65 were used by both the Twitter and Incremental plugins. 66 * The usual bugfixes, performance improvements, and documentation tweaks. 67 68 ## Changes for 0.9.4 (2014-05-05): 69 70 * **SITE-BREAKING CHANGE**: Coleslaw now supports user-defined routing. 71 Instead of hard-coding the paths various content types are stored at, 72 they **must** be specified in the configuration file (.coleslawrc). 73 Just copy the `:routing` key from the [example][example.rc] to 74 get the old behavior. 75 * **SITE-BREAKING CHANGE**: Coleslaw's multi-site support has changed. 76 Instead of having a single .coleslawrc in the user's home directory 77 that has sections for multiple repos, a .coleslawrc may be included 78 *in* the blog repo itself. If no .coleslawrc is found in the repo, 79 it is loaded from the user's home directory instead. 80 * Coleslaw no longer expects a particular repo layout. Use whatever 81 directory hierarchy you like. 82 * New Content Type Plugin: Static Pages, accepting a title, url, and 83 optionally tags and a date. All files with a `.page` extension are 84 compiled as static pages and reuse the POST template. 85 To enable Static Pages, add `(static-pages)` to the `:plugins` 86 section of your config. 87 * Coleslaw now allows content without a date or tags. Note that POSTs 88 without a date will still show up in the reverse chronological 89 indexes at the very end. 90 * Fixed an embarrassing escaping bug in our last quicklisp release. 91 92 ## Changes for 0.9.3 (2014-04-16): 93 94 * **INCOMPATIBLE CHANGE**: `page-path` and the `blog` config class are no longer exported. 95 * **INCOMPATIBLE CHANGE**: `render-content` has been renamed `render-text` for clarity. 96 * New Docs: [A Hacker's Guide to Coleslaw][hacking_guide] and [Themes][theming_guide]! 97 * A new theme *readable* based on bootswatch readable, courtesy of @rmoritz! 98 * Posts may have an author to support multi-user blogs courtesy of @tychoish. 99 * Fixes to the ReStructuredText plugin courtesy of @tychoish. 100 * UTF-8 fixes for config files and site content courtesy of @cl-ment. 101 * Fix timestamps in the sitemap plugin courtesy of @woudshoo. 102 103 ## Changes for 0.9.2 (2013-05-11): 104 105 * **INCOMPATIBLE CHANGE**: Renamed staging, deploy config options staging-dir, deploy-dir. 106 * A plugin for Github Pages support. (thanks @mrordinaire!) 107 * A new and improved implementation of tags. (thanks @woudshoo!) 108 * A THEME-DOES-NOT-EXIST error is raised when the theme can't be found. 109 110 ## Changes for 0.9.1 (2013-04-10): 111 112 * Added a PREVIEW function for REPL use. 113 * Make ATOM and RSS templates a separate "generic" theme. (thanks @woudshoo!) 114 * Fixed bug where repeatedly loading plugins caused them to appear in the page more than once. (thanks @woudshoo!) 115 * Fixes to spacing in navigation and tagsoup. (thanks @woudshoo!) 116 117 ## Changes for 0.9 (2013-02-20): 118 119 * **INCOMPATIBLE CHANGE**: All :plugins in .coleslawrc must be lists. (i.e. (mathjax) not mathjax) 120 * Add support for analytics via Google. 121 * Add support for Restructured Text via cl-docutils. 122 * Add support for deploying to Amazon S3. 123 * Add a heroku plugin to ease hunchentoot deployments. (thanks @jsmpereira!) 124 * Ensure coleslaw exits after MAIN. Fixes issue #13. 125 * Greatly improved docs for the various plugins and plugin API. 126 127 ## Changes for 0.8 (2013-01-06): 128 129 * Add support for new [content types](http://blog.redlinernotes.com/posts/Lessons-from-Coleslaw.html). 130 * Support for [Multi-site Publishing](http://blub.co.za/posts/Adding-multi-site-support-to-Coleslaw.html). 131 * CCL and Atom feed bugfixes. 132 * Major code refactor and docs update. 133 134 ## Changes for 0.7 (2012-09-20): 135 136 * Add commenting support via Disqus plugin. 137 * Add formal plugin API with per-page predicate support. (aka "injections") 138 * Note jsmpereira's [coleslaw heroku package](https://github.com/jsmpereira/coleslaw-heroku) in README. 139 * Support for RSS feeds of arbitrary tags, e.g. "lisp" posts. 140 141 ## Changes for 0.6.5 (2012-09-12): 142 143 * Add support for ATOM feeds. 144 * Add support for a sitenav in coleslawrc configs. 145 * Template and rendering cleanup. 146 * Miscellaneous deployment improvements. 147 148 ## Changes for 0.6 (2012-08-29): 149 150 * Support Markdown in core rather than as a plugin. 151 * Improve documentation + README. 152 * Copious bugfixes and code cleanups. 153 154 ## Changes for 0.5 (2012-08-22): 155 156 * Initial release. 157 158 [hacking_guide]: https://github.com/redline6561/coleslaw/blob/master/docs/hacking.md 159 [theming_guide]: https://github.com/redline6561/coleslaw/blob/master/docs/themes.md 160 [example.rc]: https://github.com/redline6561/coleslaw/blob/master/examples/example.coleslawrc 161 [plg-use]: https://github.com/redline6561/coleslaw/blob/master/docs/plugin-use.md 162 [plg-api]: https://github.com/redline6561/coleslaw/blob/master/docs/plugin-api.md#extension-points 163 [ts-cards]: https://dev.twitter.com/cards/types/summary