The audience is a lighting engineer looking for a specification, not a shopper, and that changes what the site owes them.
39 yrs
Manufacturer in market
two production plants
Spanish
First, not translated
copy, formatting and search
Dozens
Fixture families
each with full technical detail
The problem
Lumenac manufactures LED lighting: interior and exterior ranges across dozens of fixture families such as Venus, Stadium, Flow and Backlight, each carrying the technical detail a specifier actually reads.
The visitor is usually an engineer or an architect looking for a specific specification, not a shopper browsing. And they are reading in Spanish, so a site built in English and translated afterwards would be the wrong way round.
What we did
Built as a Vue single-page application on a Node backend, with product search, a downloadable catalogue and a language switcher.
Spanish is the primary locale rather than a translation layer, so copy, formatting and search behaviour were built for it from the start. A projects gallery of installed work sits alongside the catalogue, which for a manufacturer is the proof that the specification performs outside a datasheet.
The outcome
Engineers and architects search the full fixture range by technical attribute in their own language, download the catalogue, and see the installed work behind the specification.
Frontend
Backend
Localisation
What we learned
Build for the primary locale first. Translating an English-first site into Spanish leaves search and formatting subtly wrong in the market that matters most.
For a manufacturer, installed projects are the proof. A datasheet says what it should do; a photograph of a stadium says it did.
Thirty minutes with the engineer who would lead the project. You will leave with an opinion on what to build, what to skip, and roughly what it costs, whether or not you hire us.
2 build slots open · Next start: early next month
What happens next