revert(ui): language switcher back to its own band; fold MCP into Model-Context-Protocol - #71
Merged
Merged
Conversation
I had moved the switcher include into .post-header-info as a fourth meta item — PUBLISHED · READ TIME · CATEGORY · LANGUAGE on one line — on the grounds that a lone right-aligned button in a full-width strip was "aligned against nothing". Rendering both and looking at them says otherwise. The button's right edge lines up exactly with the right edge of the meta card above it and the table-of-contents box below it; those two cards are the alignment, and there is nothing floating about it. Verified at 1200px and at a real 390px viewport. The label was the worse half of that change. "English로 읽기 →" already says what the control does, so a LANGUAGE caption in front of it states the same thing twice. And the row it joined is information the reader reads — a date, a duration, a category — while this is an action the reader takes. Putting them on one line flattened that distinction to save a line of vertical space. Markup and CSS are now byte-identical to what they were before; only the comments differ, and they state the current intent rather than narrating the round trip.
Both tags existed and meant the same thing. MCP was on exactly one post, which already carried Model-Context-Protocol as well, so the pair split nothing — it just gave /tags/ two entries for one concept and put two chips saying the same word on one post. Keeping the spelled-out form matches the rest of the taxonomy, which already prefers Retrieval-Augmented-Generation over RAG and Mixture-of-Experts over MoE. This does retire the /tags/#mcp anchor. That is the reason the two were left coexisting earlier; the tradeoff is now accepted deliberately rather than by default. The only link that pointed at it was the post's own tag chip, so nothing internal breaks.
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
1 participant
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.
Two changes, both reversing a call I had made without the user's input.
The language switcher goes back to its own band
I had moved the include into
.post-header-infoas a fourth meta item — PUBLISHED · READ TIME · CATEGORY · LANGUAGE on one line — arguing that a lone right-aligned button in a full-width strip was "aligned against nothing."Rendering both and looking at them says otherwise. The button's right edge lines up exactly with the right edge of the meta card above it and the table-of-contents box below it. Those two cards are the alignment.
The label was the worse half.
English로 읽기 →already says what the control does, so aLANGUAGEcaption in front of it states the same thing twice. And the row it joined is information the reader reads — a date, a duration, a category — while this is an action the reader takes. Merging them flattened that distinction to save a line of vertical space.Markup and CSS are now byte-identical to their previous state; only the comments differ, and they state the current intent rather than narrating the round trip.
Verified at 1200px and at a real 390px viewport (through a fixed-width iframe — legacy headless Chrome lays out at a 500px floor and crops, which fakes an overflow bug).
MCP folds into Model-Context-Protocol
Both tags existed for one concept.
MCPwas on exactly one post, which already carriedModel-Context-Protocoltoo, so the split separated nothing — it gave/tags/two entries for one idea and printed two chips saying the same word on one post.Keeping the spelled-out form matches the taxonomy, which already prefers
Retrieval-Augmented-Generationover RAG andMixture-of-Expertsover MoE.This retires the
/tags/#mcpanchor, which is why the two had been left coexisting. That tradeoff is now taken deliberately. The only link pointing at it was the post's own tag chip, so nothing internal breaks — html-proofer confirms.Gates
All four pass: 100 unit tests, build, html-proofer (with CI's flag set),
validate-site.sh./tags/goes 271 → 270 entries;#model-context-protocolkeeps its 3 posts.