Resolved Issue: Status Table on the Github page is cut off (#132) - #133
Merged
Conversation
Contributor
|
@zionmich Tho I do appreciate the compactness of the table being viewable, it is harder as a user (from my perspective) to go back and forth between the descriptions and the table to understand what each row means. Other comparison matrices in our ospo-guide are also horizontal, so I'm less +1 on switching to a vertical layout here. I do think your instincts are on point tho for the clipping/scrolling issue, so perhaps we can try some other ways to reduce the size:
|
Contributor
|
+1 to what Remy said^ I think having each status determination as its own row with each determining factor as a column most clearly and understandably explains the content here. I'm down for the first two ideas! |
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.
outbound/archiving-repositories: Fix clipped status table on GitHub page
Problem
The repo activity status table in
content/outbound/archiving-repositories.mdwas too wide to render properly on the GitHub page — it was clipped with no
horizontal scrolling element, making the "Criticality Score" and "Is repo
empty/README only?" columns unreadable (#132).
Solution
Restructured the table so that the status name and the description share one columns.
Result
The status table now displays fully on the GitHub page without clipping.
Test Plan
Render the updated markdown locally (npm run clean, npm run build, npm run start) to confirm the table displays fully
within the page width.
AI Usage
No AI was used in this iteration, development was based on Remy's feedback.