diff --git a/.drone.yml b/.drone.yml
index 9603d76..dc687aa 100644
--- a/.drone.yml
+++ b/.drone.yml
@@ -1,6 +1,6 @@
 kind: pipeline
 type: docker
-name: default
+name: Blog build and release
 
 steps:
 - name: build
@@ -11,8 +11,6 @@ steps:
 - name: docker
   image: plugins/docker
   settings:
-    username:
-    password:
     repo: registry.while-false.de/blog
     tags:
       - 'latest'
diff --git a/content/blog/003-writing-articles/index.md b/content/blog/003-writing-articles/index.md
index 28ba9a2..cec5c9d 100644
--- a/content/blog/003-writing-articles/index.md
+++ b/content/blog/003-writing-articles/index.md
@@ -64,7 +64,7 @@ The worker then connected to the drone server. In the UI of the drone server I c
 ```yaml
 kind: pipeline
 type: docker
-name: default
+name: Blog build and release
 
 steps:
 - name: build
@@ -88,4 +88,10 @@ For now I only require two steps:
 1. build the gatsby project
 2. build the new docker image and push it to the registry
 
-Then, the last required step is to update the running container to the new version. The event on which to react would be the upload to the registry. There are some ways to handle this myself using webhooks, but as with the build trigger I decided to take a route a little more convenient: use [Watchtower](https://containrrr.github.io/watchtower). I tried watchtower before and don't feel comfortable blindly updating every container I run, so I [configure it to just watch the one blog container and update that automatically](https://containrrr.github.io/watchtower/container-selection/).
+An additional benefit of the drone build is this beatiful badge, every project has nowadays, conveniently prepared as markdown:
+[![Build Status](https://drone.while-false.de/api/badges/stephan/blog/status.svg)](https://drone.while-false.de/stephan/blog)
+```markdown
+[![Build Status](https://drone.while-false.de/api/badges/stephan/blog/status.svg)](https://drone.while-false.de/stephan/blog)
+```
+
+Then, the last required step is to update the running container to the new version. The event on which to react would be the upload to the registry. There are some ways to handle this myself using webhooks, but as with the build trigger I decided to take a route a little more convenient: use [Watchtower](https://containrrr.github.io/watchtower). I tried watchtower before and don't feel comfortable blindly updating every container I run, so I [configure it to just watch the one blog container and update that automatically](https://containrrr.github.io/watchtower/container-selection/). As I am the only one pushing updates of the image for the blog I can take precautions when I know something will break.