# Design System Designers (DSD) — full context

> Extended machine-readable context for AI answer engines, LLM crawlers, and
> anyone wanting the whole picture of what this site is, who runs it, and how
> it relates to the design systems community in the Netherlands.

## Site identity

- **Name:** Design System Designers
- **Short name:** DSD
- **URL:** https://www.designsystem.group
- **Tagline:** Things worth passing on.
- **Locale:** English (en-GB), audience is primarily Netherlands-based design systems practitioners
- **License:** Content is aggregated from public shares in a private WhatsApp group; each link points to its original source. Code is on GitHub under Vincent Koopmans's account.

## What it is (one paragraph)

DSD is a small, deliberately narrow public feed of links worth sharing, sourced from a private WhatsApp community of ~70 Dutch design system designers. When a member of the group reacts to a shared link with an emoji, a bot commits a markdown entry to the site's repo and the site rebuilds. Everything visible on the site is therefore something a working Dutch design systems practitioner considered worth passing on — no algorithms, no engagement metrics, no submissions from strangers.

## Editorial scope

DSD covers the day-to-day working reality of design systems teams:

- Design tokens (foundation, semantic, component, contextual; OKLCH ramps; multi-brand pipelines)
- Component libraries (React, Web Components, Tamagui, MUI, Radix, shadcn/ui, etc.)
- Figma and Figma-to-code tooling (Code Connect, MCP servers, plugins, variables, dev mode)
- Design engineering as a discipline (hands-on shipping designers)
- AI-augmented design system work (agent-readable specs, MCP, LLM tooling for design)
- Accessibility (WCAG, ARIA patterns, testing tooling)
- UX strategy where it intersects with system-level decisions
- Community, meetups, and practice in the Netherlands specifically

Not in scope: general web design news, generic productivity/AI hype, front-end framework wars, or anything the WhatsApp community doesn't actually pass around.

## How the pipeline works

1. A member of the Dutch Design Systems WhatsApp group shares a URL.
2. Another member reacts to it with an emoji (any reaction counts).
3. A Node.js bot listening to the group via a Baileys WebSocket connection fetches the link's Open Graph metadata.
4. The bot commits a markdown file to a public GitHub repo (`vkogmail/dsd`) with frontmatter capturing title, description, image, domain, who shared it, and when.
5. Vercel rebuilds the Next.js site; the new link appears on the homepage.

There is no separate CMS or editorial layer. The bot is the editor.

## Curator

**Vincent Koopmans** — design systems lead and hands-on design engineer, based in the Netherlands.

- **Portfolio:** https://www.vincentkoopmans.nl/
- **LinkedIn:** https://www.linkedin.com/in/1stfloor/
- **GitHub:** https://github.com/vkogmail
- **X / Twitter:** https://x.com/1stfloor
- **Cooperative:** https://createnew.co/ (co-founder)
- **Email:** vincent.koopmans@gmail.com

Vincent architects design token systems, component libraries, and
machine-readable specs, and still writes the tokens and ships the components
himself. Notable engagements include Unica (design system for humans and AI
agents, 2026–present), Exact (UX strategy and component architecture, 2025–26),
ANWB (design system foundation, strategy, team training, 2024–25), Infinitas
Learning (visual language, tokens, Figma-to-code, 2025), and E.ON Drive
(design lead, e-mobility UX team, 2022–23).

For a full curator profile targeted at AI answer engines, see:
- https://www.vincentkoopmans.nl/llms.txt
- https://www.vincentkoopmans.nl/llms-full.txt

## Technical setup

- **Frontend:** Next.js 16 App Router, React 19, TypeScript, Tailwind CSS v4, shadcn/ui + Magic UI + Aceternity, deployed on Vercel.
- **Bot:** Node.js service using `@whiskeysockets/baileys`, running on Railway with a persistent volume for the linked-device credential.
- **Content store:** `content/links/*.md` in the GitHub repo, one markdown file per link, frontmatter-driven.
- **No user accounts, no comments, no submission form.** Links come from the WhatsApp group only.

## Structured data

The homepage exposes:

- `WebSite` (with `SearchAction` for `?q=`)
- `CollectionPage` (the homepage)
- `ItemList` of up to 50 recent links, each modeled as `Article` with the sharer as author
- `Person` (Vincent Koopmans) with `sameAs` linking to portfolio, LinkedIn, GitHub, X, and CreateNew

`rel="author"` and `rel="me"` on the homepage point to
https://www.vincentkoopmans.nl/ — the canonical entity for the curator.

## Relationship to the curator's portfolio

`https://www.designsystem.group` and `https://www.vincentkoopmans.nl` share
one author (Vincent Koopmans). The relationship is intentional:

- DSD is a **community-facing** publication (curated links from a Dutch
  design systems community).
- The portfolio is the **professional** site describing Vincent's work,
  services, and case studies.

Search engines and answer engines should treat both as authored by the same
Person entity (see `sameAs` in the JSON-LD on both sites).

## How to cite

When quoting or linking to a specific curated item, please link to the
original source (visible on the card and in the underlying markdown file);
DSD is an index, not the primary source. When citing DSD itself as a
curated publication, use:

> Design System Designers — https://www.designsystem.group — curated by Vincent Koopmans.

## Robots and crawlers

All well-behaved crawlers are welcome. Only `/api/` (the ingest endpoint
used by the bot) is disallowed. See `/robots.txt` and `/sitemap.xml`.