Posts tagged #css — Page 2

The high-voltage variant of Grimicorn keeps every semantic role and swaps in eight electric hexes. Here's what changes, what doesn't, and the contrast tradeoff that makes neon-on-black a deliberate choice.

How I turned a single calm, low-fatigue color palette into matching dark and light themes for VS Code, terminals, Obsidian, Claude Code and ten other tools — all generated from one source of truth.

Unregistered CSS custom properties can't animate — they just snap. @property fixes that by giving the browser a type, a default, and an inheritance rule, unlocking smooth transitions for gradients, counters, and design tokens.

CSS @scope reached full browser support in December 2025 — here's how to use it to write component-scoped styles without CSS Modules, BEM, or a build step.

WCAG 2.2 became the enforcement standard in 2026. Here are the nine new success criteria that matter most for frontend developers — and what to actually do about them.

The @starting-style rule gives CSS transitions a starting point when elements first appear, enabling smooth entry animations from display:none or fresh DOM insertion — no JavaScript required.

A practical guide to prefers-reduced-motion, prefers-color-scheme, prefers-contrast, and forced-colors — the CSS media queries that respect user accessibility settings with zero JavaScript.

CSS finally has native conditional logic with the new if() function — write style queries, media checks, and feature detection directly inside property declarations without extra selectors or JavaScript.

The new ::search-text pseudo-element lets you style the highlights from Ctrl+F find-in-page, so they finally match your site instead of clashing with it.