Entries list images (#6)

* feat: tiles with separated title

* adjusted images without background

content/posts/2016-from-idea-to-vision-own-scope-of-action-as-a-sliding-window/index.de.md

@@ -22,6 +22,8 @@ aliases:
  - "/posts/von-der-idee-zur-vision-der-eigene-handlungsspielraum-als-sliding-window/"
 ---
 
+![](2016-12-20-Sliding-Window-2.png)
+
 Viele Menschen haben Geschäftsideen. Oft sind es schlechte. Viel zu oft allerdings sind es utopische. [Es soll das nächste Uber für X werden. Oder noch besser: das nächste Instagram.](https://klaus-breyer.de/blog/entrepreneurship/das-neue-x-fuer-y-ueber-startups-die-plattformen-sein-wollen/1810)
 
 Dazu erst mal: Es ist super unrealistisch, ein solches Plattform-Geschäftsmodell wie Instagram mit dem Luxus mehrerer Millionen Venture Kapital für Reichweite aufzubauen, bevor Geld verdient werden muss. In Deutschland erst recht.

content/posts/2016-from-idea-to-vision-own-scope-of-action-as-a-sliding-window/index.md

@@ -19,6 +19,8 @@ tags:
  ]
 ---
 
+![](2016-12-20-Sliding-Window-2.png)
+
 Many people have business ideas. Often they are bad. Far too often, however, they are utopian. [It is supposed to become the next Uber for X. Or even better: the next Instagram.](https://klaus-breyer.de/blog/entrepreneurship/das-neue-x-fuer-y-ueber-startups-die-plattformen-sein-wollen/1810)
 
 First of all, it's incredibly unrealistic to build a platform business model like Instagram with the luxury of several million venture capital for reach before having to make money. Even more so in Germany.

content/posts/2022-shape-up-track-for-scrum-how-to-hack-a-process/index.md

@@ -48,7 +48,7 @@ So, the reasons for Shape Up are plenty. But furthermost, the implications for e
 
 Our Experiment: Augmenting a stable Scrum process with a [Shape Up](https://basecamp.com/shapeup) track to have the benefits of Shape Up without making a frightening "all-in" decision to ditch Scrum.
 
-![](2022-09-23-processes-scrum-vs.-shapeup-v2-process1.svg)
+![](2022-09-23-processes-scrum-vs.-shapeup-v2-process1.png)
 
 Before we get into more details, first, a bit of context: I am currently in the role of Tech Lead of a remote international team to develop a PWA product in the IIoT context.
 
@@ -64,7 +64,7 @@ Scrum working mode:
 
 It is not precisely [dual-track Scrum](https://www.agile-academy.com/de/product-owner/dual-track-scrum/), but a formal method was not necessary: We have excellent communication between the trades, and things are ready when the engineers need them.
 
-![](2022-11-16-processes-scrum-mini-waterfall.svg)
+![](2022-11-16-processes-scrum-mini-waterfall.png)
 
 Still, there was always more pre-work than Engineering could implement cleanly. And that always came with pressure in every engineer's mind. Also, in planning, tickets with medium priority were pushed to the next sprint, again and again.
 
@@ -95,7 +95,7 @@ While I am writing this article during the shaping phase for the second Shape Up
 
 _The builders formed what I would call a "temporary squad": Working focused on one thing while still being in exchange with their peers so that the overall architecture and visual esthetics do not suffer._
 
-![](2022-11-16-shape-up-teamsetup-squad.svg)
+![](2022-11-16-shape-up-teamsetup-squad.png)
 
 An exciting aspect emerged for the rest of the team (working within a regular Scrum track): Communication for them was also much more efficient when there were no longer 4 developers but only 2 developers who had to coordinate. ([Remember: communication increases exponentially](https://www.leadingagile.com/2018/02/lines-of-communication-team-size-applying-brooks-law/).)
 _This avoids situations where in backlog refinement/grooming, there are sometimes discussions that only concern some attendees: If 1 UI + 1 dev argues about a particular detail, it doesn't help that 2 UI designers (and sometimes even the other developers) are present for this time._
@@ -122,12 +122,12 @@ Things that we have not implemented from Shape Up:
 
 _To scale up Shape Up for larger Orgs, UX must end up in a position where it only provides sparring to the builders while already leading the pitches for the next feature together with the PO._
 
-![](2022-11-16-processes-scrum-vs.-shapeup-v3-compare.svg)
+![](2022-11-16-processes-scrum-vs.-shapeup-v3-compare.png)
 
 _But because our pitch could have been at a better altitude, we needed to make some decisions during the sprint. So we ended up in an "RND Mode".
 This will scale poorly for a larger product/dev org. But in the end, it was a fundamental agile approach because we could show real things to actual customers, making important decisions on the way._
 
-![](2022-11-16-processes-scrum-vs.-shapeup-v3-corporate-rnd-mode.svg)
+![](2022-11-16-processes-scrum-vs.-shapeup-v3-corporate-rnd-mode.png)
 
 ## Whats next?
 

content/posts/2024-dumplink-open-source/index.md

@@ -8,7 +8,7 @@ tags:
  - technology
  - dumplink
 categories: ["Product"]
-image: "dumplinnk.png"
+image: "dumplink.png"
 aliases:
  - "/posts/2023-dumplink-launch/"
 ---

layouts/partials/entries-list.html

@@ -1,14 +1,38 @@
 <!-- entries-list.html -->
-<ul class="mb-4 space-y-2">
+<ul class="grid grid-cols-1 gap-4 md:grid-cols-2 lg:grid-cols-3">
  {{ range .Pages }}
- <li class="text-lg space-2 ">
- <time datetime='{{ .Date.Format "2006-01-02" }}' class="inline-block px-3 py-1 text-base text-white rounded-lg shadow-sm bg-footer">
- {{ .Date.Format "Jan 02, 2006" }}
- </time>
- <a href="{{ .Permalink }}" class=" text-primary hover:text-primary-dark hover:underline">
- {{ .Title }}
- </a>
+ <li class="flex flex-col overflow-hidden text-lg">
+ <a href="{{ .Permalink }}" class="flex flex-col h-full hover:opacity-75">
+ <!-- Bild einfügen -->
+ {{/* default - what is configured sitewide */}}
+ {{ $image := printf "%s%s" .Site.BaseURL .Site.Params.image }}
+
+ {{/* next best: take the first image of the article, if any */}}
+ {{ range first 1 (.Resources.ByType "image") }}
+ {{ $image = .Permalink }}
+ {{ end }}
 
+ {{/* if in the post is something defined, this overwrites everything. */}}
+ {{ if .Params.image }}
+ {{ $langPath := print .Lang "/" }}
+ {{ if eq .Lang "en" }}
+ {{ $langPath = "" }}
+ {{ end }}
+ {{ $image = printf "%s%s%s%s" .Site.BaseURL $langPath .File.Dir .Params.image }}
+ {{ end }}
+
+ <div class="relative h-48">
+ <img src="{{ $image }}" alt="{{ .Title }}" class="object-cover w-full h-full">
+ <time datetime='{{ .Date.Format "2006-01-02" }}' class="absolute px-3 py-1 text-base text-white rounded shadow-sm bg-footer top-2 right-2">
+ {{ .Date.Format "Jan 02, 2006" }}
+ </time>
+ </div>
+ <div class="flex flex-col justify-between flex-grow p-4 bg-footer2">
+ <h3 class="text-base font-semibold text-primary">
+ {{ .Title }}
+ </h3>
+ </div>
+ </a>
  </li>
  {{ end }}
 </ul>

layouts/partials/meta.html

@@ -24,6 +24,8 @@
 {{ end }}
 {{ $image = printf "%s%s%s%s" .Site.BaseURL $langPath .File.Dir .Params.image}}
 {{ end }}
+
+
 {{- $iso8601 := "2006-01-02T15:04:05-07:00" -}}
 
 <meta name="keywords" content="{{ $keywords }}">

layouts/shortcodes/image.html

@@ -0,0 +1,17 @@
+{{ $image := printf "%s%s" .Site.BaseURL .Site.Params.image }}
+
+{{/* next best: take the first image of the article, if any */}}
+{{ range first 1 (.Resources.ByType "image") }}
+{{ $image = .Permalink }}
+{{ end }}
+
+{{/* if in the post is something defined, this overwrites everything. */}}
+{{ if .Params.image }}
+{{ $langPath := print .Lang "/" }}
+{{ if eq .Lang "en" }}
+{{ $langPath = "" }}
+{{ end }}
+{{ $image = printf "%s%s%s%s" .Site.BaseURL $langPath .File.Dir .Params.image }}
+{{ end }}
+
+{{ $image }}