Repository navigation
Final Hindi/Kannada report showcase with responsive three-card layout - #11
Merged
Merged
Conversation
…nine viewport sizes
…-card responsive layout
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.
Final submission showcase
lang=eninherited from the HTML ancestor, one suspected mobile overflow), 13 informational font notes, both Chromium pages present. No invented AI claims.scripts/finalize_submission_showcase.py) to validate the exact saved report, copy all real evidence to GitHub Pages samples, then switch the homepage catalog from Hindi Wikipedia to Kannada while keeping Wikipedia's archive files. README updates alongside it.review_note; cards keep equal widths in a single row at desktop widths and stack on smaller screens.No BharatCode API calls or new scans, no changes to saved 9/9 AI report. This PR intentionally does NOT fabricate/add binary report screenshots from a local user archive. User runs the publisher locally after the PR merges; the real image assets are then committed for deployment.