docs: collapsible record index - #119
Merged
Merged
Conversation
Uses <details>/<summary> rather than CSS overflow, since GitHub strips inline CSS on div elements in rendered markdown. Collapsed by default to reduce README scroll length; expands on click.
The badge, Stats table, and the new collapsible record index summary label (docs/collapsible-record-index) each use different text patterns; a single grep for '[0-9]+ records' would silently miss two of the three. Spelled out all three explicitly so this doesn't drift out of sync from memory each time a record gets added.
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.
Wraps the record index table in a details/summary block, collapsed by default. Chose details over a CSS-scrollable div since GitHub sanitizes inline styles on divs in README rendering; details is native HTML5 and actually works. Verified against GitHub's real rendered HTML (not just source inspection): the details/summary/table structure parses correctly, the table renders as a proper table inside the collapsed block, and the closing tag lands in the right place.