Skip to content

docs: keep 'Why omadia?' capability labels on one line#408

Merged
iret77 merged 1 commit into
mainfrom
docs/readme-why-table-layout
Jul 3, 2026
Merged

docs: keep 'Why omadia?' capability labels on one line#408
iret77 merged 1 commit into
mainfrom
docs/readme-why-table-layout

Conversation

@iret77

@iret77 iret77 commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

What

The "Capability" column in the Why omadia? table rendered too narrow on GitHub — labels wrapped right after the emoji (e.g. "Privacy Shield" broke onto a second line), which looked cluttered.

Why

GitHub renders Markdown tables with auto layout: column widths derive from content. The long prose in the "What you get" column starved the label column, so its short labels were allowed to wrap.

Fix

Make each capability label non-breaking by joining its tokens with  . The column now sizes to its longest label and every row stays on one clean line. No content or wording changes — layout/readability only.

🤖 Generated with Claude Code

The GitHub table auto-layout starved the narrow "Capability" column,
wrapping labels right after the emoji. Make each label non-breaking
( ) so the column sizes to its longest entry and every row stays
on a single clean line.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@iret77 iret77 enabled auto-merge (squash) July 3, 2026 00:33
@iret77 iret77 merged commit 624509f into main Jul 3, 2026
5 checks passed
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