Project indexEngineering website

MODUS Engineering
An engineering portfolio built around the next project.
I rebuilt the MODUS Engineering website so an architect, a facilities leader or a construction manager could find the experience that mattered to their decision.
Visit MODUS- My role
- Site strategy, design, writing, photography and development
- Scope
- 94 pages · 81 project profiles
Start with the client’s question
In business development I hear the questions before a project has a name. An architect wants to know who can protect the design intent. An owner may be thinking about a building they have to run for thirty years. A construction manager needs a team that understands what can be built within the budget.
I used those different starting points to organize the homepage. Services explain what the firm does. Project profiles give a reader a way to see that capability in a building. Contact sits close to both so a visitor can move from research to a conversation.
Give 81 projects a common structure
A qualifications package rarely calls for every project we have done. The same is true online. I developed a repeatable layout that lets a visitor scan a project, see the engineering scope and decide whether to keep reading. Consistent titles and image placement make it easier to move between examples.
Market One shows how the pieces fit. In my rooftop photograph the solar array fills the foreground and the city sits beyond it. The project narrative can then explain why the array matters to the building’s energy design.

From the photographer’s notebook

At Market One the engineering story was up on the roof. I put the solar array in the foreground so a reader could see exactly what the project description was referring to.
Open the photographs · File 08Keep both reading paths on a phone
On a wide screen there is room for the opening photograph, navigation and several ways into the work. On a phone the same elements compete for the first screen. I kept the service and portfolio routes close to the introduction and used the same project structure at both sizes.
Take responsibility for release
I used Codex during development and moved the site off WordPress. My work included content migration, testing, search setup, release and backups. Running the finished site is part of my marketing role, so I also had to make it practical to publish the next project or briefing.
The deliverable is a live 94-page site. Reviewers can move from the homepage into a single building, compare its story with other engineering projects and see how the design holds up beyond the first screen.
