Paul Petruzzi website

This project was a real professional website build for a criminal defense law practice — a context where the site isn’t just marketing, but part of how a firm presents itself to people under stress, often searching quickly, on mobile, and judging trust in seconds.

The site was structured and implemented in Nuxt 3, with the aim of delivering a strong, credible, modern law firm presence: clear hierarchy, readable service content, and a foundation that supports both user confidence and long-term SEO growth — not a one-off brochure page.

The work involved design and technical thinking together: how sections repeat, how practice pages scale, how navigation and internal linking reinforce context, and how the frontend stays maintainable as the site grows. That combination — presentation, structure, and execution — is what made this a meaningful, real-world build.

A law firm site has to earn trust before anything else. Visitors may be anxious, rushed, or comparing options — so the design can’t feel cheap, gimmicky, or like a generic template. At the same time, it still needs to guide people toward contact in a way that feels appropriate and restrained, not pushy, in a sensitive legal context.

Structuring service and practice-area content is its own problem: pages need to be distinct enough to be useful (for users and for search) without overlapping in confusing ways. The site also had to feel modern and authoritative— not dated, but not flashy either.

The build was never only visual. It required a foundation that supports long-term SEO and content expansion: predictable routes, consistent page patterns, and metadata that matches what each page actually says — so the site can grow without turning into a patchwork of one-off layouts.

The visual direction was premium and restrained: strong typographic hierarchy, generous spacing, and a layout that prioritises clarity over decoration. Every section should answer “what is this for?” before asking for attention.

Conversion-focused layout meant obvious CTAs and contact paths — but placed with restraint so the site still feels respectful. Legal audiences don’t respond well to pressure tactics; the design had to signal authority and calm first.

Repeated patterns — hero treatments, service summaries, trust-oriented blocks — were designed to compose consistently across routes, so the experience feels cohesive whether you land on a practice area or a location page. That consistency is part of what makes a firm feel real and established, not stitched together page by page.

The site is built in Nuxt 3 with Vue 3 and a component-driven structure: shared layouts, reusable sections, and page templates that map to real user journeys — services, locations, contact, and supporting content.

The emphasis was on scalable structure and maintainability: fewer duplicated layouts, clearer boundaries between components, and styles organised with LESS and shared tokens so the UI stays coherent as pages multiply.

The frontend is responsive end-to-end, with semantic HTML, sensible heading order, and focus states that make sense for keyboard users — not an afterthought. Implementation stayed performance-aware: practical choices about how pages are composed and delivered, aligned with the reality of real users on real devices.

The project delivered a more polished, structured, and credible web presence for the practice — one that presents services and locations with clarity and supports future content work without forcing every update to be a bespoke layout job.

It created a stronger foundation for ongoing SEO and content iteration: pages are easier to reason about, metadata aligns with on-page content, and the architecture supports growth rather than fighting it.

From a product perspective, the site brings design, structure, and frontend implementation together in a more cohesive way — a single narrative that matches how the firm actually wants to be perceived. I’m not attaching fabricated metrics; the outcome here is qualitative, structural, and professional — and that’s the honest read.

Information architecture pays dividends. When URLs and headings tell a coherent story, both users and search engines benefit — and the codebase stays easier to extend.

In legal and other high-stakes niches, trust is designed through detail: rhythm of copy, spacing, motion, and tone. Small inconsistencies read as carelessness.

SEO thinking and frontend execution aren’t separate phases. Metadata, internal links, and component structure are part of the same system — treating them that way avoids expensive rework.

Real-world sites need strategy as well as delivery. A beautiful layout that doesn’t scale or doesn’t match page intent is a liability. Building for the next page — not just the current screenshot — is what separates durable work from one-off builds.