feat(landing): update the hero screenshot and supporting copy

[bishopBethel]

The hero image had only ever existed in the working tree, so production was still serving the previous screenshot. Commit the updated devasign-app.svg along with the hero paragraph it was updated alongside, so the section ships as a whole rather than a new image above stale copy.

[devasign-agent]

DevAsign review — changes requested

End goal

Update the landing hero section by committing the new devasign-app.svg screenshot together with the accompanying hero paragraph copy.

Acceptance criteria not met

These requirements aren't satisfied by the current diff yet — each shows what was required, why it isn't met, and a suggested fix.

1. Include the hero paragraph copy change in this PR

2 — Not met. Required: The hero paragraph copy is updated alongside the new screenshot.

Reasoning: The only file changed in the diff is src/assets/devasign-app.svg. No component, markup, or copy file (e.g. a hero section .tsx/.jsx) appears in the diff, so there is no visible update to the hero paragraph copy. The PR description claims the copy was updated alongside the image, but that change is not present in the provided diff. The PR goal is to ship the new screenshot together with its updated hero paragraph so the section ships as a whole. The diff only modifies the SVG asset; the hero copy edit is missing, leaving the requirement unmet.

1 of 2 acceptance criteria met

Show met criteria

• 1 — The updated devasign-app.svg hero screenshot is committed to the repository.

---

One prompt to fix all of this — paste into your AI coding agent

You are helping fix PR "feat(landing): update the hero screenshot and supporting copy" in devasignhq/website. Automated review surfaced the items below — failed acceptance criteria and review findings. Each item states what was required, what's wrong with the current diff, and how to fix it; the embedded fix blocks include the expected behavior and the relevant diff hunk. Apply each fix so the item is resolved. Items tagged **Blocker** gate approval; the rest are advisory but worth addressing. Don't introduce changes beyond what's listed.

## End goal
Update the landing hero section by committing the new devasign-app.svg screenshot together with the accompanying hero paragraph copy.

## Failed acceptance criteria

### 1. Required: The hero paragraph copy is updated alongside the new screenshot. (2)
What's wrong now: The only file changed in the diff is src/assets/devasign-app.svg. No component, markup, or copy file (e.g. a hero section .tsx/.jsx) appears in the diff, so there is no visible update to the hero paragraph copy. The PR description claims the copy was updated alongside the image, but that change is not present in the provided diff.

How to fix:
Fix: Update hero paragraph copy to ship with the new screenshot

File: <the hero/landing component containing the hero paragraph, e.g. src/components/Hero.tsx>
Symbol: Hero (or the hero section component)

Issue:
This PR commits the updated devasign-app.svg hero screenshot but contains no change to the hero paragraph copy. The stated intent is to update the copy alongside the new image so the section ships together, but the copy edit is absent from the diff.

Expected behavior:
The hero paragraph text is updated in the same PR as the new screenshot, so the diff shows both the SVG asset change and the corresponding hero copy change.

Suggested approach:
Locate the hero section component that renders the paragraph beneath the DevAsign hero image, update its text to the new copy, and commit it in this PR. Verify the component imports src/assets/devasign-app.svg so the image and copy are visibly paired.

Relevant diff:
```diff
diff --git a/src/assets/devasign-app.svg b/src/assets/devasign-app.svg
index 8749976..a5a3624 100644
--- a/src/assets/devasign-app.svg
+++ b/src/assets/devasign-app.svg
@@ -1,488 +1,483 @@
-<svg width="1508" height="771" viewBox="0 0 1508 771" fill="none" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
+<svg width="1506" height="856" viewBox="0 0 1506 856" fill="none" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
```

## Your task
Work through every item above — the failed acceptance criteria and each review finding. For each one: understand the gap from "What's wrong now", implement the change so the Required behavior holds (each fix block's `Expected behavior` describes the target state), and use the `Relevant diff` hunks as the anchor for where to edit. After each change, re-verify it resolves the item. Treat **Blocker**-tagged items as required (they block approval); address the rest too.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
devasign-website	Ready	Preview	Aug 1, 2026 5:56pm