Lambert.Architectural Lighting
From a catalog
to a product a buyer can assess.Jardine redesigned and coded Lambert’s website around the work of architects and lighting designers: find the right family, compare the details and prepare a specification request.
- Designed & developed by
- Alex Jardine
- The work
- Website structure, identity refinement, design & development
- The audience
- Architects, lighting designers & specifiers
Website pages
Product families
Legacy category terms retained
Delivery facts from the completed build. Traffic, inquiry and revenue improvements are not claimed.
Website design: find lighting by space and application.
The former site placed much of the product information inside a 46 MB catalog PDF. The rebuild brings that information onto pages buyers can read, share and return to while planning a project.
Choose by application
Grazer, cove, downlight, suspended linear and wall wash each get a dedicated page. The starting question is what needs lighting, with product names and technical details available as the buyer moves further in.
Keep the details beside the choice
Seven configurations sit within the five families. Product pages bring configuration information, specifications and file-request actions together, so the buyer can review them in context.
Refine the existing identity
Jardine refined Lambert’s logo for digital use and built the page design around strong typography, architectural photography and light against dark surfaces. Three project pages provide another way to explore the range in context.
Inspect the website and comparison
Explore the rebuilt interface on desktop and mobile.
The former-site view is Jardine’s reconstruction of the available legacy experience, not an archived production screenshot.
What stayed familiar
Fourteen category terms and four established route concepts carried into the new structure.
The navigation changed, but the rebuild retained the catalog language existing buyers knew. Those terms sit within the new product model rather than disappearing when the design changes.
Product range, gallery, contact and specification support remain recognizable destinations. This preserves a connection to the former site while giving each page a clearer purpose.
Development: light explains the product.
The lighting effects have a specific job: show how each family distributes light across a surface. Product names, descriptions and specifications remain readable without needing to trigger an animation.
A different effect for each family
Each application has its own lighting stage. As it enters view, the light rises and settles, revealing the difference between grazing a wall, washing it evenly and lighting a horizontal surface.
Motion with a quieter version
The implementation checks reduced-motion and reduced-data preferences and provides a settled lighting state. It also caps rendering resolution to limit the work required by the visual effects.
Pages generated from shared content
Product and project information lives in a central content file. A build script turns it into static HTML, keeping the thirteen pages consistent without requiring each one to be maintained separately.
Images, page checks and search setup
The less visible work that supports the finished interface.
- Photography
- AVIF and WebP image versions at several sizes, with small previews while the full image loads. The build copies the versions referenced by the generated pages.
- Typography
- Self-hosted fonts keep type within the site’s own asset delivery.
- Build checks
- Validation checks for missing product families, page headings, image dimensions and alternative text before release.
- Search structure
- Page-specific metadata, canonical URLs and structured data accompany the generated pages.
The specification request
The product and file are filled in before the buyer types a word.
Asking for a file from a product page opens Lambert’s request form with the product and file already filled in, and the form checks each entry before it is sent. Buyers ask for exactly what they need without retyping it.
Jardine’s part of the project is complete. Lambert’s own team chose to connect the form to their systems and add new products in-house, so the range can keep growing on their schedule.
A technical catalog brought together through website redesign, custom development and SEO migration services, with a structure that keeps the buyer’s next decision in view.
Planning a similar product range? See how we build manufacturing websites.