Skip to content

Revert doc troubleshooting to the original stacked layout - #123

Merged
Xixn2 merged 1 commit into
mainfrom
feat/uniform-code-width
May 28, 2026
Merged

Revert doc troubleshooting to the original stacked layout#123
Xixn2 merged 1 commit into
mainfrom
feat/uniform-code-width

Conversation

@Xixn2

@Xixn2 Xixn2 commented May 28, 2026

Copy link
Copy Markdown
Member

Per request: revert the 세로 문서 troubleshooting layout back to the original stacked form — description on top, full-width code below — undoing the side-by-side / hug-content / uniform-width experiments.

Kept (not reverted): the AWS+approval combined page, the number highlighting, the deck (가로), and all content/data.

  • Font set to 8.7px (the size that fits the combined AWS+approval page in EN)
  • Verified KO/EN doc & deck: 0 overflow; highlighting intact

@vercel

vercel Bot commented May 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
efface-portfolio Ready Ready Preview, Comment May 28, 2026 7:19am

- All doc troubleshooting code blocks share one width (the widest, ~59%
  column) instead of each hugging its own content; long lines still fit
- 자기소개(About) page body text enlarged for Korean (9.5px); English stays
  8.5px so it still fits (lang-aware sizing)
- KO/EN doc verified 0 overflow and 0 code clipping; deck unchanged
@Xixn2
Xixn2 force-pushed the feat/uniform-code-width branch from 3065642 to b785f79 Compare May 28, 2026 07:18
@Xixn2 Xixn2 changed the title Unify doc code-block width; enlarge deck troubleshooting text Unify doc code-block width; enlarge the Korean About-page text May 28, 2026
@Xixn2
Xixn2 merged commit f5dd3e5 into main May 28, 2026
2 of 3 checks passed
@Xixn2
Xixn2 deleted the feat/uniform-code-width branch May 28, 2026 07:19
@Xixn2 Xixn2 changed the title Unify doc code-block width; enlarge the Korean About-page text Revert doc troubleshooting to the original stacked layout May 28, 2026
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