Repository navigation
🎨 Stop boxing every inline code word in docs prose - #548
Merged
Merged
Conversation
PR #548: 🎨 Stop boxing every inline code word in docs prose1 files, +4 / -2 Scope✅ PR scope looks good. Structural✅ No structural bloat detected. Slop✅ Slop indicators look low. Static Analysis✅ Oxlint found no issues. Correctness✅ Small PR — correctness review skipped. |
taras
enabled auto-merge (squash)
August 22, 2026 18:34
`.doc :not(pre) > code` ruled and padded every inline `<code>` in documentation body text. `main class="doc"` wraps every /docs page, so this hit every `meta`, `exec`, `--journal`, and similar term in running prose — a sentence with two or three of them reads as a chain of boxes rather than a sentence. Drop the border and padding. Keep the mono face, bump to weight 700, and keep --ink for contrast — the same treatment `Term` in components/Prose.tsx already uses for inline mono terms on the landing page, so docs prose now matches how the rest of the site treats an inline code word: distinguished by weight and font, not a box. Fenced code blocks are untouched (`:not(pre)` already excluded them), as are `.command`, `.code-panel`, and the docs sidebar. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0125zbFPKdEhKdUJxuRufpfj
taras
force-pushed
the
fix/docs-inline-code-boxes
branch
from
August 22, 2026 23:52
c33bdde to
839eb32
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Documentation prose boxes and pads every inline code term. Sentences containing several identifiers or flags read as a chain of controls instead of continuous prose.
What changes
Before:
Inline code inside documentation prose has a border and horizontal padding.
After:
Inline code is distinguished by its monospace face, heavier weight, and full-contrast text without a surrounding box.
How it works
The existing
.doc :not(pre) > coderule drops its border and padding and adds the same weight used by the sharedTermcomponent. The selector continues to exclude code insidepre, so fenced blocks remain unchanged.How to verify it
git diff --check origin/main...origin/fix/docs-inline-code-boxespasses, catching whitespace errors in the patch.mainapplies the stylesheet change without conflicts.Scope
Included
Intentionally unchanged
Risks and limitations
Scope confirmation