Procházet zdrojové kódy

Formatting tweaks.

Brit Butler před 10 roky
rodič
revize
deb2e556a4
2 změnil soubory, kde provedl 6 přidání a 3 odebrání
  1. 2 1
      README.md
  2. 4 2
      docs/hacking.md

+ 2 - 1
README.md

@@ -8,7 +8,8 @@
8 8
 > behind the enormous bushy eyebrows and that we called him Coleslaw. - anon
9 9
 
10 10
 Coleslaw is Flexible Lisp Blogware similar to [Frog](https://github.com/greghendershott/frog), [Jekyll](http://jekyllrb.com/), or [Hakyll](http://jaspervdj.be/hakyll/).
11
-Have questions? Come talk to us on **IRC in #coleslaw on Freenode**!
11
+
12
+Have questions? Come talk to us on IRC in **#coleslaw** on Freenode!
12 13
 
13 14
 ## Features
14 15
 

+ 4 - 2
docs/hacking.md

@@ -272,7 +272,7 @@ This is a initial set of commands which will be used to implement the first cole
272 272
 Imagine a executable `coleslaw`, the commands would be invoked like this: `coleslaw <commandname> <args>`
273 273
 
274 274
 * `build` generates the site. Takes:
275
-	* `--repo-dir`: first defaults to `~/.coleslawrc`'s `repo-dir` then to `./.coleslawrc`'s `repo-dir` and otherwise fails
275
+	* `--repo-dir`: first defaults to `~/.coleslawrc`'s `repo-dir` then to `.` and otherwise fails
276 276
 * `clean` removes the files from `output-dir` and `staging-dir`. Takes:
277 277
 	* `--repo-dir`: See above
278 278
 * `rebuild` is a shortcut for `clean` and then `build`. Takes:
@@ -288,7 +288,9 @@ Imagine a executable `coleslaw`, the commands would be invoked like this: `coles
288 288
 
289 289
 Ideas for later:
290 290
 
291
-* handle deployment with commands but because we've got many methods there would have to be an intelligent way of handling that.
291
+* Deployment. It would be nice to have but user needs vary greatly
292
+  and there are multiple deployment methods to support (heroku, s3,
293
+  gh-pages, git, etc). This will require some careful thought.
292 294
 
293 295
 ### Plugin Constraints
294 296