From 37897f07c32c20fb08bcc125c26200524185314c Mon Sep 17 00:00:00 2001 From: hsiegeln <37154749+hsiegeln@users.noreply.github.com> Date: Sat, 25 Apr 2026 12:41:59 +0200 Subject: [PATCH] chore: remove all nJAMS references from the live site MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Per Hendrik's direction, no nJAMS references on the website. The founder pedigree claim now stands on the years and the customer segment ("15 years building integration monitoring for banks, insurers, and logistics operators") without naming a prior product. Changes: - src/components/sections/SocialProofStrip.astro: drop the ' · ex-nJAMS' suffix from the founder attribution; collapse the multi-step PENDING comment into a single-line founder-name TODO. - src/components/sections/WhyUs.astro: drop the trademark-review comment (no longer relevant — the body text never named the prior product, only the comment did). - OPERATOR-CHECKLIST.md: remove the 'Why us / nJAMS wording review' pre-publish task. Also rename the adjacent 'MID-tier retention' TODO to 'Starter-tier retention' to match the relaunched tier taxonomy. - docs/superpowers/specs/2026-04-25-cameleer-website-relaunch-design.md: update §4, §6.2, §12 to reflect the removed wording. Only the founder-name placeholder remains as a pre-publish blocker. Historical specs / plans under docs/superpowers/{specs,plans}/ keep their original wording — they're records of past decisions and are not on the website. Co-Authored-By: Claude Opus 4.7 (1M context) --- OPERATOR-CHECKLIST.md | 3 +-- .../2026-04-25-cameleer-website-relaunch-design.md | 12 ++++-------- src/components/sections/SocialProofStrip.astro | 9 ++------- src/components/sections/WhyUs.astro | 2 -- 4 files changed, 7 insertions(+), 19 deletions(-) diff --git a/OPERATOR-CHECKLIST.md b/OPERATOR-CHECKLIST.md index cadb4ce..16f29a2 100644 --- a/OPERATOR-CHECKLIST.md +++ b/OPERATOR-CHECKLIST.md @@ -87,8 +87,7 @@ workflows read them via the `${{ secrets.* }}` context. - [ ] Fill in `src/pages/imprint.astro` `operator` object with real legal details. - [ ] Fill in `operatorContact` in `src/pages/privacy.astro`. -- [ ] Review the "Why us" / nJAMS wording in `src/components/sections/WhyUs.astro` for trademark safety. -- [ ] Confirm MID-tier retention: spec says **7 days**; `cameleer-saas/HOWTO.md` says **30 days**. Reconcile one side or the other. +- [ ] Confirm Starter-tier retention: spec says **7 days**; `cameleer-saas/HOWTO.md` says **30 days**. Reconcile one side or the other. ## 5. First deploy diff --git a/docs/superpowers/specs/2026-04-25-cameleer-website-relaunch-design.md b/docs/superpowers/specs/2026-04-25-cameleer-website-relaunch-design.md index 2446edd..f5f497b 100644 --- a/docs/superpowers/specs/2026-04-25-cameleer-website-relaunch-design.md +++ b/docs/superpowers/specs/2026-04-25-cameleer-website-relaunch-design.md @@ -53,7 +53,7 @@ The relaunch's H1 leans Manager-outcome on purpose — the IT Manager is the che The original site shipped with no social proof. This relaunch can't fix that with logos or attributed customer quotes — **none are ready to publish**. The two anchors we *can* lean on: -1. **Founder pedigree** (nJAMS lineage). Subject to trademark clearance — same gating as `WhyUs.astro`'s existing comment. Until cleared, the wording is held in a `` HTML comment. +1. **Founder pedigree** — "15 years building integration monitoring for banks, insurers, and logistics operators." No prior-product name is used. The pedigree claim stands on the years and the customer-segment, not on a brand reference. 2. **Design-partner program**. Reframes the pre-customer state as a feature ("hand-picked early partners"), with a `mailto:` CTA to `PUBLIC_SALES_EMAIL` that the visitor can use to apply. Both anchors live in a new dedicated **Social Proof Strip** section (§6.2) immediately below the hero. @@ -118,14 +118,12 @@ Order is deliberate — see §11 for the rationale (proof-first arc: hero → wh - **Eyebrow** (mono, amber, ~12px): `// Built by people who've done this before` - **Quote block** (italic, ~17px, max 62ch, accent-colored 3px left border, padding-left ~20px): > *"We spent 15 years building integration monitoring for banks that couldn't afford downtime. Cameleer is what we'd build today — purpose-built for Apache Camel, no retrofit."* -- **Attribution** (~13px, muted, mono): `— [Founder Name], co-founder · ex-nJAMS` +- **Attribution** (~13px, muted, mono): `— [Founder Name], co-founder` - **Below attribution** (~24px gap, then a single `mailto:`-styled CTA in mono+cyan): `Apply to the design-partner program →` **`` gates** (do not ship without resolving): -- `[Founder Name]` is a placeholder. -- `ex-nJAMS` mention is gated on trademark clearance (same as `WhyUs.astro`'s existing §10 caveat). -- Either gate may be deferred by removing the affected line — the section still works as "pedigree quote, design-partner CTA" without the nJAMS-specific phrase. +- `[Founder Name]` is a placeholder. Must be filled in pre-publish. **Design-partner CTA target**: built inline in `SocialProofStrip.astro` using `auth.salesEmail` (not `auth.salesMailto`, which has no subject helper): @@ -372,15 +370,13 @@ A traditional SaaS layout (features → benefits → how → pricing) would put - [ ] `prefers-reduced-motion: reduce` disables the hero-mark sway and any tile-rise animations (existing handling preserved). - [ ] Tab focus order on the homepage is: nav → hero primary → hero secondary → social-proof CTA → walkthrough CTA targets … → final CTA. - [ ] All `mailto:` links open with the correct subject (design-partner CTA + sales contacts). -- [ ] Trademark `` gate in `SocialProofStrip.astro` and `WhyUs.astro` is reviewed before publish. - [ ] Founder name placeholder is filled in `SocialProofStrip.astro` before publish. **Pre-publish blockers** (recorded in code as `` HTML comments): 1. `[Founder Name]` placeholder in `SocialProofStrip.astro` — must be replaced with a real name. -2. nJAMS / `ex-nJAMS` wording — must clear trademark review (existing pattern from `WhyUs.astro`). -These are deliberately surfaced as code-level TODOs rather than spec-level open questions so the operator can't accidentally publish with the placeholders intact. +This is deliberately surfaced as a code-level TODO rather than a spec-level open question so the operator can't accidentally publish with the placeholder intact. --- diff --git a/src/components/sections/SocialProofStrip.astro b/src/components/sections/SocialProofStrip.astro index 4105290..4adec98 100644 --- a/src/components/sections/SocialProofStrip.astro +++ b/src/components/sections/SocialProofStrip.astro @@ -3,12 +3,7 @@ import { getAuthConfig } from '../../config/auth'; const auth = getAuthConfig(); -// PENDING — must be filled in before publish: -// 1. [Founder Name] placeholder below. -// 2. The "ex-nJAMS" mention is gated on Hendrik's trademark review -// (same pattern as WhyUs.astro §10 caveat). If the review is not -// cleared by publish time, drop the " · ex-nJAMS" suffix from the -// attribution line. +// PENDING — [Founder Name] placeholder must be filled in before publish. const founderName = '[Founder Name]'; const designPartnerSubject = 'Design partner enquiry — Cameleer'; const designPartnerHref = `mailto:${auth.salesEmail}?subject=${encodeURIComponent(designPartnerSubject)}`; @@ -24,7 +19,7 @@ const designPartnerHref = `mailto:${auth.salesEmail}?subject=${encodeURIComponen “We spent 15 years building integration monitoring for banks that couldn’t afford downtime. Cameleer is what we’d build today — purpose-built for Apache Camel, no retrofit.”