All insights

What we learned building academic websites in 2025

A MacBook with lines of code on its screen on a busy desk

December is for taking stock. Across this year’s projects — page-builder conversions, membership platform launches, AI augmentation pilots — a handful of lessons kept repeating. We are writing them down mostly so we follow them ourselves.

The short list

  • Editability is the product. Every client request eventually reduces to: can our own people change this safely? Build for that question first.
  • Subtraction wins arguments. The most appreciated deliverables this year removed things — plugins, steps in a renewal journey, fields from a form.
  • Volunteers are the real users. Society platforms succeed or fail on whether a volunteer can run them in an evening. Design for the treasurer, not the demo.
  • AI value arrived quietly. No transformation programmes — just minutes drafted, inboxes triaged, documents summarised, inside tools people already had.
  • Accessibility discipline compounds. Teams that put it in the definition of done stopped needing remediation projects at all.

The thread through all of it: longevity comes from restraint. Build less, build it natively, and make sure the people who live with the work can run it themselves. That is the bar for next year as well.

What we’re changing for 2026

Lessons are only real if they change behaviour, so: every build now ships with its pattern library documented inside the editor itself, where editors will actually find it. Accessibility review moved from pre-launch to per-component, because batching it was producing pre-launch panic. And we now ask membership platform clients to nominate their grumpiest volunteer as a tester — flattery finds fewer bugs than impatience.

We are also writing more down in public, this journal included. The sector shares its research; its operational knowledge mostly evaporates in handovers. Publishing what we learn is partly marketing, candidly — but mostly it is the discipline of having to be sure.

Predictions we’re willing to be wrong about

  • More institutions will convert away from page builders than adopt them, for the first time.
  • AI policies will consolidate around short, enforceable documents as the long ones quietly fail.
  • Accessibility regulation will reach further into member-facing platforms, not just public pages.
  • The greenest, fastest, most accessible site in any comparison will keep being the same site.

If any of those age badly, next December’s post will say so. Holding ourselves to that is rather the point.

The Tecology Brief

Get insights like this in your inbox.

Occasional, considered notes on academic digital — never noisy, unsubscribe in one click.

By subscribing you agree to our Privacy Policy. We only ever send The Tecology Brief — unsubscribe in one click, any time.

More insights

Overhead view of hands highlighting documents on a desk
Digital Strategy
How to run a website RFP a specialist can actually answer
Feature matrices select for confidence, not competence — every agency ticks every box. Five questions that actually discriminate, from the other side of the table.
3 min read
Read article
white and blue printer paper
AI in Academia
WordPress 7.0’s AI foundations: what a university web team should actually do with them
WordPress 7.0 shipped its AI foundations in May — an abilities registry, a core AI client, and connectors you control. The real opportunity isn’t the features: it’s that AI on your website just became governable.
3 min read
Read article
A smartphone is showing an ai assistant's interface.
Digital Strategy
When AI answers first: keeping academic content visible
More of your audience now gets their answer from an AI summary without ever reaching your site. The response isn’t panic or paywalls — it’s becoming the source the answer cites.
2 min read
Read article

Start a conversation

Tell us about the work you’re doing.

The best projects start with understanding the academic work behind them. Book a 30-minute call — no pitch deck, no pressure, just a conversation about what you’re trying to do.

Or email info@tecology.co — we reply within one working day.

Privacy Settings
This website uses cookies to enhance your browsing experience on our website and our services. You may revoke or change your consent settings at any time.

Accept all Essential only