Skip to content

Add monochrome icons to integration navigation - #530

Merged
juecd merged 2 commits into
mainfrom
feature/add-integration-navbar-icons
Aug 31, 2026
Merged

juecd merged 2 commits into
mainfrom
feature/add-integration-navbar-icons

Conversation

@goosewin

@goosewin goosewin commented Aug 31, 2026

Copy link
Copy Markdown
Collaborator

Adds consistent monochrome icons to integration pages and navigation groups with tuned sizing, left alignment, and dark-mode support.


Note

Low Risk
Documentation and CSS-only changes with no impact on APIs, auth, or product runtime behavior.

Overview
Adds monochrome integration icons across the Mintlify docs so the Integrations sidebar and pages show consistent branding.

New SVGs live under images/integration-icons/. Standalone integration MDX pages (1Password, Browser Use, Hermes, Laminar, Stagehand, Terraform, Val Town, Vibium) now set an icon in frontmatter; nested nav groups in docs.json (Claude, Computer Use Models, Stripe Projects, Vercel) get matching icon fields.

style.css standardizes icon size and opacity, applies per-logo scale tweaks, reorders flex children so icons sit left of labels in sidebar buttons, and inverts icons in dark mode.

Reviewed by Cursor Bugbot for commit fc59ce3. Bugbot is set up for automated code reviews on this repo. Configure here.

@mintlify

mintlify Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Kernel 🟢 Ready View Preview Aug 31, 2026, 6:47 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

cursor[bot]
cursor Bot approved these changes Aug 31, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Risk Assessment: Low

Decision: No re-approval (existing approval stands). Risk did not increase after this update.

Re-evaluation (synchronize)

HEAD is still fc59ce39 (merge of main into the feature branch). The three-dot diff vs main is unchanged in scope from the prior Low assessment. The merge only brought already-merged main docs into the branch; it does not add PR-unique production logic.

This automation already approved this commit. A human reviewer has also approved. Per policy, this run does not approve again and does not dismiss.

What the diff actually changes

  • docs.json: additive icon paths on four existing Integrations nav groups (Claude, Computer Use Models, Stripe Projects, Vercel). No pages, redirects, theme, or OpenAPI changes.
  • 13 static SVGs under images/integration-icons/. Path/stroke logos only — no <script>, event handlers, foreignObject, or external resource loads.
  • 8 integration MDX files: one icon frontmatter line each. Page bodies are unchanged.
  • style.css: presentation rules scoped to /images/integration-icons/ (14px size, opacity/scale tweaks, dark-mode invert, flex order so icons sit consistently in sidebar buttons).

Why Low (not Very Low)

  • Docs presentation only. No application logic, auth, billing, permissions, or infrastructure.
  • Blast radius is Integrations sidebar/page icons on the Mintlify site.
  • Easy to reason about: icon path wiring plus CSS attribute selectors.
  • No CODEOWNERS file, so codeowner review is not required.
  • Classified Low rather than Very Low because the CSS flex order rules depend on Mintlify’s sidebar button DOM (li > button > div children). If that structure differs, icon/chevron alignment could look off. That is visual-only and easy to revert.
Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@juecd
juecd merged commit a9d59d0 into main Aug 31, 2026
4 checks passed
@juecd
juecd deleted the feature/add-integration-navbar-icons branch August 31, 2026 19:07
goosewin added a commit that referenced this pull request Aug 31, 2026
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.

2 participants