Skip to content

Why: a "Works with" card in the third benefit's place (0.2.5) - #13

Merged
samifouad merged 1 commit into
mainfrom
claude/works-with
Nov 6, 2026
Merged

samifouad merged 1 commit into
mainfrom
claude/works-with

Conversation

@samifouad

Copy link
Copy Markdown
Member

Sami wants a "Works with" section on securecore.addis.gg (addiscorp/securecore-site#2) in place of the "What it costs" card. This lets Why put it in the third benefit's slot. Version 0.2.5.

What changed

  • Why takes either three benefits, as before, or two benefits plus works. The types enforce it: two benefits without works, or three with it, don't compile.
  • WorksWith is { title, note?, items }. Each WorksItem is { name, logo?: { light, dark? }, note? }:
    • Logo: an image the site serves itself, shown when the owner allows reference use. With dark, the light and dark images switch with the theme, using the same .akt-mark rules as the marks.
    • No logo: where the owner allows the name only in plain text, as Woo's trademark guidelines do for WooCommerce, the row renders no image at all.
    • Note: sits under the name, in the family list's muted mono.
  • CSS: .akt-work rows. The card is in the narrow slot (4 of 10 columns), so each row is a 28px logo, then the name with its note stacked under it.

Every other tool site is unchanged: three benefits render exactly as before.

Evidence

npm ci            exit 0
npm run typecheck exit 0
npm test          exit 0   (build + 18 tests, 18 pass; 1 new)

The new test, 'a "works with" card takes the third benefit's place…', checks:

  • the card order;
  • light and dark logos;
  • that a name-only item has no <img>;
  • the notes;
  • that three benefits render no card.

With index.tsx stashed it fails (exit 1).

Needs (orchestrator)

Merge and tag v0.2.5.

-claude

…here the owner allows them, names, notes (0.2.5)
@samifouad
samifouad merged commit 10cbf30 into main Nov 6, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant