feat(docs): surface external-service homepage links from block metadata

[waleedlatif1]

Summary

• Extract the new BlockMeta.url (external-service homepage, e.g. exa.ai) in generate-docs.ts and project it into integrations.json
• Render an outbound Visit link on every generated integration doc page via BlockInfoCard (design-system tokens, rel="noopener noreferrer")
• Add a Visit {name} CTA on the integration landing pages and a SoftwareApplication.sameAs entity link in the JSON-LD — strengthens topical authority for SEO
• Regenerated docs: per-page BlockInfoCard props + icons sync (picked up the newer Quartr logo that the docs copy had drifted from)

Type of Change

• New feature (non-breaking)

Testing

Tested manually — ran bun run generate-docs, verified 207 integrations carry a url, spot-checked MDX (with + without url), tsc --noEmit, bun run lint, and bun run check:api-validation all pass.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jun 13, 2026 9:05pm

[cursor]

PR Summary

Low Risk
Docs and presentational UI only; outbound links use standard security attributes with no auth or runtime behavior changes.

Overview
Integration doc pages now pass name and href into BlockInfoCard, which renders an optional Visit {service} outbound link (new tab, noopener noreferrer) under the hero icon when a homepage URL is provided. Internal blocks without a URL (e.g. Deployments, File, Knowledge) stay icon-only.

QuartrIcon is updated to a compact 32×32 mark (logo on white) instead of the wide wordmark SVG.

English integration MDX was regenerated in bulk so each third-party integration supplies the new props; formatting on BlockInfoCard usage is normalized.

^{Reviewed by Cursor Bugbot for commit 73a538f. Configure here.}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit deb0def. Configure here.}

[waleedlatif1]

@greptile review

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 2fa2183. Configure here.}

[greptile-apps]

Greptile Summary

This PR surfaces BlockMeta.url (the external-service homepage) across three doc surfaces: a "Visit" outbound link in each generated MDX integration page via BlockInfoCard, a CTA button on the integration landing page, and an about: Organization JSON-LD node for SEO. A new extractBlockMetaBody helper refactors shared meta-scoping logic between the existing extractTagsFromBlockMeta and the new extractUrlFromBlockMeta.

• generate-docs.ts: Adds extractBlockMetaBody + extractUrlFromBlockMeta; projects url into integrations.json and the MDX BlockInfoCard component attributes; refactors extractTagsFromBlockMeta to use the shared helper.
• BlockInfoCard: Gains name/href props and renders an outbound Visit link with rel="noopener noreferrer", design-system CSS tokens, and a formatHostname display helper. The surrounding wrapper gains not-prose to prevent Fumadocs prose styles from overriding the link appearance.
• Integration landing page: Adds a "Visit {name}" animated CTA button and an about: { '@type': 'Organization', … } JSON-LD entity (note: the PR description calls this sameAs, but about is the correct schema.org property for this relationship).

Confidence Score: 5/5

Safe to merge; all changed surfaces are additive doc/metadata features with no mutations to runtime workflow logic.

The doc-generation script changes are isolated to a new extraction path that produces optional metadata — blocks without a BlockMeta.url are unaffected and fall back to the existing rendering path. The BlockInfoCard and landing-page additions are purely presentational and conditionally rendered only when url is present. All 207 generated URL values are well-formed absolute HTTPS URLs verified by the author's manual run. No runtime logic, auth paths, database writes, or API contracts are touched.

No files require special attention beyond the doc-generation script, where a prior review already identified the regex word-boundary and MDX-escaping risks that apply to future block additions.

Important Files Changed

