21 files changed, 10 insertions, 36 deletions
diff --git a/content/en/blog/news/20191006-new-site.md b/content/en/blog/20191006-new-site.md
index c04ff2d..c04ff2d 100644
--- a/content/en/blog/news/20191006-new-site.md
+++ b/content/en/blog/20191006-new-site.md
diff --git a/content/en/blog/news/20200116-hn.md b/content/en/blog/20200116-hn.md
index b80a7bd..b80a7bd 100644
--- a/content/en/blog/news/20200116-hn.md
+++ b/content/en/blog/20200116-hn.md
diff --git a/content/en/blog/news/20200212-ecmp.md b/content/en/blog/20200212-ecmp.md
index 019b40d..019b40d 100644
--- a/content/en/blog/news/20200212-ecmp.md
+++ b/content/en/blog/20200212-ecmp.md
diff --git a/content/en/blog/news/20200216-ecmp.md b/content/en/blog/20200216-ecmp.md
index ce632c9..ce632c9 100644
--- a/content/en/blog/news/20200216-ecmp.md
+++ b/content/en/blog/20200216-ecmp.md
diff --git a/content/en/blog/news/20200502-frcp.md b/content/en/blog/20200502-frcp.md
index 28c5794..28c5794 100644
--- a/content/en/blog/news/20200502-frcp.md
+++ b/content/en/blog/20200502-frcp.md
diff --git a/content/en/blog/news/20200507-python-lb.png b/content/en/blog/20200507-python-lb.png
index 89e710e..89e710e 100644
--- a/content/en/blog/news/20200507-python-lb.png
+++ b/content/en/blog/20200507-python-lb.png
diff --git a/content/en/blog/news/20200507-python.md b/content/en/blog/20200507-python.md
index d4b3504..2b05c91 100644
--- a/content/en/blog/news/20200507-python.md
+++ b/content/en/blog/20200507-python.md
@@ -65,7 +65,7 @@ released after the weekend.
 Oh, and here is a picture of Ouroboros load-balancing between the C (top right)
 and Python (top left) implementations using the C and Python clients:
 
-{{<figure width="60%" src="/blog/news/20200507-python-lb.png">}}
+{{<figure width="60%" src="/blog/20200507-python-lb.png">}}
 
 Can't wait to get the full API done!
 
diff --git a/content/en/blog/news/20201212-congestion-avoidance.md b/content/en/blog/20201212-congestion-avoidance.md
index f395a4f..0b010c5 100644
--- a/content/en/blog/news/20201212-congestion-avoidance.md
+++ b/content/en/blog/20201212-congestion-avoidance.md
@@ -334,7 +334,7 @@ big oscillations because of AIMD), when switching the flows on the
 clients on and off which is on par with DCTCP and not unexpected
 keeping in mind the similarities between the algorithms:
 
-{{<figure width="60%" src="/blog/news/20201212-congestion.png">}}
+{{<figure width="60%" src="/blog/20201212-congestion.png">}}
 
 The periodic "gaps" were not seen at the ocbr endpoint applicationand
 may have been due to tcpdump not capturing everything that those
