Adding additional files to blog/theme root like robots.txt and favicon (and the million app icons)

[BorisKourt]

If I leave a robots.txt or any app icon related images (apple-touch-icon.png etc.) in the root of the theme or the blog they get discarded on build. Do I need to make a small plugin to specify which files to move/generate/keep? (Perhaps from looking at gh-pages)

Or are there configuration options available in .coleslawrc?

[vdikan]

If still relevant :)
I think easiest way is to patch (compile-blog) in the coleslaw.lisp:

--- a/src/coleslaw.lisp
+++ b/src/coleslaw.lisp
@@ -35,7 +35,12 @@
                          (merge-pathnames "js" theme-dir)
                          (repo-path "static")))
         (when (probe-file dir)
-          (run-program "rsync --delete -raz ~a ." dir))))
+          (run-program "rsync --delete -raz ~a ." dir)))
+      (cl-fad:walk-directory            ; sync files from `root-static`
+       (repo-path "root-static")        ; to the root of staging dir
+       #'(lambda (file)
+           (run-program "rsync --delete -raz ~a ." file))
+       :if-does-not-exist :ignore))
     (do-subclasses (ctype content)
       (publish ctype))
     (do-subclasses (itype index)

I use root-static as a hardcoded name for dir in the blog repo, same as static is hardcoded directory for other static files that do not necessarily need to show up in the root. I'm totally fine with both names.