Customer-facing website
Built a responsive website that gives the boats, fabrication quality, and product details a clear hierarchy across desktop and mobile.
← All projectsPublic website and operations hub
E13 Marine
A connected digital experience that pairs a customer-facing marine website with an internal hub for the content and workflows behind the business.
The challenge
E13 needed more than a polished public presence. Customers needed a clear way to understand the brand and its boats, while the team needed a practical hub for keeping information organized and supporting the work behind the website.
My approach
I treated the website and hub as two sides of one product. The public experience focuses on brand, boats, technical detail, and clear next steps; the hub gives the team a structured place to manage the information and processes that feed that experience.
Before
Customer-facing boat information and the internal work required to maintain it could easily drift into separate, inconsistent processes.
Automation
A structured hub supports repeatable content and operational updates while the public website turns that source information into a clear buyer experience.
Operational result
Customers get a polished, current website and the team gets a more maintainable system for keeping the experience useful.
What I built
Turning the workflow into a usable product.
E13 Hub
Created a supporting internal experience that organizes business information and gives the team a practical home for recurring website and operational work.
One connected content system
Structured content so the public story and the internal source material stay aligned instead of becoming two disconnected sets of information.
Key decisions
Clarity before complexity.
Design for two audiences
Customers need confidence and clarity; the internal team needs speed and consistency. Each surface serves its audience while supporting the same business.
Make the website maintainable
The hub turns updates into a repeatable workflow, helping the public website remain useful as boats, content, and business needs change.
Engineering the solution
What makes the product dependable.
- Responsive public interface and reusable content patterns
- Structured information architecture across the website and hub
- Accessible navigation, hierarchy, and interaction states
- Deployment and ongoing content workflow design
Current outcome