improvement(landing): rewrite hero subheading for target keywords

[mzxchandra]

Summary

Rewrites the landing hero subheading with the SEO/GEO copy from the latest audit. The single line

Open source, with 1,000+ integrations and every major LLM. Build, deploy, and manage agents visually, conversationally, or with code.

becomes two paragraphs:

Sim is an AI agent and workflow builder for teams creating agents that automate real work. Design workflows visually, describe what you need in natural language, or use code for complete control.

Connect your agents to 1,000+ integrations and every major LLM, then deploy, monitor, and improve them from one collaborative workspace.

This leads by naming Sim (pulling the brand into the first 150 visible characters of the hero, alongside "AI Workspace" / "AI Agents" already in the H1) and works the priority keywords (ai agent builder, ai workflow builder, ai workspace) into visible, server-rendered copy.

The other five items from the audit (title tag, meta description, H1, product-demo paragraph, mothership H2) were already shipped in a prior landing SEO pass and already match the suggested wording, so this PR is only the outstanding hero delta.

Implementation

• hero.tsx passes the new two-paragraph description as a string[].
• LandingHeroHeader description prop widened string → string | string[]. A string still renders the exact same single <p> (so /workflows and the other solutions heroes are byte-identical); an array renders stacked <p>s at gap-3 within the same 58ch measure.

Type of Change

• Other: landing-page copy / SEO

Testing

Verified against a local dev build of the (landing) route:

• Server-rendered HTML contains both new paragraphs; the old line is gone; H1 unchanged.
• No console errors; zero horizontal overflow at 1280 / 1024 / 768 / 390.
• Desktop + mobile screenshots confirm the two-paragraph hero reads well; CTA row and right-side stat unmoved.
• /workflows solutions hero still renders its single-paragraph string path unchanged.
• biome check clean on both files; tsc --noEmit passes for apps/sim.

Checklist

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

Screenshots/Videos

Verified locally at 1280 and 390 widths (two stacked paragraphs, clean gap, no overflow). Happy to attach if useful.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JgSoC2yCfeDkSpZqafWoPA

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Aug 4, 2026 12:39am

[cursor]

PR Summary

Low Risk
Copy and presentational rendering only on the landing hero; shared header keeps backward-compatible string behavior for other routes.

Overview
Updates the main landing hero subheading to two SEO-focused paragraphs (brand + “AI agent/workflow builder” keywords in visible copy) instead of the previous single line about open source and integrations.

LandingHeroHeader now accepts description as string | string[]: a string still renders one <p> (solutions heroes unchanged); an array renders stacked paragraphs at gap-3 within the same 58ch measure.

^{Reviewed by Cursor Bugbot for commit c32f370. Bugbot is set up for automated code reviews on this repo. Configure here.}

[greptile-apps]

Greptile Summary

Rewrites the landing-page hero subheading as two SEO-focused paragraphs while preserving the existing single-paragraph behavior for other consumers.

• Expands LandingHeroHeader.description to accept either a string or string array.
• Renders array descriptions as stacked semantic paragraphs within the existing text measure.
• Replaces the homepage hero description with two static paragraphs highlighting agent building, workflows, integrations, deployment, and monitoring.

Confidence Score: 5/5

The PR appears safe to merge with no actionable defects identified.

The new array branch receives two distinct static paragraphs, while all existing shared-component consumers continue through the unchanged single-string rendering path.

Important Files Changed

Filename	Overview
apps/sim/app/(landing)/components/hero/components/hero-header/hero-header.tsx	Adds a backward-compatible multi-paragraph description path without changing existing string rendering.
apps/sim/app/(landing)/components/hero/hero.tsx	Replaces the homepage hero’s single description string with two distinct static marketing paragraphs.

_{Reviews (1): Last reviewed commit: "improvement(landing): rewrite hero subhe..." | Re-trigger Greptile}