Filename	Overview
scripts/generate-docs.ts	Adds extractBlockMetaBody + extractUrlFromBlockMeta for URL extraction; refactors extractTagsFromBlockMeta to share the new helper. The regex in extractStringPropertyFromContent has no word-boundary guard (pre-existing risk, already flagged in prior review). MDX template interpolates name/url without escaping double-quotes (also pre-flagged).
apps/docs/components/ui/block-info-card.tsx	Adds name/href props and renders an outbound Visit link with correct rel="noopener noreferrer", design-system tokens, and a formatHostname display helper. Logic is straightforward; no issues found.
apps/sim/app/(landing)/integrations/(shell)/[slug]/page.tsx	Adds websiteUrl CTA button with animation and an about:Organization JSON-LD node for SEO. Implementation is clean; rel="noopener noreferrer" present. Note: PR description calls this a sameAs link but code uses about — about is semantically more accurate here.
apps/sim/lib/integrations/types.ts	Adds optional url field to Integration interface with clear JSDoc. All 207 current integration entries carry properly-formed https:// URLs.
apps/docs/components/icons.tsx	QuartrIcon replaced with a 32x32 logo variant embedding hardcoded fill='white' and fill='black' paths; does not inherit text-color / currentColor like every other icon in the file. This was flagged in the prior review.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Block source file\n(*BlockMeta.url)"] --> B["extractBlockMetaBody\nscopes to meta literal"]
    B --> C["extractUrlFromBlockMeta\nreturns url string or null"]
    C --> D["extractBlockConfigFromContent\nattaches url to BlockConfig"]
    D --> E["writeIntegrationsJson\nurl → integrations.json"]
    D --> F["generateMarkdownForBlock\nurl → MDX BlockInfoCard props"]
    E --> G["Integration Landing Page\nVisit CTA + JSON-LD about:Org"]
    F --> H["BlockInfoCard component\noutbound Visit link"]
    style A fill:#f0f4ff,stroke:#6b7280
    style G fill:#f0fff4,stroke:#6b7280
    style H fill:#f0fff4,stroke:#6b7280

Loading

_{Reviews (4): Last reviewed commit: "fix(docs): style block-info-card visit l..." | Re-trigger Greptile}

[greptile-apps]

QuartrIcon hardcodes fill='black' instead of fill='currentColor'

Every other icon in this file renders its paths with fill='currentColor' so they inherit the parent's text color — in BlockInfoCard that's text-white, which makes them appear as white silhouettes on the colored card background. The new QuartrIcon instead embeds a self-contained white rounded rectangle with black paths. On Quartr's color="#000000" card the icon will render as a white boxed app-icon floating inside a black panel rather than a clean white monochrome glyph like every other integration icon. If the card background ever changes (or the icon is used in a different listing context), the hardcoded colors will not adapt.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

MDX JSX attributes inject name and url without escaping

If a block's name or url value ever contains a double-quote ("), the generated MDX attribute will be syntactically broken — e.g. name="Google \"Foo\" Search" or href="https://example.com/?q=\"bar\"" would both corrupt the JSX attribute boundary and prevent the page from rendering. The values are developer-controlled today so the risk is low, but adding simple escaping (value.replace(/"/g, '"')) would make the template resilient to future additions.

[waleedlatif1]

@greptile review

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 0d54af8. Configure here.}

[greptile-apps]

Greptile Summary

This PR surfaces BlockMeta.url (the external-service homepage) through the docs pipeline: the generation script extracts it from block source files, writes it into integrations.json, and renders it as an outbound "Visit" link in both the MDX BlockInfoCard component and the landing-page integration hero. A SoftwareApplication.about entity is also injected into the JSON-LD for SEO.

• generate-docs.ts gains extractBlockMetaBody (shared by tags and URL extraction) and extractUrlFromBlockMeta; the URL propagates into integrations.json and into the MDX <BlockInfoCard> template.
• block-info-card.tsx gains optional name/href props and renders a styled outbound anchor below the icon card.
• The integration landing page [slug]/page.tsx adds a conditional "Visit {name}" CTA button and wires websiteUrl into the JSON-LD about field.

Confidence Score: 4/5

Safe to merge. The Visit links and JSON-LD additions are isolated, opt-in (only shown when url is present), and the docs generation script is not run at runtime.

