Institutional Web Estates

A large institution commissions a flagship site. Faculties and departments then commission their own, each bespoke, each built by a different supplier, each accurate on the day it launched. Three years later the estate contains several hundred pages, an unknown number of them wrong, and no single team can say which.

The cause is not negligence. It is that the estate was designed as a collection of projects rather than as a system with a content model, a pattern library and a named owner per area.

Where the estate is large, the correct response is to standardise a pattern that departments populate, rather than to build bespoke pages that decay. This is less satisfying to commission and considerably cheaper to own.

The pattern carries the accessibility, performance and search behaviour. A department that fills in a pattern inherits compliance. A department that commissions a bespoke page inherits a liability.

A content model designed for the central team will fail, because the central team is not who updates the page. Model the content for the departmental administrator who has twenty minutes and no training, and the estate stays current.

Domains, hosting and accounts belong in the institution’s name with the institution as account holder, and every account created should appear in a handover register. Estates that fail this test tend to discover it during a supplier dispute, which is the most expensive possible moment.

Institutional templates rarely serve individual academics well. A staff listing is not a research profile, and an academic whose record is under-represented has a reputation problem the institution shares. This is the gap Academix Studio was created to close, at individual scale, on the same design system and ownership principles.