joh/customer-presentation
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

roadmap: rename Wave cards to Knowledge/Tools/Agents, drop duration meta

Browse source 
Card faces and the expanded panel now show only title + subtitle.
Setup keeps its title; Wave 1/2/3+ become Knowledge, Tools, Agents
with updated subtitles. The .rm-mono meta line (e.g. "Once · 1-2
weeks") is removed from all four cards, along with the now-orphan
.rm-mono base rule and its is-expanded order override. Card
min-height drops to 132px and the column flex now centres the
title+subtitle pair so the leaner content sits balanced inside the
walnut surface; grid stretch keeps the row equal-height.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jonathan Hvid 2026-05-20 13:26:55 +02:00
parent fb815768e2
commit bd4d2f5f33
2 changed files with 9 additions and 29 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
protected/index.html
View file

@ -3392,7 +3392,6 @@ html {
aria-expanded="false" data-detail="setup">
<h3 class="rm-name">Setup</h3>
<p class="rm-italic">Platform live in your environment</p>
<p class="rm-mono">Once &middot; 1&ndash;2 weeks</p>
<div class="rm-card-body" aria-hidden="true">
<p class="rm-card-intro">The one-time foundation. In a single sprint, the platform goes live inside your infrastructure &mdash; model deployed, identity wired in, brand voice applied, baseline policies enforced. After this, the platform is ready to receive any use case.</p>
<p class="rm-card-section-label">Key activities</p>
@ -3413,9 +3412,8 @@ html {
<li class="rm-card" role="button" tabindex="0"
aria-expanded="false" data-detail="wave-1">
<h3 class="rm-name">Wave 1</h3>
<p class="rm-italic">Knowledge captured</p>
<p class="rm-mono">2&ndash;4 weeks per use case</p>
<h3 class="rm-name">Knowledge</h3>
<p class="rm-italic">Captured into one structured source</p>
<div class="rm-card-body" aria-hidden="true">
<p class="rm-card-intro">The first body of use cases captures what your organisation already knows. For each use case, the team scopes the target output, ingests the right files, and runs AI-led interviews to surface the knowledge that today lives only in people&rsquo;s heads.</p>
<p class="rm-card-section-label">Key activities</p>
@ -3436,9 +3434,8 @@ html {
<li class="rm-card" role="button" tabindex="0"
aria-expanded="false" data-detail="wave-2">
<h3 class="rm-name">Wave 2</h3>
<p class="rm-italic">Systems connected</p>
<p class="rm-mono">1&ndash;4 weeks per use case</p>
<h3 class="rm-name">Tools</h3>
<p class="rm-italic">Acting across your systems</p>
<div class="rm-card-body" aria-hidden="true">
<p class="rm-card-intro">Use cases that reach beyond knowledge into your systems. Each tool implementation wires the platform into a specific source or destination &mdash; a data warehouse, a SharePoint repository, an API, a structured report. The platform stops being read-only and starts acting on your behalf.</p>
<p class="rm-card-section-label">Key activities</p>
@ -3459,9 +3456,8 @@ html {
<li class="rm-card" role="button" tabindex="0"
aria-expanded="false" data-detail="wave-3">
<h3 class="rm-name">Wave 3+</h3>
<p class="rm-italic">Agents at work</p>
<p class="rm-mono">1&ndash;4 weeks per use case</p>
<h3 class="rm-name">Agents</h3>
<p class="rm-italic">Workflows running under your control</p>
<div class="rm-card-body" aria-hidden="true">
<p class="rm-card-intro">Use cases that compose multiple steps into one governed workflow. For each agent use case, the team defines the task, builds the specialist agents that handle it, and configures monitoring, human checkpoints, and governance at every step. The platform now does work end to end &mdash; under your control.</p>
<p class="rm-card-section-label">Key activities</p>

22
protected/platform.css
View file

@ -209,8 +209,9 @@ body:has(#page-product-deepdive.is-active) .dot-nav-tray { opacity: 0; }
padding: var(--space-6) var(--space-5);
display: flex;
flex-direction: column;
justify-content: center;
gap: var(--space-2);
min-height: 168px;
min-height: 132px;
/* Clickable. Hover and focus-visible lift the card so it's
obvious the surface is interactive; the focus outline uses
the brand accent and the same offset the rest of the deck
@ -277,15 +278,6 @@ body:has(#page-product-deepdive.is-active) .dot-nav-tray { opacity: 0; }
margin: 0;
}
.rm-mono {
font-family: var(--font-mono);
font-size: 11px;
letter-spacing: 0.04em;
line-height: 1.4;
color: rgba(255, 252, 247, 0.62);
margin: auto 0 0 0;
}
/* Cross-cutting band — sits underneath the row, spans the same
width. Paper surface (not walnut) so the eye reads "continuous
infrastructure" rather than "fifth step". */
@ -404,15 +396,7 @@ body:has(#page-product-deepdive.is-active) .dot-nav-tray { opacity: 0; }
margin-top: var(--space-5);
}
/* Meta moves to the TOP of the expanded panel via flex order;
the natural margin-auto that pushed it to the bottom in the
collapsed face is reset to zero. */
.rm-card.is-expanded .rm-mono {
order: -1;
margin: 0 0 var(--space-2) 0;
}
/* Title + subtitle stay in DOM order below the meta. Subtitle
/* Title + subtitle sit at the top of the expanded panel. Subtitle
gets a small bottom margin to separate it from the intro. */
.rm-card.is-expanded .rm-name {
font-size: clamp(1.5rem, 2.4vw, 2rem);