The core rendering changes in block-info-card.tsx and page.tsx are clean and correct. The generate-docs.ts script has two related fragility points: the string-extraction regex lacks a word boundary (a docsUrl field in any future BlockMeta literal would silently be picked up as the service homepage), and name/url values are interpolated into JSX attribute strings without escaping quotes. Neither issue breaks any currently generated file, but they are easy to hit as new blocks are added.

scripts/generate-docs.ts — the extractStringPropertyFromContent regex and the MDX attribute template string warrant a quick fix before new block metadata containing URL-suffixed properties is added.

Important Files Changed

Filename	Overview
scripts/generate-docs.ts	Adds url extraction from BlockMeta; refactors extractTagsFromBlockMeta to share extractBlockMetaBody; injects url into integrations.json and MDX template. The regex used for url extraction lacks a word boundary, so a property named docsUrl in a BlockMeta literal would satisfy the pattern for url.
apps/docs/components/ui/block-info-card.tsx	Adds optional name/href props and renders an outbound Visit link below the icon card. Logic is clean; uses rel="noopener noreferrer" and a defensive formatHostname fallback.
apps/sim/app/(landing)/integrations/(shell)/[slug]/page.tsx	Adds conditional Visit CTA button and wires websiteUrl into JSON-LD as an about Organization entity. Clean conditional rendering, correct rel attributes.
apps/sim/lib/integrations/types.ts	Adds optional url field to the Integration interface with clear JSDoc. Non-breaking additive change.
apps/docs/components/icons.tsx	Replaces the old path-based QuartrIcon with a new one using a white rounded rect background and hardcoded fill='black' paths. The icon won't adapt to dark mode or colored parent contexts the way other icons do.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Block source file\n(*BlockMeta.url)"] --> B["generate-docs.ts\nextractBlockMetaBody\nextractUrlFromBlockMeta"]
    B --> C["integrations.json\n{url: 'https://...'}"]
    B --> D["MDX file\n<BlockInfoCard href='...' name='...' />"]
    C --> E["Integration type\n(types.ts url?: string)"]
    E --> F["[slug]/page.tsx\nwebsiteUrl"]
    F --> G["JSON-LD about\n{Organization, url}"]
    F --> H["Visit CTA button\n(outbound anchor)"]
    D --> I["BlockInfoCard\nVisit link (docs site)"]

Loading

Comments Outside Diff (1)

1. scripts/generate-docs.ts, line 1207-1213 (link)

   The regex built from propName has no word boundary, so searching for 'url' will match inside a longer property name. If a *BlockMeta literal ever contains a field whose name ends in url (e.g. docsUrl, thumbnailUrl, baseUrl) before the actual url field, extractUrlFromBlockMeta will silently return the wrong value and every generated doc page + integrations.json entry for that block will carry the wrong link.

_{Reviews (2): Last reviewed commit: "feat(docs): surface external-service hom..." | Re-trigger Greptile}

[greptile-apps]

The name and url values are interpolated directly into a JSX attribute string without escaping double-quote characters. A block whose name contains " or a URL with an embedded " would produce malformed JSX in the generated MDX, breaking the doc page for that integration.

Suggested change

	color="${bgColor || '#F5F5F5'}"${url ? `\n name="${name}"\n href="${url}"` : ''}
	color="${bgColor || '#F5F5F5'}"${url ? `\n name="${name.replace(/"/g, '"')}"\n href="${url.replace(/"/g, '%22')}"` : ''}

[greptile-apps]

QuartrIcon ignores color context

The new icon embeds a hard-coded fill='white' background rect and fill='black' paths, so it no longer responds to text-white or any CSS color applied by the parent. Every other icon in the file uses fill='currentColor', which lets the caller (e.g. BlockInfoCard's size-10 text-white) control the fill. On a dark-mode docs site or any non-white background the icon will render as a white square with a black logo regardless of the surrounding theme.

[waleedlatif1]

@greptile review

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 73a538f. Configure here.}