[site-conversion-fixes] hero data-residency line + works-with / audience band

[Smetools]

What & why

Two evidence-backed conversion additions from the deep-research website audit (docs/website-improvement-research-2026-06-14.md). The audit found most best-practice fixes were already shipped — these are the two genuine, safe gaps.

Changes (homepage only)

1. Hero data-residency/privacy trust line near the CTA — "Your data stays yours · never used to train models · built for Saudi PDPL & GDPR Article 22." The 🔐 Add branch protection: Only Abdelaziz can push to master #1 trust lever for the MENA + regulated beachhead; was previously only buried in the FAQ.
2. New "Works with" band after the hero — Claude · Codex · Gemini · Google Meet · Odoo · Telegram — plus "Built for Odoo partners · regulated teams · AI power-users." Honest pre-launch proof (real integrations, not fake customer logos) and answers who-it's-for above the fold.

Already live (not touched)

Self-serve CTA, Listen→Extract→Confirm→Act loop, FAQ + schema + llms.txt + robots (#62/#59), product screenshot (§03), founder trust line.

Deliberately NOT shipped (flagged for Hassan)

• "Otter + Loom + NotebookLM, verified" competitor anchor in the H1 — names 3 competitors on a Hassan-locked headline; brand-voice call, not force-shipped.
• Extra product-screenshot gallery — site already shows the product; would risk bloat (Wynter: too much text lowers conversion).

Proof

• npm run build — green, homepage / + all routes compiled.
• Diff: +45 lines, 1 file (app/components/home-commitment.tsx). No locked copy changed.

Type-1 brand surface → opened for Hassan's review + merge. Merge = deploys live to knowcap.ai.

Summary by CodeRabbit

• New Features
  • Added a "Works with" integrations section displaying partnerships on the home page.
  • Extended the trust band with privacy commitment information, including Saudi PDPL and GDPR Article 22 compliance details.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
knowcap-landing	Ready	Preview, Comment	Jun 14, 2026 5:47pm

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a privacy compliance trust row to the hero section with PDPL & GDPR copy and a new WorksWith integrations strip component. New CSS classes (cl-trust--privacy, cl-worksband) support the visual layout. WorksWith is inserted between <Hero /> and <Problem /> in the page render order.

Changes

Home page trust band and integrations strip

Layer / File(s)	Summary
CSS additions and hero privacy trust row app/components/home-commitment.tsx	Adds cl-trust--privacy and cl-worksband CSS rules (layout, typography, responsive), then inserts a second trust row in the hero section with data-privacy and PDPL/GDPR copy.
WorksWith component and page wiring app/components/home-commitment.tsx	Defines the WORKS_WITH integrations array, implements the WorksWith component rendering dot-separated integration labels and an audience line, and wires <WorksWith /> into HomeCommitment between <Hero /> and <Problem />.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐇 A new trust row, a band of friends,
Dots and labels, compliance blends,
PDPL, GDPR, all in line,
"Works with" partners, looking fine!
The rabbit hops between Hero and Prob,
Delivering integrations — what a job! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 75.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the two main changes: adding a hero data-residency line and a works-with/audience band to the homepage.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch hassan/site-conversion-fixes

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

app/components/home-commitment.tsx (1)

767-772: ⚡ Quick win

Consider moving inline styles to CSS for consistency.

Line 768 uses inline styles (style={{ display: 'inline-flex', alignItems: 'center', gap: 18 }}), while the rest of this file consistently uses CSS classes. Moving this to a CSS class would improve maintainability and match the established pattern.

♻️ Suggested refactor

Add a CSS class for the wrapper:

+.cl-works-item-wrap{display:inline-flex;align-items:center;gap:18px}

Then update the JSX:

 {WORKS_WITH.map((name, idx) => (
-  <span key={name} style={{ display: 'inline-flex', alignItems: 'center', gap: 18 }}>
+  <span key={name} className="cl-works-item-wrap">
     {idx > 0 && <span className="cl-works-dot" aria-hidden="true">·</span>}
     <span className="cl-works-item">{name}</span>
   </span>
 ))}

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@app/components/home-commitment.tsx` around lines 767 - 772, Move the inline
styles from the span element in the WORKS_WITH.map function to a CSS class for
consistency with the rest of the file. Create a new CSS class (following the
naming pattern of existing classes like "cl-works-dot" and "cl-works-item") that
contains the styles display: inline-flex, alignItems: center, and gap: 18. Then
replace the style prop on the span with a className prop referencing this new
CSS class.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@app/components/home-commitment.tsx`:
- Around line 767-772: Move the inline styles from the span element in the
WORKS_WITH.map function to a CSS class for consistency with the rest of the
file. Create a new CSS class (following the naming pattern of existing classes
like "cl-works-dot" and "cl-works-item") that contains the styles display:
inline-flex, alignItems: center, and gap: 18. Then replace the style prop on the
span with a className prop referencing this new CSS class.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: b2a17c91-f881-4410-96cf-6bb217ca04f2

📥 Commits

Reviewing files that changed from the base of the PR and between 65710b7 and 8426f15.

📒 Files selected for processing (1)

• app/components/home-commitment.tsx