Skip to content

Apply the copy and layout trims from the 1 Oct client review - #7

Merged
laveshparyani merged 1 commit into
mainfrom
feat/meeting-trims-01oct
Oct 1, 2026
Merged

laveshparyani merged 1 commit into
mainfrom
feat/meeting-trims-01oct

Conversation

@laveshparyani

Copy link
Copy Markdown
Collaborator

Changes the client walked through on the 1 Oct call. All of them are removals
or re-weightings — no new surface.

Copy

  • Drop "Architectural & Design Consultancy" from the hero eyebrow and from
    under the footer wordmark. He called it "collaborative designs" on the call;
    the recording confirms he was pointing at this line.
  • Footer Instagram is now the icon alone, enlarged (15px → 26px). The handle
    moves to aria-label so the link is still announced, and it gets a 44px hit
    area now that there is no text to click.

Contact affordances

  • Add Instagram to the header, beside Enquire. It stays visible below 620px
    where .nav__cta is hidden — the practice's first enquiry arrived through the
    profile, so it should not be the thing that drops on a phone.
  • Remove the inline phone beside "Start a project" in the hero and in the
    CTA band. The floating Call button already covers that intent, and it carries
    both numbers.
  • Contact page: the two numbers were inline-flex with a size step between
    them, so they ran onto one line and collided. They now stack at one size.
    Both numbers stay published, equally — the client was explicit about that, and
    the --alt modifier is gone entirely so there is no variant left to drift.

Layout

  • Footer columns: auto-fit split the row evenly and left Contact ~204px,
    just under what kalapritidesigns@gmail.com needs, so it broke mid-word.
    Weighted the columns so the width goes to the one that uses it. Follow is now
    a single icon plus a short link, so it had room to give.

Verification

  • npm run lint and npm run build clean.
  • Checked the minified CSS, not just the source: the five dead rules are
    gone, the new ones survive, and the 821px rule is still scoped to its media
    query (LightningCSS rewrites it to width>=821px).
  • Contact numbers measured in the DOM — identical font-size, font-family,
    font-weight, color, icon size, gap and height; stacked 6px apart.
  • Zero horizontal overflow at 375px. No console or server errors.

Changes the client walked through on the call, all of them removals or
re-weightings rather than new surface:

- Drop "Architectural & Design Consultancy" from the hero eyebrow and from
  under the footer wordmark. (He called it "collaborative designs" on the
  call; the recording shows he was pointing at this line.)
- Instagram in the footer is the icon alone, enlarged, with the handle moved
  to aria-label so the link is still announced.
- Add an Instagram link to the header beside Enquire. It stays visible below
  620px where .nav__cta is hidden — the practice's first enquiry arrived
  through the profile, so it should not be the thing that drops on a phone.
- Remove the inline phone beside "Start a project" in the hero and the CTA
  band. The floating Call button already covers that intent.
- Contact page: the two numbers were inline-flex with a size step between
  them, so they ran onto one line and collided. They now stack at one size,
  which is also what he asked for — both numbers published equally.
- Footer columns: auto-fit split the row evenly and left Contact ~204px,
  just under what the email needs, so it broke mid-word. Weight the columns
  so the width goes to the one that uses it.

Verified against the production build: the dead rules are gone, the new ones
survive minification, and the 821px rule is still scoped to its media query.
@laveshparyani
laveshparyani merged commit 31ed715 into main Oct 1, 2026
3 checks passed
@laveshparyani
laveshparyani deleted the feat/meeting-trims-01oct branch October 1, 2026 04:24
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