Semway is a Norwegian digital-marketing company. INFIGO built their first website when the firm was starting out, and has been close to that site, in one role or another, ever since.
01 · The context
Over a decade, every website becomes several websites.
A company that lasts changes its skin every few years - new positioning, new design, new people with opinions. The usual pattern is that each redesign also means a new supplier, and everything learned about the previous build leaves with them.
This engagement is the other pattern: suppliers of the design may vary, but the engineering stays in one place.
02 · The build
First the site, then the redesigns.
INFIGO built the original site when Semway started, and then coded the redesigns that followed as the company grew - new designs, new content structures, the same hands doing the implementation each time. Every version ran on WordPress, built to be maintained rather than merely launched.
03 · The long haul
Today we maintain a build that is not ours - deliberately.
The newest design was coded in-house at Semway. The people who wrote it have since moved on, and the code they left needed someone who could own it. That someone is INFIGO: we keep the current site updated and running, on a codebase we did not write.
Taking over another team’s code and carrying it responsibly is its own discipline - reading before changing, updating without breaking, resisting the reflex to rewrite. A relationship that has survived a first build, several redesigns and a handover in both directions is what long-term engineering support actually looks like.
What we delivered
- The company’s first website, built at its founding.
- The coded implementations of the redesigns that followed.
- Ongoing maintenance of the current, in-house-built site - a takeover, done properly.
