Skip to content

docs: expand guidance on when to use --inline - #33

Merged
timhettler merged 1 commit into
mainfrom
docs/when-to-use-inline
Aug 10, 2026
Merged

timhettler merged 1 commit into
mainfrom
docs/when-to-use-inline

Conversation

@timhettler

Copy link
Copy Markdown
Owner

Expands the --inline section from "a fallback when a proxy isn't an option" into first-class decision guidance, per review discussion.

What

  • Reframes inline as often the simplest correct choice for small/moderate icon sets (no proxy, no cross-origin gotcha, no cold-cache flash, SSR'd).
  • Adds a "When to reach for --inline" heuristic: inline for small sprites / navigation-light apps; the default static sprite (+ --hash/immutable) for large sets or high-traffic sites; --proxy when that cached file lives on a CDN.
  • Keeps the honest cost visible: one copy of the sprite in every HTML document, re-sent per full navigation — which is why inline isn't the default.
  • Corrects a stale line that implied the proxy is the default recommendation (the default is the static same-origin sprite).

Docs only.

🤖 Generated with Claude Code

Reframe the inline section from a proxy fallback into first-class decision guidance with a size-based heuristic (inline vs static sprite vs proxy), and correct the stale note implying the proxy is the default (the static same-origin sprite is).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@timhettler
timhettler merged commit ec7c95e into main Aug 10, 2026
1 check passed
@timhettler
timhettler deleted the docs/when-to-use-inline branch August 10, 2026 19:30
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