Oceanecostructure

Oceanecostructure is a marine engineering startup focused on ecological construction methods in marine and coastal environments — structures built with materials and techniques that minimize disruption to marine ecosystems and support habitat recovery. Their work sits at the intersection of civil engineering, marine biology, and environmental regulation.

This was one of my first freelance projects, and it presented a challenge common to early-stage technical companies: a highly credible technical team, a differentiated and genuinely interesting proposition, but no clear way to communicate it to clients, partners, and regulators who needed to understand the work without a marine engineering background.

What Was Built

A WordPress corporate website built to communicate Oceanecostructure’s proposition clearly to three distinct audiences: potential clients (port authorities, coastal development projects, offshore energy companies), potential partners and subcontractors (engineering firms, environmental consultancies), and regulatory bodies involved in project approval processes.

The architecture was kept simple deliberately. No complex plugins, no heavy page builders — a clean custom WordPress theme built from scratch with PHP templates, structured around the project portfolio and the services offered. The priority was page weight and load time: the marine engineering sector often involves site visits and fieldwork with slow connections, and client-side-heavy sites create friction at the wrong moment.

Content Strategy

A significant part of the project was structuring the content itself. Technical companies often write about their work the way engineers talk to other engineers — accurate but opaque to decision-makers. For Oceanecostructure, the challenge was presenting ecological marine construction methods in language that port development committees and environmental impact reviewers could engage with, without losing the technical credibility that mattered to engineering partners.

This involved close collaboration with the founders to understand which projects could be documented publicly, what regulatory certifications were relevant to mention, and how to frame the ecological angle without it reading as greenwashing.

Technical Decisions

WordPress for content management because the founders needed to update project documentation and add new case studies independently. PHP templates from scratch rather than a commercial theme, which kept the output clean and the page weight low. CSS written deliberately — no framework, just structured stylesheets — which was appropriate for a site with limited interactive complexity but specific visual requirements for presenting technical diagrams and project photography.

One of my earliest freelance projects. The constraints of working with a small budget and a technically sophisticated but content-inexperienced client shaped how I think about scoping these engagements.