ANDRES / Shared website rules / Review copy

Open homepage
ANDRES Construction

Visual decision board
August 4, 2026

Six shared choices

One direction.
Applied on purpose.

The homepage is our working reference. These choices determine how that direction behaves across every remaining page type. Each comparison shows BMC’s recommendation beside the literal sitewide interpretation of the request.

01

Margins + section spacing

The homepage already sets the horizontal margin: 40px on desktop, fluid through tablet, and 24px on mobile. The choice below applies only to vertical section spacing.

Recommended

One vertical system, three settings

Responsive
Compact
Standard
Feature
  • Spacing stays consistent because every section uses the same approved scale.
  • Short navigation bands, normal content, and major storytelling moments can breathe differently.
  • Mobile spacing can tighten without forcing desktop proportions onto a phone.

Literal sitewide interpretation

One fixed vertical gap everywhere

Uniform
Same
Same
Same
  • Every section receives the same reduced top and bottom space.
  • Dense content becomes cramped while small sections can still feel visually empty.
  • The rule ignores the different jobs performed by a hero, a list, and a feature story.
02

Button consistency

Does “all buttons the same size” mean a consistent component, or the exact same width regardless of the words inside it?

Recommended

Same height. Natural width.

Clear rhythm
View projects Our services Start a conversation
  • Height, type, color, corners, and interaction are identical.
  • Width follows the label, which preserves readable spacing and works better on mobile.
  • Primary and secondary buttons remain recognizable across every page.

Literal sitewide interpretation

Every button is one width

Fixed box
View projects Our services Start a conversation
  • Short labels carry unnecessary empty space.
  • Long labels wrap or require a larger fixed width that becomes difficult on phones.
  • The visual box is consistent, but the reading experience is not.
04

Arrow and icon language

Should ANDRES standardize the restrained navigation icons already used on the site, or should raw text characters replace arrows everywhere?

Recommended

Use the existing navigation set

Already in use
Open pageFooter and page links
Next projectPrevious and next controls
ContinueVertical scroll cue
  • These exact thin-stroke paths are already used in the footer, project carousel, and scroll cues.
  • Page links, previous/next controls, and vertical movement retain distinct meanings.
  • No new brand device is required; the existing SVGs stay sharp and accessible at every size.

Literal sitewide interpretation

Use < and > as the arrows

Text glyph
View projectForward>
Back to projectsBack<
Open reportExternal?>
  • The shape varies with font, weight, browser, and platform.
  • A text symbol cannot clearly distinguish forward navigation from an external link.
  • The resemblance is immediate, but the behavior is less precise.
05

Project image ratios

Is the square crop a homepage composition choice, or the new rule for every project image across the website?

Recommended

Square feature. Landscape catalog.

Image-led
The National construction project shown in a square homepage crop

Homepage feature

Editorial crop

The National construction project shown in a landscape catalog crop

Project catalog

Architecture-friendly crop

  • The homepage gets the stronger square composition Jonathan requested.
  • The catalog retains a wider frame that better suits buildings and jobsite photography.
  • Each placement uses the ratio best suited to its job.

Literal sitewide interpretation

Square project images everywhere

Single ratio
The National construction project in a square homepage crop

Homepage

Square crop

The National construction project in a square catalog crop

Catalog

Same square crop

  • Every card aligns to one clean grid.
  • Wide elevations and contextual jobsite photography lose more of the frame.
  • The portfolio requires additional crop review and art direction.
06

Leadership titles

Should the website retain official titles, or should ANDRES approve a separate short label for every leader whose title needs to fit on one line?

Recommended

Official title stays authoritative

Accurate
Jonathan Haywood

Jonathan Haywood

Vice President,
Relationship Development

Optional approved display label: VP, Relationships

  • The official title remains the source of truth on profiles and in accessible content.
  • ANDRES may provide one approved short display label when a compact card needs it.
  • Designers and developers do not invent executive titles to make a layout fit.

Literal sitewide interpretation

Shorten titles to one line

Unapproved copy
Jonathan Haywood

Jonathan Haywood

VP Relationships

Short enough to fit—but this becomes a new public-facing title unless ANDRES approves it.

  • Every card gets a short, single-line label.
  • Meaning and seniority can change when titles are abbreviated informally.
  • The same issue repeats across operations, relationship, and location-specific roles.

Recommended approval boundary

Lock the system once.

Use three representative pages to approve the reusable rules. After that approval, the remaining layouts become implementation—not a new design exercise on every page.

01

Homepage

Confirms the overall visual language and top-level story.

02

Service detail

Tests copy, proof, lists, calls to action, and responsive content.

03

Project detail

Tests photography, facts, galleries, recommendations, and mobile flow.

04

System locked

The approved rules carry through Locations, About, Insights, Article, and Contact.

Your decision summary

  1. Spacing — No selection
  2. Buttons — No selection
  3. Footer navigation — No selection
  4. Arrow language — No selection
  5. Project image ratios — No selection
  6. Leadership titles — No selection