Skip to content

Constrain landing meeting asset width#5816

Merged
ComputelessComputer merged 4 commits into
mainfrom
fix/landing-meeting-asset-width
Jun 30, 2026
Merged

Constrain landing meeting asset width#5816
ComputelessComputer merged 4 commits into
mainfrom
fix/landing-meeting-asset-width

Conversation

@ComputelessComputer

@ComputelessComputer ComputelessComputer commented Jun 30, 2026

Copy link
Copy Markdown
Collaborator

Cap the meeting capture visual at 260px so the asset renders smaller in the privacy section.


Note

Low Risk
Presentation-only Tailwind class changes on the marketing landing route; no logic, data, or auth impact.

Overview
Tightens vertical rhythm on the home page so the hero, workflow demo, and credibility marquee sit closer together.

The hero section and HeroWorkflowDemo lose large bottom padding (pb-20/pb-24pb-2/pb-4, and pb-16pb-8). The Trusted by people in block is de-emphasized with smaller heading text (text-3xltext-base/md:text-lg), less section padding, and a tighter gap above the logo marquee.

In the privacy meeting visual, the Google Meet–style capture card is capped at max-w-[260px] instead of stretching full width on desktop (md:w-full removed), so the asset reads smaller in that column.

Reviewed by Cursor Bugbot for commit 205ad94. Bugbot is set up for automated code reviews on this repo. Configure here.

Cap the meeting capture visual at 260px so the asset renders smaller in the privacy section.
@netlify

netlify Bot commented Jun 30, 2026

Copy link
Copy Markdown

Deploy Preview for old-char canceled.

Name Link
🔨 Latest commit 205ad94
🔍 Latest deploy log https://app.netlify.com/projects/old-char/deploys/6a4343e3a3f6a8000862972b

@ComputelessComputer ComputelessComputer merged commit b75fe13 into main Jun 30, 2026
9 checks passed
@ComputelessComputer ComputelessComputer deleted the fix/landing-meeting-asset-width branch June 30, 2026 04:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant