marcuskammer/coleslaw
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update NEWS and remove user-defined routing item from docs.

Browse source
This commit is contained in:
Brit Butler 2014-04-29 13:31:45 -04:00
parent 514761e1cd
commit e26ed4398c
2 changed files with 8 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
NEWS.md
View file

@ -1,5 +1,10 @@
## Changes for 0.9.4 (2013-05-05): ## Changes for 0.9.4 (2013-05-05):
* **SITE-BREAKING CHANGE**: Coleslaw now supports user-defined routing.
Instead of hard-coding the paths various content types are stored at,
they must be specified in the configuration file (.coleslawrc). Just
copy the `:routing` key from the [example][single_site.rc] to get
the old behavior.
* Coleslaw no longer expects a particular repo layout. Use whatever * Coleslaw no longer expects a particular repo layout. Use whatever
directory hierarchy you like. directory hierarchy you like.
@ -69,5 +74,6 @@
* Initial release. * Initial release.
[hacking_guide]: https://github.com/redline6561/coleslaw/blob/master/docs/hacking.md [hacking_guide]: https://github.com/redline6561/coleslaw/blob/master/docs/hacking.md
[theming_guide]: https://github.com/redline6561/coleslaw/blob/master/docs/themes.md [theming_guide]: https://github.com/redline6561/coleslaw/blob/master/docs/themes.md
[single_site.rc]: https://github.com/redline6561/coleslaw/blob/master/examples/single-site.coleslawrc

12
docs/hacking.md
View file

@ -176,18 +176,6 @@ changes to at least the post templates and the `read-content`
function. There may be other areas where it was assumed tags/dates function. There may be other areas where it was assumed tags/dates
will always be present. will always be present.
### User-Defined Routing
There is no reason *coleslaw* should be in charge of the site layout or
should care. If all objects only used the *slug* slot in their `page-url`
methods, there could be a :routing argument in the config containing
a plist of `(:class "~{format string~}")` pairs. A default method could
check the :class key under `(routing *config*)` if no specialized
`page-url` was defined. This would have the additional benefit of
localizing all the site routing in one place. New Content Types would
probably `pushnew` a plist onto the config key in their `enable` function.
This has been implemented on the branch `user-defined-routing`.
### New Content Type: Pages! ### New Content Type: Pages!
Many users have requested a content type PAGE, for static pages. It Many users have requested a content type PAGE, for static pages. It