|
@@ -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
|
|