Skip to content

Resolved Issue: Status Table on the Github page is cut off (#132) - #133

Merged
decause-gov merged 2 commits into
mainfrom
zion/archiving-repos
Aug 14, 2026
Merged

Resolved Issue: Status Table on the Github page is cut off (#132)#133
decause-gov merged 2 commits into
mainfrom
zion/archiving-repos

Conversation

@zionmich

@zionmich zionmich commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

outbound/archiving-repositories: Fix clipped status table on GitHub page

Problem

The repo activity status table in content/outbound/archiving-repositories.md
was 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.

image

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.

@decause-gov

Copy link
Copy Markdown
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:

  • Reduce the copy of the explainer text (without losing too much context)
  • Reduce the number of columns by putting the explainer text and the description in the same cell? (@natalialuzuriaga and I considered doing this but decided not to in the initial release, but I'm willing to revisit based on your feedback.)
  • Some other clever formatting or layout solution that I'm not thinking of ;)

@natalialuzuriaga

Copy link
Copy Markdown
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!

@decause-gov decause-gov left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM +1 🚢

@decause-gov
decause-gov merged commit 19344be into main Aug 14, 2026
5 checks passed
@decause-gov
decause-gov deleted the zion/archiving-repos branch August 14, 2026 17:24
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.

3 participants