From b1b6b52f3ff4d4c89fb88c73258dfbfe084fe90d Mon Sep 17 00:00:00 2001
From: hsiegeln <37154749+hsiegeln@users.noreply.github.com>
Date: Sat, 25 Apr 2026 02:35:24 +0200
Subject: [PATCH] refactor(why-us): drop 03:00 watermark, reword card 2
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The decorative giant '03:00' watermark on card 2 plus its 'live'
ops-desk timestamp gimmick was the third repetition of the 3 AM
metaphor on the homepage — the post-launch review flagged that
five hits turns a sharp pain point into a slogan.

Card 2 reworded to lead with 'operated integration in production
for 15 years' — same pedigree claim, no second 3 AM reference.
The walkthrough section already does the 3 AM beat in full.

Card 1 unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 src/components/sections/WhyUs.astro | 33 +++++++----------------------
 1 file changed, 8 insertions(+), 25 deletions(-)

diff --git a/src/components/sections/WhyUs.astro b/src/components/sections/WhyUs.astro
index d4ffc88..a5fc5ff 100644
--- a/src/components/sections/WhyUs.astro
+++ b/src/components/sections/WhyUs.astro
@@ -20,31 +20,14 @@
           So when you ask "why did this exchange fail?", you get an answer, not a log tail. And you can reach back into a running app to replay a message, deep-trace a correlation ID, or toggle recording — observability that does things, not just shows them.
         </p>
       </div>
-      <div class="relative overflow-hidden rounded-lg border border-border bg-bg-elevated p-8 transition-all duration-200 ease-out hover:-translate-y-0.5 hover:border-accent/40 hover:shadow-[0_12px_32px_-12px_rgba(240,180,41,0.18)]">
-        <div
-          aria-hidden="true"
-          class="pointer-events-none select-none absolute -top-6 -right-4 font-mono font-bold leading-none tracking-tight text-accent/[0.04] text-[7rem] md:text-[9rem]"
-        >
-          03:00
-        </div>
-        <div class="relative">
-          <div class="flex items-center gap-2.5 mb-5 font-mono text-xs">
-            <span aria-hidden="true" class="relative inline-flex w-1.5 h-1.5">
-              <span class="absolute inset-0 rounded-full bg-accent"></span>
-              <span class="absolute inset-0 rounded-full bg-accent/60 animate-ping [animation-duration:2.4s]"></span>
-            </span>
-            <span class="text-accent tabular-nums tracking-wide">03:00:47.218</span>
-            <span class="text-text-faint">·</span>
-            <span class="text-text-faint uppercase tracking-[0.2em]">ops desk</span>
-          </div>
-          <h3 class="text-xl font-bold text-text mb-4">Built by people who know what 3 AM looks like.</h3>
-          <p class="text-text-muted leading-relaxed mb-4">
-            We spent years building integration monitoring for banks, insurers, and logistics operators — the kind of shops where a stuck exchange at 3 AM means someone's phone is ringing. We know what integration teams actually need then, and what they never use.
-          </p>
-          <p class="text-text-muted leading-relaxed">
-            Cameleer is what we would build today, purpose-built for Apache Camel. No legacy, no retrofit, no assumptions about a generic middleware platform.
-          </p>
-        </div>
+      <div class="rounded-lg border border-border bg-bg-elevated p-8 transition-all duration-200 ease-out hover:-translate-y-0.5 hover:border-accent/40 hover:shadow-[0_12px_32px_-12px_rgba(240,180,41,0.18)]">
+        <h3 class="text-xl font-bold text-text mb-4">Built by people who've operated integration in production for 15 years.</h3>
+        <p class="text-text-muted leading-relaxed mb-4">
+          We spent over a decade building integration monitoring for banks, insurers, and logistics operators — the kind of shops where a stuck exchange is a regulatory event, not just an inconvenience.
+        </p>
+        <p class="text-text-muted leading-relaxed">
+          Cameleer is what we'd build today, purpose-built for Apache Camel. No legacy, no retrofit, no assumptions about a generic middleware platform.
+        </p>
       </div>
     </div>
   </div>