chore(site): adjusted photos and seo

[NicholasKissel]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[railway-app]

🚅 Deployed to the rivet-pr-4177 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
website	😴 Sleeping (View Logs)	Web	Feb 18, 2026 at 9:16 pm
mcp-hub	✅ Success (View Logs)	Web	Feb 18, 2026 at 2:19 am
frontend-inspector	❌ Build Failed (View Logs)	Web	Feb 11, 2026 at 4:07 am
frontend-cloud	❌ Build Failed (View Logs)	Web	Feb 11, 2026 at 4:07 am
ladle	❌ Build Failed (View Logs)	Web	Feb 11, 2026 at 4:07 am

[NicholasKissel]

• chore(site): adjusted photos and seo #4177 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

PR Review: chore(site): adjusted photos and seo

Summary

This PR makes minor adjustments to the marketing website, including a bug fix in the 404 page animation, an image update, and SEO title refinement. The changes are small in scope and focused on polish.

---

✅ Code Quality

NotFoundPage.tsx (website/src/components/marketing/NotFoundPage.tsx:29-86)
The memory leak fix is well-implemented:

• Added isMounted flag to prevent state updates after unmount
• Properly initialized animationFrameId to 0
• Cleanup function correctly sets isMounted = false before canceling animation frame

This follows React best practices for cleanup in useEffect hooks with animation frames.

index.astro (website/src/pages/index.astro:80)
The title change is reasonable:

• Shorter, more focused SEO title
• Changed from "Rivet - Infrastructure for software that thinks." to "Infrastructure for software that thinks"
• More concise while maintaining keyword relevance

---

🔍 Observations

Image Binary Change
The PR modifies website/src/images/thinking/0000405625_OG.JPG (binary file). Without seeing the actual images, I cannot assess:

• File size impact (potential page load performance)
• Content appropriateness
• Image quality/compression

Consider documenting what changed and why in the PR description.

---

💡 Suggestions

1. PR Description: The PR template is unfilled. Please complete:

   • Summary of what changed and why
   • Type of change checkboxes
   • How this was tested
   • Self-review checklist

2. Testing: For the animation fix:

   • Manually verify the 404 page (/404) renders correctly
   • Confirm no console errors about state updates on unmounted components
   • Test that the bouncing pill animation continues smoothly

3. SEO Impact: The title change may affect:

   • Search engine rankings (removing "Rivet" brand name)
   • Browser tab/bookmark display
   • Social media sharing cards

   Consider whether the brand name should remain in the title for SEO and brand recognition.

---

✨ No Issues Found

• Security: No security concerns
• Performance: The memory leak fix improves performance
• Best Practices: Code follows React patterns
• Test Coverage: Frontend changes typically tested manually; no unit tests expected for marketing pages

---

📝 Minor Notes

• The animation fix addresses a real issue (memory leak) even though it may not be immediately visible
• The early return if (!isMounted) return; at line 35 is correctly placed before any state updates
• SEO title now matches common patterns (focus on value proposition rather than brand first)

---

✅ Recommendation

APPROVE with suggestions to:

1. Fill out the PR description template
2. Consider SEO implications of title change
3. Verify image size/quality of the binary change

The code changes are solid and improve the codebase.