Building Scalable AI systems with LLMs, SLMs, Semantic Search, NLP, and AI Agents.

Design System: Sachin Kalsi Portfolio

1. Overview

Creative North Star: “The Field Notebook”

The site reads as a working engineer’s technical notebook, not a marketing template: high-contrast ink-on-paper for reading, a single committed signal color (burnt-orange) used sparingly and deliberately, and monospace reserved for exactly the places a developer expects it — code, dates, tags, source labels — never as costume. This replaces the prior “SaaS Template” baseline (royal-blue #2563eb, Slate-50/white, Inter-everywhere, ambient-shadow hover-lift cards), which PRODUCT.md named as an explicit anti-reference undermining credibility with an NLP/ML practitioner audience.

The structural skeleton from the previous system is preserved (hero → content sections → grid/list → footer) because it was sound information architecture; what changed is the surface treatment and, on the blog specifically, the decision to stop giving original technical notes and syndicated reposts the same visual weight.

Key Characteristics:

2. Colors

Restrained-to-committed strategy: a near-black ink on near-white paper carries almost all of the surface; one saturated accent (signal orange) is spent deliberately on interactive and identity moments, never as background wash.

Primary

Neutral

Named Rules

The One Accent Rule. Signal orange is the only saturated color on the site. If a new component reaches for a second bright hue, that’s drift — stop and ask whether ink, paper, or an existing neutral would do the job instead.

Documented exception: the copy-code button’s .copied success state uses green (rgba(34,197,94,*) / #86efac) on the dark code surface. This is universal success semantics, not brand color, and is scoped to a two-second transient state — it doesn’t violate the One Accent Rule.

3. Typography

Display/Body Font: Archivo (Google Fonts, weights 400–800), fallback sans-serif. Mono/Label Font: JetBrains Mono (Google Fonts, weights 400–700), fallback monospace.

Character: A geometric grotesk (Archivo) for everything a reader parses as prose or UI, paired with a monospace face (JetBrains Mono) for everything that’s technically precise — code, dates, tags, source labels, the hero-role line. The pairing itself is the “engineer’s notebook” signal: prose reads cleanly, metadata reads like annotations in the margin.

Hierarchy

Named Rules

The Mono-Is-Metadata Rule. JetBrains Mono is reserved for metadata and code — dates, tags, source labels, badges. It never appears in headings or body prose. This keeps the mono accent earned (this is a genuinely technical site) rather than costume.

4. Elevation

Flat by default. No ambient shadows anywhere in the system; depth and interactivity are communicated entirely through a 1px border shifting from neutral to signal-orange on hover, plus (on cards) a background tint on repost list rows. This directly replaces the prior ambient-shadow + translateY(-4px) hover-lift pattern, which is now a Don’t (see below).

Named Rules

The Flat-By-Default Rule. No box-shadow for elevation anywhere outside the .blog-post container’s structural 1px border (which is a border, authored as a shadow only for a legacy reason and should migrate fully to border over time). Cards, buttons, and badges use border-color changes, not shadows, to signal state.

5. Components

Buttons

Cards

Repost List (new — replaces a second card grid)

Tags / Chips

Post Pager & Related Posts (new)

6. Do’s and Don’ts

Do:

Don’t: