Search by author: Stephen Evans

I have been working for the University since 2005. Prior to that I was a research scientist at Cambridge University studying different biological processes using magnetic resonance imaging (MRI). Academia wasn't for me, even though scanning strawberries and melons was fascinating! Now I oversee the work of the team and provide support where it is needed, particularly on the web development side of things. I am also an alum of the University, where I studied plant biology.

Stephen Evans
WordPress logo

Migrating WordPress multisite to WP Engine

The University hosts a multisite WordPress installation (wp.st-andrews.ac.uk) that provides websites and blogs for over 200 research groups and other University organisations. WordPress enables University staff and…

Terminalfour logo

T44U – Glasgow 2018

The T44U user group meeting in Glasgow on the 6 February was a great opportunity to meet up with others who are using the T4 content managements system and to find out the latest developments from TerminalFour. There…

Scottish Web Folk meeting

Scottish Web Folk is an informal group for anyone who works in digital in higher education in Scotland. The group meets three or four times a year at one of the universities in Scotland. It’s a great opportunity to…

Content model example

Content modelling – is it the future?

One of the main lessons from IWMW 2017 was the need to focus on content not websites. It is no longer sufficient to expect users to find information just via the University website as content is being accessed by an…

IWMW 2017 logo

IWMW 2017 – top five developer ideas

This year’s Institutional Web Management Workshop (IWMW) took place at the University of Kent in Canterbury between 11 and 13 July. It was a great opportunity to meet with others who are involved in higher education…

Streamlining the migration of courses

We have just completed the migration of over 300 undergraduate and postgraduate courses from TerminalFour (T4) version 7 to version 8. A blog post describes how we automated parts of this migration, but we were still…