feat: new auto images (#35)

* feat: new auto images * feat: regenerate images * feat: use the generator everywhere * fix: simplify images
bkielbasa · Dec 30, 2021 · 17a0936 · 17a0936
1 parent 84486ce
commit 17a0936
Show file tree

Hide file tree

Showing 140 changed files with 143 additions and 30 deletions.
diff --git a/.hugo_build.lock b/.hugo_build.lock
diff --git a/Makefile b/Makefile
@@ -2,3 +2,6 @@
 deploy:
 	hugo
 	aws s3 cp public s3://developer20.com/ --recursive --acl public-read
+
+featured:
+	bash ./generate-featured.sh
diff --git a/baseImg.png b/baseImg.png
diff --git a/content/post/add-header-to-every-request-in-go/featured.jpeg b/content/post/add-header-to-every-request-in-go/featured.jpeg
diff --git a/content/post/add-header-to-every-request-in-go/featured.png b/content/post/add-header-to-every-request-in-go/featured.png
diff --git a/content/post/add-header-to-every-request-in-go/index.md b/content/post/add-header-to-every-request-in-go/index.md
@@ -1,9 +1,10 @@
 ---
 title: "Add header to every request in Go"
 publishdate: 2020-07-21
+
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 
 short: Making changes to all HTTP requests can be handy. You may want to add an API key or some information about the sender like app version etc. No matter why you want to do that you have a few options to achieve the goal.
 

diff --git a/content/post/an-agony-of-trying-to-do-the-job/featured.png b/content/post/an-agony-of-trying-to-do-the-job/featured.png
diff --git a/...an-agony-of-trying-to-do-the-job.markdown → ...an-agony-of-trying-to-do-the-job/index.md b/...an-agony-of-trying-to-do-the-job.markdown → ...an-agony-of-trying-to-do-the-job/index.md
@@ -2,6 +2,10 @@
 title: An agony of trying to do the job
 publishdate: 2017-12-27
 
+resources:
+    - name: header
+    - src: featured.png
+
 ---
 I’ll tell you a story of Igor. Igor is a web developer. He’s a young man with a girlfriend and some ambitious plan in the future. Igor sit at his desk because he has some work to do. In front of him is a PC. He turns it on and sees some system updates. 30 minutes have passed, and he can see his desktop with a beautiful wallpaper. Funny cats always make his day better. Some people are walking around his working desk, talking and drinking coffee. A typical day.
 

diff --git a/content/post/be-aware-of-coping-in-go/featured.png b/content/post/be-aware-of-coping-in-go/featured.png
diff --git a/...nt/post/be-aware-of-coping-in-go.markdown → ...nt/post/be-aware-of-coping-in-go/index.md b/...nt/post/be-aware-of-coping-in-go.markdown → ...nt/post/be-aware-of-coping-in-go/index.md
diff --git a/content/post/books-i-read-in-2018/featured.png b/content/post/books-i-read-in-2018/featured.png
diff --git a/content/post/books-i-read-in-2018.markdown → content/post/books-i-read-in-2018/index.md b/content/post/books-i-read-in-2018.markdown → content/post/books-i-read-in-2018/index.md
@@ -2,6 +2,10 @@
 title: Books I read in 2018
 publishdate: 2019-01-07
 
+resources:
+    - name: header
+    - src: featured.png
+
 ---
 I’m glad that this year I read so many valuable books. I want to share with you with the most interesting items which you may find interesting too.
 ## [Getting Things Programmed](https://helion.pl/ksiazki/getting-things-programmed-droga-do-efektywnosci-michal-bartyzel,droppp.htm#format/e)

diff --git a/content/post/custom-go-linter/featured.jpg b/content/post/custom-go-linter/featured.jpg
diff --git a/content/post/custom-go-linter/featured.png b/content/post/custom-go-linter/featured.png
diff --git a/content/post/custom-go-linter/index.md b/content/post/custom-go-linter/index.md
@@ -3,7 +3,7 @@ title: "Writing custom linter in Go"
 publishdate: 2021-03-31
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 categories: 
     - Golang
     - Programming

diff --git a/content/post/entity-and-value-object/featured.png b/content/post/entity-and-value-object/featured.png
diff --git a/...ent/post/entity-and-value-object.markdown → ...ent/post/entity-and-value-object/index.md b/...ent/post/entity-and-value-object.markdown → ...ent/post/entity-and-value-object/index.md
@@ -2,6 +2,11 @@
 title: Entity and value object  
 publishdate: 2018-08-04
 categories: [Programming]
+
+resources:
+    - name: header
+    - src: featured.png
+
 tags:
   - ddd
   - entity

diff --git a/content/post/extracting-the-business-logic-project/featured.jpg b/content/post/extracting-the-business-logic-project/featured.jpg
diff --git a/content/post/extracting-the-business-logic-project/featured.png b/content/post/extracting-the-business-logic-project/featured.png
diff --git a/content/post/extracting-the-business-logic-project/index.md b/content/post/extracting-the-business-logic-project/index.md
@@ -3,7 +3,7 @@ title: "Extracting the business logic - the project"
 publishdate: 2021-01-12
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 categories:
     - Golang
 tags:

diff --git a/content/post/garnish-simple-varnish-in-go/featured.jpg b/content/post/garnish-simple-varnish-in-go/featured.jpg
diff --git a/content/post/garnish-simple-varnish-in-go/featured.png b/content/post/garnish-simple-varnish-in-go/featured.png
diff --git a/content/post/garnish-simple-varnish-in-go/index.md b/content/post/garnish-simple-varnish-in-go/index.md
@@ -12,7 +12,7 @@ tags:
   - caching
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 ---
 
 The varnish is a well-known HTTP accelerator. As the continuation of the [GoInPractice](https://developer20.com/categories/GoInPractice/) series, today I’ll show how you can build a simple (and naive) varnish implementation in Go. Some of the code is reused from [Writing a reverse proxy](https://developer20.com/writing-proxy-in-go/) so if you don’t understand something, I recommend taking a look at the blog post.

diff --git a/content/post/go-context/featured.jpg b/content/post/go-context/featured.jpg
diff --git a/content/post/go-context/featured.png b/content/post/go-context/featured.png
diff --git a/content/post/go-context/index.md b/content/post/go-context/index.md
@@ -9,7 +9,7 @@ tags:
     - context
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 ---
 
 The `context` package in Go is quite simple and well-known. On the other hand, there are some misunderstandings while using it. Today, I'll try to explain all the most popular concerns and make more clear when and how use the `Context`.

diff --git a/content/post/go-deeper-database-connection-pool/featured.jpg b/content/post/go-deeper-database-connection-pool/featured.jpg
diff --git a/content/post/go-deeper-database-connection-pool/featured.png b/content/post/go-deeper-database-connection-pool/featured.png
diff --git a/...r-database-connection-pool/index.markdown → ...-deeper-database-connection-pool/index.md b/...r-database-connection-pool/index.markdown → ...-deeper-database-connection-pool/index.md
@@ -4,7 +4,7 @@ publishdate: 2019-01-25
 categories: [Golang, Programming]
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 tags:
   - golang
   - database

diff --git a/content/post/go-mod-replace/featured.png b/content/post/go-mod-replace/featured.png
diff --git a/content/post/go-mod-replace/index.md b/content/post/go-mod-replace/index.md
@@ -7,9 +7,10 @@ categories:
 tags:
   - golang
   - modules
+
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 ---
 
 Sometimes, we may want to use a library but a slightly modified version. It happens very often when we develop the library but test it in the context of an application. Go has a handy mechanism in go modules that can help us with it.

diff --git a/content/post/go-web-frameworks/featured.jpg b/content/post/go-web-frameworks/featured.jpg
diff --git a/content/post/go-web-frameworks/featured.png b/content/post/go-web-frameworks/featured.png
diff --git a/content/post/go-web-frameworks/index.md b/content/post/go-web-frameworks/index.md
@@ -1,9 +1,11 @@
 ---
 title: Go web frameworks
 publishdate: 2020-08-10
+
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
+
 categories:
     - Golang
 tags:

diff --git a/content/post/gogoconf-2019/featured.png b/content/post/gogoconf-2019/featured.png
diff --git a/content/post/gogoconf-2019.markdown → content/post/gogoconf-2019/index.md b/content/post/gogoconf-2019.markdown → content/post/gogoconf-2019/index.md
@@ -4,6 +4,10 @@ publishdate: 2019-07-05
 tags:
   - golang
   - conference
+
+resources:
+    - name: header
+    - src: featured.png
 ---
 Recently I've been on the GoGoConf conference in Cracow. It was a cool opportunity to learn more and meet interesting persons. Today I'll tell you about my thoughts regarding every talk from 2019 edition. Most of the talks don't have video available yet but when the videos will be published I'll update the post.
 

diff --git a/content/post/golang-tips-and-trics-i/featured.png b/content/post/golang-tips-and-trics-i/featured.png
diff --git a/...ent/post/golang-tips-and-trics-i.markdown → ...ent/post/golang-tips-and-trics-i/index.md b/...ent/post/golang-tips-and-trics-i.markdown → ...ent/post/golang-tips-and-trics-i/index.md
@@ -4,6 +4,10 @@ publishdate: 2019-03-04
 categories: [Golang, Programming]
 tags:
   - golang
+
+resources:
+    - name: header
+    - src: featured.png
 ---
 
 You should use the package `github.com/pkg/errors` instead of `errors` package for errors in your applications. The default package lacks a few things like:

diff --git a/content/post/golang-tips-and-trics-ii/featured.png b/content/post/golang-tips-and-trics-ii/featured.png
diff --git a/...nt/post/golang-tips-and-trics-ii.markdown → ...nt/post/golang-tips-and-trics-ii/index.md b/...nt/post/golang-tips-and-trics-ii.markdown → ...nt/post/golang-tips-and-trics-ii/index.md
@@ -6,6 +6,9 @@ tags:
   - golang
   - interfaces
 
+resources:
+    - name: header
+    - src: featured.png
 ---
 
 When it comes to interfaces, a good practice is to create an interface where you'll use it. Creating interfaces in advanced is not recommended in Go. There are two exceptions:

diff --git a/content/post/golang-tips-and-trics-iii/featured.png b/content/post/golang-tips-and-trics-iii/featured.png
diff --git a/content/post/golang-tips-and-trics-iii.md → ...t/post/golang-tips-and-trics-iii/index.md b/content/post/golang-tips-and-trics-iii.md → ...t/post/golang-tips-and-trics-iii/index.md
@@ -6,6 +6,9 @@ tags:
   - golang
   - graceful shutdown
 
+resources:
+    - name: header
+    - src: featured.png
 ---
 In the microservices' world, one thing what's worth considering is a graceful shutdown. This is important to not lose data while shutting down a container. The container orchestrator like Kubernetes can restart the container by sending `SIGTERM` or `SIGINT` signal. Those signals can be handled to safely close all connections and finish background tasks.
 

diff --git a/content/post/golang-tips-and-trics-iv/featured.png b/content/post/golang-tips-and-trics-iv/featured.png
diff --git a/content/post/golang-tips-and-trics-iv.md → ...nt/post/golang-tips-and-trics-iv/index.md b/content/post/golang-tips-and-trics-iv.md → ...nt/post/golang-tips-and-trics-iv/index.md
diff --git a/content/post/golang-tips-and-trics-v/featured.png b/content/post/golang-tips-and-trics-v/featured.png
diff --git a/...ent/post/golang-tips-and-trics-v.markdown → ...ent/post/golang-tips-and-trics-v/index.md b/...ent/post/golang-tips-and-trics-v.markdown → ...ent/post/golang-tips-and-trics-v/index.md
@@ -6,6 +6,9 @@ tags:
   - golang
   - strucs
 
+resources:
+    - name: header
+    - src: featured.png
 ---
 While working with structures, there's a possibility to initialize the structure without providing the keys of fields.
 

diff --git a/content/post/golang-tips-and-trics-vi/featured.png b/content/post/golang-tips-and-trics-vi/featured.png
diff --git a/...nt/post/golang-tips-and-trics-vi.markdown → ...nt/post/golang-tips-and-trics-vi/index.md b/...nt/post/golang-tips-and-trics-vi.markdown → ...nt/post/golang-tips-and-trics-vi/index.md
@@ -6,6 +6,9 @@ tags:
   - golang
   - tests
 
+resources:
+    - name: header
+    - src: featured.png
 ---
 
 

diff --git a/content/post/golang-tips-and-trics-vii/featured.png b/content/post/golang-tips-and-trics-vii/featured.png
diff --git a/...t/post/golang-tips-and-trics-vii.markdown → ...t/post/golang-tips-and-trics-vii/index.md b/...t/post/golang-tips-and-trics-vii.markdown → ...t/post/golang-tips-and-trics-vii/index.md
@@ -6,6 +6,10 @@ tags:
   - golang
   - modules
   - proxy
+
+resources:
+    - name: header
+    - src: featured.png
 ---
 
 In Go 1.13 all modules are provided using a proxy. The proxy caches dependencies what helps to make sure that the version of an external dependencies will never change. If the vendor remove the version and create a new one with the same version, only the first one will be provided.

diff --git a/content/post/grpc-ssl/featured.jpg b/content/post/grpc-ssl/featured.jpg
diff --git a/content/post/grpc-ssl/featured.png b/content/post/grpc-ssl/featured.png
diff --git a/content/post/grpc-ssl/index.md b/content/post/grpc-ssl/index.md
@@ -9,7 +9,7 @@ tags:
   - grpc
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 ---
 
 gRPC supports [authentication](https://grpc.io/docs/guides/auth/). Adding it to your project is simple. All you have to do is configure it with just a few lines of code. One of the authentication types that gRPC supports is SSL/TLS. From the server-side, the code looks like this:

diff --git a/content/post/history-of-www/featured.png b/content/post/history-of-www/featured.png
diff --git a/content/post/history-of-www.markdown → content/post/history-of-www/index.md b/content/post/history-of-www.markdown → content/post/history-of-www/index.md
@@ -2,6 +2,9 @@
 title: "History of WWW"
 publishdate: 2018-05-02
 
+resources:
+    - name: header
+    - src: featured.png
 ---
 The history of the WWW wasn’t simple and still isn’t. In the beginning, it was a complete mess. Every browser tried to meet developers halfway without any standards or cooperation with other web browser’s developers.
 

diff --git a/content/post/how-i-organize-packages-in-go/featured.png b/content/post/how-i-organize-packages-in-go/featured.png
diff --git a/...ent/post/how-i-organize-packages-in-go.md → ...st/how-i-organize-packages-in-go/index.md b/...ent/post/how-i-organize-packages-in-go.md → ...st/how-i-organize-packages-in-go/index.md
@@ -3,6 +3,9 @@ title: How I organize packages in Go
 publishDate: 2019-08-22
 categories: [Golang, Programming]
 tags: [golang]
+resources:
+    - name: header
+    - src: featured.png
 
 ---
 

diff --git a/content/post/how-to-name-exceptions-its-not-so-obvious/featured.png b/content/post/how-to-name-exceptions-its-not-so-obvious/featured.png
diff --git a/...me-exceptions-its-not-so-obvious.markdown → ...me-exceptions-its-not-so-obvious/index.md b/...me-exceptions-its-not-so-obvious.markdown → ...me-exceptions-its-not-so-obvious/index.md
@@ -2,6 +2,10 @@
 title: "How to name exceptions? It’s not so obvious..."
 publishDate: 2018-04-02
 
+resources:
+    - name: header
+    - src: featured.png
+
 ---
 Naming things is one of the most difficult things in our job. Naming exceptions are even more complicated because exceptions are not regular classes. In this article, I’ll tell you a bit about naming conventions I’ve found and tell pros and cons of them.
 ## The ‘Exception’ suffix. To add or not to add

diff --git a/content/post/how-to-send-multiple-variables-via-channel-in-golang/featured.png b/content/post/how-to-send-multiple-variables-via-channel-in-golang/featured.png
diff --git a/...-variables-via-channel-in-golang.markdown → ...-variables-via-channel-in-golang/index.md b/...-variables-via-channel-in-golang.markdown → ...-variables-via-channel-in-golang/index.md
@@ -7,6 +7,9 @@ tags:
   - channels
   - concurrency
 
+resources:
+    - name: header
+    - src: featured.png
 ---
 Channels in golang are referenced type. It means that they are references to a place in the memory. The information can be used to achieve the goal.
 

diff --git a/content/post/how-to-structure-go-code/featured.jpg b/content/post/how-to-structure-go-code/featured.jpg
diff --git a/content/post/how-to-structure-go-code/featured.png b/content/post/how-to-structure-go-code/featured.png
diff --git a/content/post/how-to-structure-go-code/index.md b/content/post/how-to-structure-go-code/index.md
@@ -8,7 +8,7 @@ tags:
     - golang
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 ---
 
 > Programs should be written for people to read, and only incidentally for machines to execute - Abelson and Sussman

diff --git a/content/post/http-connection-livetime/featured.jpg b/content/post/http-connection-livetime/featured.jpg
diff --git a/content/post/http-connection-livetime/featured.png b/content/post/http-connection-livetime/featured.png
diff --git a/content/post/http-connection-livetime/index.md b/content/post/http-connection-livetime/index.md
@@ -3,7 +3,7 @@ title: "HTTP context livetime"
 publishdate: 2021-08-09
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 categories: 
     - Golang
 tags:

diff --git a/content/post/i-talk-to-scammers/featured.jpg b/content/post/i-talk-to-scammers/featured.jpg
diff --git a/content/post/i-talk-to-scammers/featured.png b/content/post/i-talk-to-scammers/featured.png
diff --git a/content/post/i-talk-to-scammers/index.md b/content/post/i-talk-to-scammers/index.md
@@ -3,7 +3,7 @@ title: "I talk to spammers. Here is what I found"
 publishdate: 2020-08-25
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 categories:
     - General
 tags:

diff --git a/content/post/i-want-to-learn-go/featured.jpg b/content/post/i-want-to-learn-go/featured.jpg
diff --git a/content/post/i-want-to-learn-go/featured.png b/content/post/i-want-to-learn-go/featured.png
diff --git a/content/post/i-want-to-learn-go/index.md b/content/post/i-want-to-learn-go/index.md
@@ -3,7 +3,7 @@ title: "I want to learn Go - how to start?"
 publishdate: 2019-12-09
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 categories:
     - Golang
 tags:

diff --git a/content/post/indexing-in-mysql/featured.png b/content/post/indexing-in-mysql/featured.png
diff --git a/content/post/indexing-in-mysql.markdown → content/post/indexing-in-mysql/index.md b/content/post/indexing-in-mysql.markdown → content/post/indexing-in-mysql/index.md
@@ -7,6 +7,11 @@ tags:
   - indexes
   - b-tree-plus
   - explain
+
+resources:
+    - name: header
+    - src: featured.png
+
 ---
 Why do we use indexes? Searching through a row in a sorted file with N length takes O(log2N) comparisons and the same number of reads from a filesystem which is heavy itself. However, tables in databases are not sorted which complicates the operation, Especially, if you have a lot of reads, updates and deletions on them. Writing the sorted version of the file (table) would dramatically slow the database down. There is one more thing which makes it even more complicated: every table may be sorted in more than one order. That’s why we use indexes which hold only attributes used in sorting and a reference to the place where the data are kept.
 

diff --git a/content/post/is-my-interface-too-big/featured.jpg b/content/post/is-my-interface-too-big/featured.jpg
diff --git a/content/post/is-my-interface-too-big/featured.png b/content/post/is-my-interface-too-big/featured.png
diff --git a/content/post/is-my-interface-too-big/index.md b/content/post/is-my-interface-too-big/index.md
@@ -3,7 +3,7 @@ title: "Is my interface too big?"
 publishdate: 2020-10-28
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 categories:
     - Golang
 tags:

diff --git a/content/post/learning-on-mistakes/featured.png b/content/post/learning-on-mistakes/featured.png
diff --git a/content/post/learning-on-mistakes.markdown → content/post/learning-on-mistakes/index.md b/content/post/learning-on-mistakes.markdown → content/post/learning-on-mistakes/index.md
@@ -1,6 +1,10 @@
 ---
 title: Learning On Mistakes
 publishDate: 2019-03-25
+resources:
+    - name: header
+    - src: featured.png
+
 ---
 There are many situations which can cause unavailability. One of them can be a bug in a software, bad architecture design decisions or even [a human error](https://aws.amazon.com/message/41926/). Depending on how the numbers are calculated, from [22%](https://cloudscene.com/news/2017/07/datacenterdowntime/) to even [70%](https://www.cw.com.hk/it-hk/uptime-institute-70-dc-outages-due-to-human-error) of outages are caused by human error. Software engineers, DevOps or administrators cannot prevent all the outages but we can learn from ourselves to improve the stability and reliability of systems we are creating. In this article, I will present how Brainly learns on his mistakes to improve the stability and latency of its infrastructure.
 

diff --git a/content/post/mutational-tests/featured.png b/content/post/mutational-tests/featured.png
diff --git a/content/post/mutational-tests.markdown → content/post/mutational-tests/index.md b/content/post/mutational-tests.markdown → content/post/mutational-tests/index.md
@@ -5,6 +5,9 @@ categories: [Programming]
 tags:
   - tests
   - mutational testing
+resources:
+    - name: header
+    - src: featured.png
 ---
 When you have a very simple application it’s not so important to test every edge case but in a project, in the very complex domain, the priority of it will increase. The more high-quality the tests, the more high-quality the code. Mutational tests will help you with making sure you did not miss some a variant of the flow in your code.
 

diff --git a/content/post/oauth2-and-go/featured.jpg b/content/post/oauth2-and-go/featured.jpg
diff --git a/content/post/oauth2-and-go/featured.png b/content/post/oauth2-and-go/featured.png
diff --git a/content/post/oauth2-and-go/index.md b/content/post/oauth2-and-go/index.md
@@ -3,7 +3,7 @@ title: "OAuth2 and Go"
 publishdate: 2020-03-09
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 categories:
     - Golang
     - GoInPractice

diff --git a/content/post/periodically-restarting-apps-on-k8s/featured.jpg b/content/post/periodically-restarting-apps-on-k8s/featured.jpg
diff --git a/content/post/periodically-restarting-apps-on-k8s/featured.png b/content/post/periodically-restarting-apps-on-k8s/featured.png
diff --git a/content/post/periodically-restarting-apps-on-k8s/index.md b/content/post/periodically-restarting-apps-on-k8s/index.md
@@ -3,7 +3,7 @@ title: "Periodically restarting apps on Kubernetes"
 publishdate: 2021-04-12
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 categories:
     - DevOps
 tags:

diff --git a/content/post/pointer-and-value-semantics-in-go/featured.jpg b/content/post/pointer-and-value-semantics-in-go/featured.jpg
diff --git a/content/post/pointer-and-value-semantics-in-go/featured.png b/content/post/pointer-and-value-semantics-in-go/featured.png
diff --git a/content/post/pointer-and-value-semantics-in-go/index.md b/content/post/pointer-and-value-semantics-in-go/index.md
@@ -5,7 +5,7 @@ categories: [Golang, Programming]
 publishDate: 2020-06-29
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 
 tags:
  - golang

diff --git a/content/post/refactoring-for-better-testability/featured.jpg b/content/post/refactoring-for-better-testability/featured.jpg
diff --git a/content/post/refactoring-for-better-testability/featured.png b/content/post/refactoring-for-better-testability/featured.png
diff --git a/content/post/refactoring-for-better-testability/index.md b/content/post/refactoring-for-better-testability/index.md
@@ -3,7 +3,7 @@ title: "Refactoring for better testability"
 publishdate: 2020-11-17
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 categories:
     - Golang
 tags:

diff --git a/content/post/scientific-method/featured.png b/content/post/scientific-method/featured.png
diff --git a/content/post/scientific-method.markdown → content/post/scientific-method/index.md b/content/post/scientific-method.markdown → content/post/scientific-method/index.md
@@ -5,6 +5,10 @@ categories: [Programming]
 tags:
   - tests
   - scientific-method
+
+resources:
+    - name: header
+    - src: featured.png
 ---
 In 50′ and 60′ input data for programs from those years were written on paper tapes or punch cards. Writing code, compiling and testing loop took from a few hours to even few days. It was the beginning of programming we know it.
 

diff --git a/content/post/services-in-ddd-finally-explained/featured.jpg b/content/post/services-in-ddd-finally-explained/featured.jpg
diff --git a/content/post/services-in-ddd-finally-explained/featured.png b/content/post/services-in-ddd-finally-explained/featured.png
diff --git a/content/post/services-in-ddd-finally-explained/index.md b/content/post/services-in-ddd-finally-explained/index.md
@@ -6,7 +6,7 @@ tags:
   - ddd
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 ---
 I’ve noticed that there is always a challenge of understanding what services are in a context of Domain-Driven Development and what is the difference between a service in an application, domain, and infrastructure layer.
 

diff --git a/content/post/software2.0/featured.png b/content/post/software2.0/featured.png
diff --git a/content/post/software2.0.markdown → content/post/software2.0/index.md b/content/post/software2.0.markdown → content/post/software2.0/index.md
@@ -2,6 +2,9 @@
 title: Software 2.0
 publishdate: 2019-05-24
 
+resources:
+    - name: header
+    - src: featured.png
 ---
 
 There are, at least, two excellent articles about Software 2.0. [Andrzej Karpathy](https://medium.com/@karpathy/software-2-0-a64152b37c35) and [Carlos E. Perez](https://medium.com/intuitionmachine/is-deep-learning-software-2-0-cc7ad46b138f) wrote blog posts which cover the topic. In this article, I will explain how I understand the term “Software 2.0” what, I hope, will give you a different point of view on the main topic.

diff --git a/content/post/summary-of-2019/featured.jpg b/content/post/summary-of-2019/featured.jpg
diff --git a/content/post/summary-of-2019/featured.png b/content/post/summary-of-2019/featured.png
diff --git a/content/post/summary-of-2019/index.md b/content/post/summary-of-2019/index.md
@@ -3,7 +3,7 @@ title: "Summary of 2019"
 publishdate: 2020-01-01
 resources:
     - name: header
-    - src: featured.jpg
+    - src: featured.png
 ---
 
 This is the very first time I write a summary of a year. I feel that today is the day I should start doing it and that some digits may be interesting for some people.

diff --git a/content/post/tcp-scanner-in-go/featured.jpg b/content/post/tcp-scanner-in-go/featured.jpg
diff --git a/content/post/tcp-scanner-in-go/featured.png b/content/post/tcp-scanner-in-go/featured.png
-Original file line number
+Diff line change
@@ Expand Up / @@ -6,6 +6,9 @@ tags: @@
       - golang
       - tests
+    resources:
+        - name: header
+        - src: featured.png
     ---
@@ Expand Down @@