diff --git a/_config/routes.yml b/_config/routes.yml
new file mode 100644
index 0000000..bc951bd
--- /dev/null
+++ b/_config/routes.yml
@@ -0,0 +1,6 @@
+---
+Name: staticpublisherroutes
+---
+Director:
+  rules:
+    'dev/buildcache': '->dev/tasks/RebuildStaticCacheTask'
diff --git a/docs/en/StaticPublisher.md b/docs/en/StaticPublisher.md
index 4104658..6465fd5 100644
--- a/docs/en/StaticPublisher.md
+++ b/docs/en/StaticPublisher.md
@@ -449,20 +449,20 @@ you can build the static HTML files. This is done by the `RebuildStaticCacheTask
 Execution via URL
 
 ```
-http://www.yoursite.com/dev/buildcache?flush=1
+http://www.yoursite.com/dev/tasks/RebuildStaticCacheTask?flush=1
 ```
 
 Execution on CLI (via [sake](framework/en/topics/commandline))
 ```
-sake dev/buildcache flush=1
+sake dev/tasks/RebuildStaticCacheTask flush=1
 ```
 
 Depending on which extension you've set up for your `SiteTree` (`FilesystemPublisher`
 or `RsyncMultiHostPublisher`), the method `publishPages()` either stores the generated
 HTML-files on the server's filesystem, or deploys them to other servers via rsync.
 
-It is advisable to set `dev/buildcache` up as an automated task (e.g. unix cron)
-which continually rebuilds and redeploys the cache. 
+It is advisable to set `dev/tasks/RebuildStaticCacheTask` up as an automated 
+task (e.g. unix cron) which continually rebuilds and redeploys the cache. 
 
 ## Related