docs: 배경 글을 README·랜딩에서 링크 - #36
Merged
Merged
Conversation
The write-up explaining why the gap exists — and what a ruler can mean when HTML has no page model — lived only on Medium, unreachable from anything we own. It answers the question a visitor has before they read the API, so it belongs above the fold. Landing gets a muted line under the hero CTAs (translated, so the English page says 'Why this exists' and the Korean one flags that the article is in English). Both root READMEs get it right after the paragraph that states the gap. Linked the Medium original rather than the dev.to cross-post, since that is the canonical the cross-post points at. Verified in a browser: renders in both languages, same href, no competition with the CTA buttons; 99 tests green.
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.
"왜 이 공백이 생겼는지, 페이지 모델이 없는 HTML에서 줄자란 무엇일 수 있는지"를 설명한 글이 미디엄에만 있고 우리 자산 어디에서도 닿을 수 없었습니다. 방문자가 API를 읽기 전에 갖는 질문에 답하는 글이라 상단에 두는 게 맞습니다.
dev.to 교차 게시본이 아니라 미디엄 원문을 링크했습니다 — 교차 게시본의 canonical이 가리키는 대상이 원문이라서요.
검증