|
|
@@ -1,23 +1,6 @@
|
|
1
|
|
-What about themes? Templates are themes. DUH.
|
|
2
|
|
-
|
|
3
|
|
-BUGS:
|
|
4
|
|
-; Slugs aren't unicode safe. See [reddit discussion](http://www.reddit.com/r/lisp/comments/yvh6g/coleslaw_jekylllike_static_blogware_in_500_lines/) and [mozilla code](https://github.com/mozilla/unicode-slugify/blob/master/slugify/__init__.py).
|
|
5
|
|
-
|
|
6
|
1
|
TODO:
|
|
7
|
2
|
Coleslaw.next
|
|
8
|
3
|
; Add HACKING.md docs, i.e. formalize workflow+releases. No more landing broken stuff on master!
|
|
9
|
|
-; Add SHOUT content type.
|
|
10
|
4
|
;; needs: shout template/render function. Twitter\Disqus integration with shouts?
|
|
11
|
5
|
;; Rename index.posts to something else?
|
|
12
|
|
-; Document theming/template system.
|
|
13
|
|
-; unit tests
|
|
14
|
6
|
; Incremental compilation: only "touched" posts+tags+months and by-n. -> 1.0
|
|
15
|
|
-
|
|
16
|
|
-;; DOCUMENTATION
|
|
17
|
|
-;; A theme directory should be named after the theme and contain *.tmpl files
|
|
18
|
|
-;; that define the following functions in a coleslaw.theme.$NAME namespace.
|
|
19
|
|
-;; Required templates:
|
|
20
|
|
-;; {template base}
|
|
21
|
|
-;; {template post}
|
|
22
|
|
-;; {template index}
|
|
23
|
|
-
|
Brit Butler