diff --git a/content/en/blog/news/20201212-congestion.png b/content/en/blog/20201212-congestion.png
index 8e5b89f..8e5b89f 100644
--- a/content/en/blog/news/20201212-congestion.png
+++ b/content/en/blog/20201212-congestion.png
diff --git a/content/en/blog/news/20201219-congestion-avoidance.md b/content/en/blog/20201219-congestion-avoidance.md
index 7391091..240eb88 100644
--- a/content/en/blog/news/20201219-congestion-avoidance.md
+++ b/content/en/blog/20201219-congestion-avoidance.md
@@ -35,7 +35,7 @@ First, a quick refresh on the experiment layout, it's the the same
 4-node experiment as in the
 [previous post](/blog/2020/12/12/congestion-avoidance-in-ouroboros/#mb-ecn-in-action)
 
-{{<figure width="80%" src="/blog/news/20201219-exp.svg">}}
+{{<figure width="80%" src="/blog/20201219-exp.svg">}}
 
 I tried to draw the setup as best as I can in the figure above.
 
@@ -52,7 +52,7 @@ generated with our _constant bit rate_ ```ocbr``` tool trying to send
 about 80 Mbit/s of application-level throughput over the unicast
 layer.
 
-{{<figure width="80%" src="/blog/news/20201219-congestion.png">}}
+{{<figure width="80%" src="/blog/20201219-congestion.png">}}
 
 The graph above shows the bandwidth -- as captured on the congested
 100Mbit Ethernet link --, separated for each traffic flow, from the
@@ -142,7 +142,7 @@ from the "wire":
 
 ## The network protocol
 
-{{<figure width="80%" src="/blog/news/20201219-ws-0.png">}}
+{{<figure width="80%" src="/blog/20201219-ws-0.png">}}
 
 We will first have a look at packets captured around the point in time
 where the second (red) flow enters the network, about 14 seconds into
@@ -194,7 +194,7 @@ endpoint for the ```ocbr``` server.
 
 ## The flow request
 
-{{<figure width="80%" src="/blog/news/20201219-ws-1.png">}}
+{{<figure width="80%" src="/blog/20201219-ws-1.png">}}
 
 The first "red" packet that was captured is the one for the flow
 allocation request, **FLOW REQUEST**[^6]. As mentioned before, the
@@ -235,7 +235,7 @@ relevant for this message.
 
 ## The flow reply
 
-{{<figure width="80%" src="/blog/news/20201219-ws-2.png">}}
+{{<figure width="80%" src="/blog/20201219-ws-2.png">}}
 
 Now, the **FLOW REPLY** message for our request. It originates our
 machine, so you will notice that the TTL is the starting value of 60.
@@ -247,7 +247,7 @@ for this flow.
 
 ## Congestion / flow update
 
-{{<figure width="80%" src="/blog/news/20201219-ws-3.png">}}
+{{<figure width="80%" src="/blog/20201219-ws-3.png">}}
 
 Now a quick look at the congestion avoidance mechanisms. The
 information for the Additive Increase / Multiple Decrease algorithm is
@@ -256,7 +256,7 @@ active, they experience congestion since the requested bandwidth from
 the two ```ocbr``` clients (180Mbit) exceeds the 100Mbit link, and the
 figure above shows a packet marked with an ECN value of 11.
 
-{{<figure width="80%" src="/blog/news/20201219-ws-4.png">}}
+{{<figure width="80%" src="/blog/20201219-ws-4.png">}}
 
 When the packets on a flow experience congestion, the flow allocator
 at the endpoint (the one our _uni-s_ IPCP) will update the sender with
diff --git a/content/en/blog/news/20201219-congestion.png b/content/en/blog/20201219-congestion.png
index 5675438..5675438 100644
--- a/content/en/blog/news/20201219-congestion.png
+++ b/content/en/blog/20201219-congestion.png
diff --git a/content/en/blog/news/20201219-exp.svg b/content/en/blog/20201219-exp.svg
index 68e09e2..68e09e2 100644
--- a/content/en/blog/news/20201219-exp.svg
+++ b/content/en/blog/20201219-exp.svg
diff --git a/content/en/blog/news/20201219-ws-0.png b/content/en/blog/20201219-ws-0.png
index fd7a83a..fd7a83a 100644
--- a/content/en/blog/news/20201219-ws-0.png
+++ b/content/en/blog/20201219-ws-0.png
diff --git a/content/en/blog/news/20201219-ws-1.png b/content/en/blog/20201219-ws-1.png
index 0f07fd0..0f07fd0 100644
--- a/content/en/blog/news/20201219-ws-1.png
+++ b/content/en/blog/20201219-ws-1.png
diff --git a/content/en/blog/news/20201219-ws-2.png b/content/en/blog/20201219-ws-2.png
index 7cd8b7d..7cd8b7d 100644
--- a/content/en/blog/news/20201219-ws-2.png
+++ b/content/en/blog/20201219-ws-2.png
diff --git a/content/en/blog/news/20201219-ws-3.png b/content/en/blog/20201219-ws-3.png
index 2a6f6d5..2a6f6d5 100644
--- a/content/en/blog/news/20201219-ws-3.png
+++ b/content/en/blog/20201219-ws-3.png
diff --git a/content/en/blog/news/20201219-ws-4.png b/content/en/blog/20201219-ws-4.png
index 3a0ef8c..3a0ef8c 100644
--- a/content/en/blog/news/20201219-ws-4.png
+++ b/content/en/blog/20201219-ws-4.png
diff --git a/content/en/blog/_index.md b/content/en/blog/_index.md
index 43820eb..34904e5 100644
--- a/content/en/blog/_index.md
+++ b/content/en/blog/_index.md
@@ -1,13 +1,7 @@
 ---
-title: "Docsy Blog"
+title: "Developer Blog"
 linkTitle: "Blog"
 menu:
   main:
     weight: 30
 ---
-
-
-This is the **blog** section. It has two categories: News and Releases.
-
-Files in these directories will be listed in reverse chronological order.
-
diff --git a/content/en/blog/news/_index.md b/content/en/blog/news/_index.md
deleted file mode 100644
index c10cfa2..0000000
--- a/content/en/blog/news/_index.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: "News About Docsy"
-linkTitle: "News"
-weight: 20
----
diff --git a/content/en/blog/releases/_index.md b/content/en/blog/releases/_index.md
deleted file mode 100644
index b1d9eb4..0000000
--- a/content/en/blog/releases/_index.md
+++ /dev/null
@@ -1,8 +0,0 @@
-
----
-title: "New Releases"
-linkTitle: "Releases"
-weight: 20
----
-
-
diff --git a/content/en/blog/releases/upcoming.md b/content/en/blog/releases/upcoming.md
deleted file mode 100644
index f984380..0000000
--- a/content/en/blog/releases/upcoming.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-date: 2019-10-06
-title: "Plans for 0.16"
-linkTitle: "Ouroboros 0.16"
-description: "Ouroboros 0.16"
-author: Dimitri Staessens
----