Skip to content
All work
01Pre-launchCorporate Web Experience

Trihedron Website

A modern corporate web experience designed to communicate engineering services through clear visual design and intuitive navigation.

Illustrative artwork · not a screenshot
Illustrative artwork representing the project — not a screenshot of the product.
Type
Corporate Web Experience
Year
2026
Status
Built and working; final content sign-off before go-live.
Stack
HTML, CSS, JavaScript (ES modules)…

The problem

An engineering services business needs its website to explain four quite different service lines — manpower, automation, metrology and software — to very different audiences, and to turn interest into a qualified enquiry.

Objectives

  • 01Give each service pillar its own clear, focused page
  • 02Make requesting specialists a guided, low-friction process
  • 03Let non-developers update news, vacancies and FAQs without touching HTML
  • 04Deliver a distinctive visual identity without hurting performance on low-power devices

Technology

  • HTML
  • CSS
  • JavaScript (ES modules)
  • Three.js
  • PowerShell
  • JSON content
  • Netlify

Approach

Deliberately framework-free: plain HTML, a single CSS design system and vanilla JavaScript. A small PowerShell build script stamps shared partials and JSON content into each page and generates the sitemap, so the deployed site is nothing but fast static files.

Key features

  • Dedicated pages for each service pillar
  • A shared multi-step specialist request form
  • News, vacancies, FAQs and case studies driven by JSON content files
  • Interactive 3D brand crystal and a dotted globe of regions served
  • Still-image fallbacks for the 3D scenes on phones and low-power devices
  • Redirects from the previous site's URLs to preserve existing links

Challenges

3D without the penalty

The 3D scenes needed to feel premium on a desktop without punishing a phone. Low-power devices get a pre-rendered still instead of a live WebGL scene.

Shared parts without a framework

Headers, footers and forms repeat on every page. A build step stamps shared partials into marked regions, keeping the output static while keeping the source maintainable.

Lessons learned

  • “A framework isn't always the right answer — a small build script can be the most maintainable option.”
  • “Content that changes often belongs in data files, not in markup.”

Links & access

No public demo or repository — this work is private to the organisation or still in progress. I'm happy to talk through the engineering in more detail.

Next project

PDF Auto-Mover