docs(readme): clickable badges, correct product colors/logos, and one-click setup tiles#198
Merged
Merged
Conversation
…d one-click setup tiles - Wrap every badge (Official, Status, MCP, Auth, Hosting, and all 6 product pills) in links - Fix Confluence color (172B4D dark navy -> Atlassian Blue 0052CC) - Fix Jira Service Management logo (was jirasoftware / invalid slug) with embedded JSM glyph - Convert product pills to two-tone shields (logo-left / title-right) - Add 'One-click setup' section with Cursor, VS Code, ChatGPT, Claude install deep links
jatinkrmalik
requested review from
SreeNerella,
blakewang-atlassian,
dmiller113,
dvenkatesh07,
ekahinga,
iosamaatlassian,
jvarghese2,
lsosa1 and
sfatlas
as code owners
GitHub's HTML sanitizer strips custom URL schemes (cursor://, vscode:), which made those two tiles non-clickable. Switch to the https redirect install entry points that GitHub permits. Also remove the tip callout.
Remove em dash and tailing-negation fragment; avoid restating the heading.
SreeNerella
previously approved these changes
Jul 8, 2026
sfatlas
reviewed
Jul 8, 2026
| <br><sub>Reference issues and log work in your codebase.</sub> | ||
| </td> | ||
| <td align="center" width="180"> | ||
| <a href="https://insiders.vscode.dev/redirect/mcp/install?name=Atlassian-Rovo-MCP&config=%7B%22url%22%3A%22https%3A%2F%2Fmcp.atlassian.com%2Fv1%2Fmcp%2Fauthv2%22%2C%22type%22%3A%22http%22%7D"> |
Collaborator
Author
There was a problem hiding this comment.
Good call. I validated https://vscode.dev/redirect/mcp/install?... and it returns a 302 to the stable vscode:mcp/install?... handler with the expected MCP config.
sfatlas
previously approved these changes
Jul 8, 2026
sfatlas
approved these changes
Jul 8, 2026
blakewang-atlassian
approved these changes
Jul 8, 2026
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
4 participants
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.
What & why
Polishes the README header and adds a frictionless install experience.
1. All badges are now clickable
Previously several pills were static images. Every badge now links to a sensible destination — including all 6 product pills (Jira, Confluence, JSM, Bitbucket, Compass, Rovo).
2. Fixed product colors & logos
#172B4D(dark navy) → Atlassian Blue#0052CC(correct brand color).jirasoftwarelogo (andjiraservicemanagementhas no Simple Icons slug) → now an embedded JSM SVG glyph on brand blue.3. Two-tone product shields
All product pills now use a two-tone style: logo on a darker left segment (
labelColor) with the product name on the brand-colored right segment.4. One-click setup tiles
New One-click setup section mirroring atlassian.com/platform/rovo-mcp, with native install deep links for Cursor, VS Code, ChatGPT, and Claude. (VS Code/OpenAI icons were removed from Simple Icons, so those two use embedded SVG glyphs.)
Validation
node scripts/validate-template.mjspasses (only a pre-existing unrelated hooks warning).Reviewer note
Badges/tiles render only after merge/preview on github.com — please spot-check the rendered README on the branch.