Repository navigation
bring the README header in line with the awesome guidelines - #34
Conversation
|
Warning Review limit reachedNext included review available in 45 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Reviewed against the curation/description/category/duplicate/header checklist: this diff only touches the README header (description line) and |
What does this PR add?
Three header issues that
awesome-lintdoes not check but the submission guidelines do. All three are in the first eight lines.1. The description described the list, not the topic.
The old line read out the table of contents without ever saying what authorization is. That is the shape the guidelines reject (
❌ Resources and tools for iOS development.vs✅ Mobile operating system for Apple phones and tablets.), and it is what got #1042 and #2607 sent back.2. The heading and the logo both said "Awesome Authorization".
media/logo.svgcarried the wordmark in two<text>elements. Those are gone; the shield mark remains and the Markdown heading is now the only place the name appears. The viewBox is cropped to the mark and given explicit dimensions since the width can no longer be set from the img tag.3. The logo linked nowhere.
It now links back to the repo. Switching from a raw
<img>to a Markdown image-link also means no newMD033inline-HTML violations — the count stays at the one pre-existing<div align="center">.Checks
markdownlint-cli2: 1 issue, the pre-existing<div>. No regression.awesome-linton the file: no content errors; heading and badge rules still satisfied.