❌

Normal view

There are new articles available, click to refresh the page.
Before yesterdayMain stream

Key Takeaways from Scottish Web Folk 2026

2 November 2026 at 14:56

It was a busy day at the Scottish Web Folk conference, packed with ‘quick-fire’ sessions that lasted just 30 minutes each. The theme was Human vs Machine, however I took away no negative vibes about AI. The general feeling was positivity, and I enjoyed hearing how AI is altering things – how it can enhance our workflows and what it can add to a process with the correct guardrails in place.

Andrew Millar, Head of Digital Engagement & Marketing at the University of Dundee, kicked off the day. His session was thought provoking, and I jotted down several key takeaways that set the tone for the day ahead:

  • AI is a gateway to something both amazing and terrifying.
  • Just because things have worked out previously regarding innovation, we shouldn’t view that as comfort; we must accept the responsibility that comes with it.
  • Machines are now using our content and information to speak on our behalf.
  • How has this shift broken our existing metrics?
  • The machine has inserted itself into the conversation and is now providing the answers.
  • How do we determine if it is actually using our content?
  • We are using AI more and more in our daily lives, yet people are trusting it less.
  • A new acronym for me: GIGO – Garbage In, Garbage Out.

These points framed the day perfectly, as the subsequent presentations addressed these challenges and more.

The human side of digital transformation

It was interesting to hear from Mark Kennedy, Web Development Manager at Ulster University, about how he leads his web team of four, who support over 400 publishers. Mark and his team do not sit within Information Services, but instead they are integrated into Marketing and Communications. He mentioned that this can come with some challenges but also fosters more involved collaborations around content. For us in the Web Development Team at the University of Edinburgh, we are somewhat removed from the quality and accuracy of the content our publishers upload to their sites. As a wider team, we focus on providing the tools, training, and advice required to produce good-quality, accessible content. In contrast, at Ulster, the web team works closely with their MarComms colleagues, acting as gatekeepers for good content.

This close working relationship benefitted the team when Mark’s MarComms colleagues requested a sandbox to experiment with the new component-based platform, they built a publish-ready site within just one week. Although intended only as a playground, they fully embraced the reusable components – a surprising yet fantastic outcome that truly illustrated the human side of digital transformation. It struck me how accustomed we become to our own ways of working and the specific colleagues and disciplines we interact with daily. Mark’s talk sparked a thought: what would it be like if we were structured differently?

Post deployment testing

I also attended Rob McCreary’s talk (University of Dundee) on testing. He emphasised the importance of introducing automated testing techniques to enable quick fixes that can be deployed with confidence, specifically detailing how his team uses Behat feature files to confirm the live environment is healthy immediately after deployment. This was quite a complex topic, and while our team is just at the start of introducing automated testing, here are my main takeaways:

  • It’s not only developers who ship bugs – integrated content can too.
  • Import and integration failures can reach the live page before anyone notices.
  • A GitLab pipeline can run a test report and display the results clearly.
  • Build in a clean-up process: if entities (pages or users for example) are created as part of a test, they must be cleaned up afterwards.
  • Fast smoke tests can provide an early warning system.
  • Scheduled regression tests cover the wider system without holding up releases.

Side note: As I write this post, I find myself cross-referencing my notes, reviewing photos of the slides, and looking up terms I didn’t fully grasp during the sessions. This process itself feels like part of the lesson to me.


Thorough scoping with the help of AI

Matthew Jones and Robin Butler from Vepple, a virtual experience platform for universities, presented on using AI to draft development specifications. Their workflow begins with an MRD (Market Requirements Document), which outlines the problem statement and testable acceptance criteria. The most intriguing part of their talk was the concept of a ‘Grilling Session.’

At the time, I jotted down that this should be ‘thorough in a positive way,’ but I wasn’t entirely sure what that looked like. Researching it later revealed that this practice flips the conventional use of AI on its head. Instead of the user simply prompting the AI to generate content, the AI agent takes the lead. It prompts the developers with tailored, iterative questions – effectively ‘grilling’ the user to clarify scope and refine requirements. This rigorous interrogation ensures nothing is missed before the AI outputs a PRD (Product Requirements Document).

As they put it: “The agent writes with us and not for us.”

Once the specification is solid, the agent can slice it into actionable tickets for humans to follow, organising them into epics (projects). They also mentioned that automated tests are used to ‘pin’ existing functionality, ensuring that new changes remain small and manageable.

Takeaway: We don’t keep a platform in good shape by going faster – we do it by being thorough.

A presentation at Scottish Web Folk 2026

Findability and AI-driven search

Paul Costello and Rob Allen from Numiko talked about their work on findability with the University of Oxford. I know about SEO – it’s been around for some time! – but GEO and AEO were new to me. These stand for Generative Engine Optimisation and Answer Engine Optimisation, which are basically the same thing: looking at how AI-driven search works. This ties neatly back to the points from the introduction.

Honestly, this session was very content-focussed, so it’s not entirely relevant to my daily work as a developer. But I think it’s still really interesting and valuable for us to understand. And actually, it makes a lot of sense:

  • Think of a list of non-branded prompts that a user might type into an AI.
  • Structure your content around the questions users will actually ask.
  • Clear out old, out-of-date content.
  • Make sure how you talk about your organisation matches how the audience would phrase it or ask it.

It’s a simple idea – if people are asking AI questions in their own words, our content needs to speak the same language.

Extensive web estates and the importance of governance

To finish the day, I sat in on an unscripted presentation by Stratos Filalithis (University of Edinburgh) and Kris Purdy (University of Glasgow). There were no slides, just an open conversation between them and the audience about governing their massive web estates. It’s incredible just how large these estates are and I was genuinely surprised when Stratos quoted around 2,000 sites.

It’s a huge task – finding these sites, documenting them, establishing if they’re still required, tracking down owners, checking where they’re hosted, and essentially (fitting perfectly with the theme of the day) auditing the content.

The scary part? Sites from the late nineties could still be out there, serving AI agents with outdated answers! Eek!!!

Conclusion

Looking back at the day, the common thread wasn’t about fearing AI but was much more positive – it was about how we prepare our content and how we can employ agents to help with workflows, development, scoping to name just a few use cases.

Quality matters more than speed.

If we don’t audit our estates, we risk those forgotten sites from the late nineties feeding bad information to AI agents. And if we don’t speak the same language as our users, AI won’t find our answers anyway.

The landscape will keep changing, but if we focus on getting the basics right, we’ll be ready for whatever comes next.

Reflections from the Scottish Web Folk Conference 2026 – ‘Human vs machine: who does it better?’

2 November 2026 at 09:59

Scottish Webfolk has become a staple fixture in my October work calendar for the last three years. Despite the very early start to make it north for the conference starting just after nine, by the time you arrive you realise it was worth making the trip. This year there were over 100 attendees from 26 different universities, with a strong line up of presenters from Edinburgh.

Andrew Millar, Head of Digital Engagement & Marketing at University of Dundee started with his key note opening talk, which is always a highlight and this year was no different as he introduced the theme of the conference ‘Human vs machine: who does it better?’

Andrew’s talks are always grounded in realism, especially given the challenging times the higher education sector is facing, but with ample optimism and insightful narrative woven throughout so that by the end you feel energised for a day or learning, sharing ideas and discussing common challenges.

A different take on a familiar theme: AI

It’s probably not a great surprise that the conference had an AI theme. However, I felt this time it was as much about the importance and value of ‘keeping a human in the loop’ as it was about leveraging the benefits of AI-based technologies and tools.

In his talk Andrew referred to the quote: “the threat was never the machine, it’s how people use it” which really stuck with me.

AI is the latest in a whole historical timeline of technological advancements, as Andrew explained. Whilst it is revolutionary, it still needs humans to ensure that it’s used for the greatest benefit. So in that sense the day highlighted to me that machines and humans need to work in tandem, rather than in competition to get the best results.

My third presentation at the conference – ‘AI search summaries: a new lens on old content problems’

For this year’s conference I co-presented with Nick Daniels and Mel Batcharj for what was to be my last UX Service talk. We shared how we trained our web publishing community at Edinburgh on how to make their content AI-ready in the ever-evolving AI search landscape.

We highlighted how evergreen content design principles still stand strong in the new era of AI search and shared how we used the prominence of AI to teach these principles in a slightly reframed way. The aim being to enable publishers to optimise their content for AI search, whilst also tackling persistent problems with our web estate content.

The key takeaway was that website content that is well structured, well maintained and accessible is just as important for AI as it is for users.

You can read more about this training in my previous blog.

June Content Improvement Club: Is your content AI ready? 

Web governance: a problem shared is a problem halved

Another highlight of the day for me was the refreshing session which Stratos Filalithis from Edinburgh and Chris Purdy, Head of Digital Experience from the University of Glasgow hosted, which they called ‘Digital Unscripted’. There were no slides, instead an honest conversation about the challenges both universities are facing to tackle their huge, unwieldy web estates.

I’m used to starting off presentations at conferences explaining that Edinburgh has a huge web estate with over 1,000 web publishers (today was no different). This is often met by surprised faces, especially for those universities with a centralised digital marketing team who oversee the production of all web content. So, it was somewhat comforting to hear that Glasgow faced similar challenges to Edinburgh in terms of managing vast amounts of diverse web content and that both institutions were sharing knowledge and expertise to try to bring order to the chaos.

I found this interesting as a lot of my work recently has been focussed on developing guidance (alongside subject matter experts) for website owners on their key responsibilities when creating and managing a website.

The difficulties and governance risks associated with large web estates felt like a very relevant topic to be discussing given AI’s ability to unearth long forgotten about content in its answers, but also in the wake of the PHP vulnerability incident which highlighted the importance of ‘knowing what you own’ from a web registry perspective.

Scottish Web Folk – much more a community event than a traditional conference

I think the ‘Digital Unscripted’ session, along with the panel discussions where representatives from different universities shared their perspectives on challenges they were facing for me sums up that really Scottish Web Folk is more a community event than a traditional conference. There’s a real sense of sharing solutions to mutual problems and discussing the challenges that nobody has yet managed to resolve, rather than just highlighting successes. I think it’s the community emphasis and collegiality that keeps bringing people back year after year.

Finding My Place in the Wild Web Estate

By: mponder
30 October 2026 at 13:23

After a month in my role as Web Governance Administrator, I thought it appropriate to reflect and share a little about my experience so far (prior to the events of the PHP incident, that deserves it’s own post)!

A Weeklong Handover

After my interview and first day, I started getting an idea of what my job would entail – or at least, I had a good idea of the overall project of the team I was on: taming the “Wild Web Estate”. 

My manager, Stratos, let me know that this job had a steep learning curve and that there would be a lot of information handed over to me from Angelina, the student previously in my role. He warned that the four days I had left before Angelina’s last day might not be enough for her to impart all her knowledge and pass what she had been working on over to me. 

We finished the handover sheet they had put together and went through all my questions in about three hours. The rest of my time with her was spent going through and helping her finish her big tagging project – and, perfectly, we finished about 30 minutes before the end of her last day.  

“My experience as a Web Governance Admin Intern” – Blog post by Angelina Lai. 

Of course, this experience using the software and having her next to me while I went through the process myself was incredibly useful for when questions popped up that I wouldn’t have thought to ask. So, I am glad the handover form didn’t take as much time as we had planned. 

After finishing the handover and project with Angelina, my expectations of my role changed significantly. I was then under the impression that my job would be very similar to other student roles I have seen or held in the past: heavily supervised, with little flexibility or say in what I’m working on. I would be given a task, complete it, and hand it back to my manager – for lack of better terminology, “busy work” that’s necessary for the project to be completed. (Spoiler alert: I was wrong.) 

More Than Just a Student Role 

At this point, I thought that if I couldn’t get much professional development from my role, I would at least do my best to reach out to others in the larger group to make connections, get a better understanding of the overall strategy of the Information Services Group, and learn more about my colleagues’ and superiors’ backgrounds and how they got into the roles they’re in now. 

These kinds of 1:1 meetings were extremely common in my previous corporate roles, so in my next 1:1 with Stratos, I went in ready to hear what my next assignment was and brought up the question: Is this kind of connecting with coworkers common here, and what is the proper etiquette around it? 

With the contents of this meeting and his response to that question, my expectations changed yet again. 

He informed me that he wanted to start bringing me into the larger project, rather than just giving me assignments to work on and then submit, as I had previously assumed. He also let me know that he had already started scheduling introductions with a lot of people I would be working with, and that having him in those meetings would help give both me and my new colleagues context for where we each fit into one another’s roles and the overall project. 

This wasn’t something my previous supervisors had taken the time to do, and I was, and still am, incredibly grateful. 

Finding My Voice 

That 1:1 with Stratos started a series of discoveries for me over the following weeks about how much flexibility and freedom I had to bring my own ideas and thoughts into my role. 

I started attending meetings and conferences, like the “10-year digital estate plan” and speaking with more colleagues. As I gained a more all-encompassing understanding of not only what we were trying to do, but also the obstacles that stood in our way, I slowly, little by little, started pushing the self-inflicted boundaries of my role. 

The final turning point for me was yet another weekly 1:1 with Stratos that we had to extend by over an hour to cover all the thoughts, questions, and ideas I had around our project. 

That conversation was probably the most productive work meeting I’ve ever had, in the sense that it was an incredibly informative conversation where I was able to fully understand the challenges and boundaries of our project, challenge the assumptions we had, and ask questions to help us think about the project differently. 

It was really the first meeting in a corporate setting where I felt like my thoughts and opinions were taken seriously and valued. We talked about my self-inflicted restrictions and set clear expectations around the freedom I had to problem-solve, generate ideas, and give opinions and input on our project. 

Putting Ideas Into Action (Behind the Scenes of the Wild Web Estate) 

Since then, I have thoroughly enjoyed being an active participant in conversations around the strategy, planning, and implementation of the “Wild West Web Estate” project. 

“2,117 websites and counting: welcome to our Wild West Web Estate” – Blog post by Stratos Filalithis 

We worked to define the scope of my work, which entails taking all the work Angelina did in tagging websites in Little Forest (the software for documenting website information for maintaining the web estate), exporting the data, and formatting it in a functional way to give to the respective IT departments. They will then fill in missing information, correct inaccurate information, and make active decisions on whether to keep, fix, or retire these websites. I will then format their responses and update Little Forest with these actionable insights. 

Building Something That Lasts 

There is one thing I have noticed, however, that will be a bit of a challenge in my role. 

Building out the tools I’ve alluded to in this project and making them reusable to sustain the practice we are implementing is actually fairly straightforward. With the flexibility and ability to really contribute my own ideas to the implementation and customisation of these tools, I’m able to bring my own vision to life. 

However, my role isn’t permanent. As of now, I’m only planning to be in the UK for a year while I finish my studies. 

This adds an additional layer to the project: How can I make these tools and processes sustainable and usable by someone else who might not have my technical background – especially when it comes to the aspects of my job that involve data management, restructuring, and organisation through coding? 

It’s an interesting line to walk between making this process as efficient as possible with the tools I know how to use and making it usable for the next person in my position with minimal training on the process. 

This challenge, though, only adds to my excitement about both this specific project and this role as a whole. 

Leaving My Mark 

I can’t begin to describe (although it may have been evident above) how pleased I am with my role and the support I have, specifically from Stratos and my other colleagues, to be a genuine thought partner throughout this project. 

My biggest goal, beyond professional development, is to leave behind a legacy – my input written, either figuratively or literally, into these tools and processes that will hopefully be used for many years to come. 

At Scottish Web Folk 2026, the theme was Human vs Machine. The takeaway was Human plus Machine.

The theme of this year’s Scottish Web Folk conference in Dundee was “Human vs Machine”, and AI dominated the programme, as you’d expect. But session after session told another story: the successes came from humans and machines working together, with people firmly in charge of the judgement calls. Here’s my reflections from a day packed with very interesting sessions and networking with colleagues from the Higher Education sector.

Four years in, and still the friendliest room in Scottish higher education

The annual Scottish Web Folk conference began in 2023 to bring Scottish universities’ digital and web professionals back together after the hiatus of the pandemic. Colleagues from University from Dundee (can’t say thank you enough to Andrew Millar and Rob Ryder-Richardson enough for keeping this community together) organise a day of more than twenty sessions, with teams from across the UK and Ireland attending. When I reflected on the 2024 edition, I called it a ceilidh, and the description still fits.

The Scottish Web Folk ceilidh at Dundee – Blog post by Stratos Filalithis, October 2024

Alistair Campbell used the title of “Challenging times, brilliant people” for last year’s conference, and this description still stands, even stronger.

Scottish Web Folk 2025: Challenging times, brilliant people – Blog post by Alistair Campbell, November 2025

A large lecture theatre, with people sitting on the foreground and a large screen welcoming attendees of the Scottish Web Folk 2026 conference.

The opening of the Scottish Web Folk 2026 conference.

This is a working conference rather than a showcase: people turn up to talk about their challenges and successes and leave with valuable insights, ideas and new friends to follow up after the day. The University of Edinburgh was very well represented, with colleagues from our teams sharing their work.

Scottish Web Folk 2026 conference programme

In Edinburgh and Glasgow, we “never waste a crisis”

During the last few years, Kris Purdy, Head of Digital Experience at University of Glasgow, and I have met regularly to exchange thoughts and ideas, and compare your approaches against very similar challenges in our web estates. In this year’s conference, we were given the opportunity to stand and share our stories, findings and action plans to bring order to our chaotic web estates. We agreed to “freestyle” the session, having an open discussion without any slides. This allowed us to be frank in an informal environment, and, hopefully, better engage with our audience, allowing questions to be asked during our discussion and not waiting until the end, as is the usual format.

We spoke about our common challenges, like the risk of not knowing the size, shape and individual ownership of our websites, and differences, for example Glasgow’s web estate counts approximately 900 websites, half of which are hosted in their corporate website, while Edinburgh’s web estate counts more than 2,000 websites, with less than 8% using the centrally-supported web platform, EdWeb 2. Some of these numbers triggered audible gasps from the crowd, like the fact that Google regularly indexes more than 2 million pages and files under our corporate domain (ed.ac.uk), which is way more than those hosted in our web platform, or expected to manage.

There was a very special mention to last week’s PHP2Shell vulnerability incident which highlighted the need for an up-to-date web estate registry, as well as the immediate and quick action everyone took to update it with information about ownership, technology usage, which helps identify those websites that need to be retired immediately. This is a crisis we will not waste.

Through our journeys, though, we identified a very strong conclusion: the lack of clear web estate governance and ownership increases multiple risks across reputation, ability to stand out in search results, content accuracy, compliance, cyber security and higher costs associated with the web services. As I have blogged recently, these risks are untenable in the are of the great amplifier: Artificial Intelligence (AI).

2,117 websites and counting: welcome to our Wild West Web Estate – Blog post by Stratos Filalithis, October 2026

With a day full of insights and interesting sessions, here are the main themes that stood out for me:

The threat was never the machine

The customary introduction by Andrew Millar, Head of Digital Engagement & Marketing at University of Dundee, sets the tone for the rest of the day, and this time was not different. I fully agree with his argument that humanity had always had a challenge with transformative and disruptive technologies. AI is the most recent addition in a list having the printing press, factory power, office computers and the web, all of which provided a turning point making some things scarce and other more valuable.

Slide titled “Not the first turning point”, comparing the printing press, steam power, office computers, the web and AI. Each earlier shift made one skill cheap and another valuable, such as judgement and trust after the printing press. For AI, drafting and summarising are no longer scarce, but what becomes valuable and who loses out are marked with question marks. Caption: “It worked out previously…

Andrew Millar’s slide listing the human technology turning points and their impacts.

Each of these technologies had an impact relative to their era and world, making AI the most impactful (yet). What we do with it, though, is up to humans since technology by itself is not a threat. How we use it and for which purposes and benefits is. Andrew concluded by pointing out that to achieve this, we need to make sure to ask the right questions, like “Did the user get the right answer, anywhere in our website?” instead of “How many people viewed this page?”, or “Does key content have an owner and a review date?” instead of having “Machines make unlimited content”.

Most of the sessions in the day were focussing on just that, how to leverage the powerful technologies at hand to enhance our capability, experience and skills to fulfil our objectives.

AI bots are an audience too

This wasn’t the first time that I attended a session about building website and webpages for AI bots. This is a very real subject because optimizing how AI bots scan and index our content, supports what they respond on our behalf to a rising number of user using them as their first point in searching for a programme, degree or research opportunities.

Rob Ryder-Richardson shared how University of Dundee improved their programmes’ entry requirements presentation to ensure both humans and AI bots got the most out of it. The journey through each iteration of the page exposed that the human experience is not necessarily useful for an AI bot, which then impacts the accuracy of their responses. More specifically, personalised content via location was triggering wrong answers by AI bots, since they had indexed their responses based on their location, the United States of America, and not the visitor’s location, which could be any other country in the world.

The current solution is to publish a single, plain HTML page containing all information in structured tables. This page more than 60,000 lines, making it unusable by humans but perfect for AI crawlers, allows AI bots to provide accurate answers per location. His “five things to check on Monday” slide provided an easy guide for everyone to check on their websites (higher education or not):

  • check what bots are allowed to reach.
  • turn JavaScript off and look at your key pages.
  • check what a US visitor sees on any content personalised by location.
  • write ten questions applicants really ask.
  • put them to Google, Gemini, ChatGPT, Claude and others, then see what they say about you.

And yet, humans still hold the keys

However much AI might have dominated the sessions and discussions, the human element was hard to miss. From Andrew’s opening session, highlighting human-verified as a key element for a good website, and Ulster University’s Mark Kennedy highlighting the role a very small team of 4 plays to support a community of around 400 publishers, to the very informative panel discussion where Marta Krukowska, from Bangor University, highlighted how students are asking real-life questions to make their decision to apply for any University, and Neil Allison, from The University of Edinburgh, raising the issue of cost of living for those considering Edinburgh as their study destination, all had one thing in common: real people.

Later in the day, Neil’s session focussed on how to make the most of stakeholder workshops, He provided easy, practical guidance and real-life examples to maximize engagements and outcomes in a very useful, and directly applicable, guide to human input. His premise is that workshops take many forms, but a few fundamentals sit underneath every successful one: bringing people together, solving a problem and ending with something tangible that everyone can get behind.

A slide with the title "What should a workshop facilitate?" listing Sharing, Collaboration, Democratisation, Ideation and Prioritisation as the key goals of a workshop. A diagram showing a workshop journey from diverging to exploring ideas and then covering to those that matter at the end.

Neil’s slide listing a successful workshop’s facilitation phases and goals.

A slide with the title “What should a workshop facilitate?” listing Sharing, Collaboration, Democratisation, Ideation and Prioritisation as the key goals of a workshop. A diagram showing a workshop journey from diverging to exploring ideas and then covering to those that matter at the end.

Human plus Machine

The theme of the day was “Human Vs Machine”, but the best sessions were about both: bots that need clean structure and humans who need honest answers, AI that speeds up the build and people who still decide what is worth building. The old, but always relevant acronym GIGO: Garbage in, garbage out, that Andrew referenced in his opening talk, has never been more true, and people are still the ones deciding what goes in.

As for what’s next? I have already booked Wednesday 27th of October 2027 in my calendar to travel back to Dundee for the 5th Scottish Web Folk conference.

Thank you to everyone who spoke, sponsored and chatted over coffee and lunch. If any of this sparks a thought, a challenge or a question, I would love to hear from you. Please get in touch directly at stratos.filalithis@ed.ac.uk.

2,117 websites and counting: welcome to our Wild West Web Estate

How many websites does the University of Edinburgh have? A few years ago, the honest answer was “a lot, probably more than you think”. During recent years, we built a better idea about their number, shape and performance. This summer, we have counted them all, audited them by hand, and this is the first post in a series about what we found, what it means and what we are doing about it.

What do Edinburgh trees and our Web Estate have in common?

Last week, I had the pleasure of opening the HE Connect 26 conference here in Edinburgh and part of my introduction was, as any good host would do, about bragging about our city. As you might be aware, it is built on seven hills, two of them are extinct volcanoes, and it has more trees than residents (according to the official Council records).

Websites are not forever, and neither is fragmentation: reflections from HE Connect 26 – Blog post by Stratos Filalithis

Those weren’t random trivia about Edinburgh, at least not one out of three. I shared the information about the amount of trees by adding that approximately 75% of them are privately managed. This constitutes a hugely valued shared asset, looked after by many different people, with varying levels of care.

That is our web estate in a nutshell. A large collection of websites, hosting publicly available content, promoting the University, its study programmes, world changing research, available services and other relevant areas. This collection is following a devolved ownership model, much like every other area of the University itself, which results in a variety of quality, performance, technology usage and maintenance approaches.

What are we counting and who is accountable?

To set the scene, it’s very useful to share some definitions about what we consider a website and our web estate to be:

  • A website is a discrete collection of pages under a single web address, built and maintained as one entity, delivering content to external audiences without any requirement to login. It must have a defined owner.
  • Our web estate is all University-owned websites, web applications and publishing platforms, centrally managed and devolved. These host publicly available content for all our external audiences without any requirements to login.

Our devolved ownership to University Schools, Units and Departments is a local arrangement. For regulators, though, the University is a single legal entity. Accessibility and data protection regulations apply to all of it, and our responsibility to the Information Commissioner’s Office (ICO), which is the UK regulator, sits with the University. But, given our devolved governance model, each website owner is accountable to carry these responsibilities on behalf of the University.

How many websites we actually have and where do they live?

The latest count of websites in our web estate is 2,117. This is a growth of 30% since our last full web estate audit.

It includes all “live” websites who either use the University’s corporate domain (ed.ac.uk) or have a direct relationship or affiliation to the University.

Approximately 8% of this web estate is hosted in our University Web Platform, EdWeb 2. Even though this is a small number, it includes a lot of of our highest priority content: 20 out of 25 School websites, the Degree Finder, our corporate homepage and website, and the majority of our student and staff services.

The rest of the 92% websites are using various technologies, hosted across several platforms, managed by roles and teams having a variety of skills.

Through our close collaboration with the University’s Digital Preservation team, we have uncovered a lot more detail about the history, legacy, structure and lifecycles of our websites. David Mahoney, Digital Archive Assistant, has conducted thorough research on the history of our web estate, and published a blog post about his approach and findings.

Strata: Uncovering the Layers of the Archived Web – Blog post by David Mahoney

Key initial learnings from our manual audit

To establish the strongest possible baseline and benchmark, we took the hard decision to audit each one of the 2,117 websites manually. I would not usually recommend this approach, because it’s very time consuming, but it was essential to bring our experience and organizational knowledge to fulfil the gaps in ownership. An additional benefit of the manual audit was assessing the risk per website, based on use of technology, content freshness or other factors. It helped us, also, to identify the more common website use cases, approaches and risk triggers, and allowed us to better inform our initial key learnings.

Ownership means a named person

The majority of our web estate is directly related to our College’s activities, either teaching or research. For most websites, we can identify the College or Professional Group responsible, but we cannot name a person as the website owner. “The College is owning this website” is not a tenable position, since it does not carry any real accountability, responsibility or direct action with it.

Technology and content are our highest risk factors

The audit is looking at what our websites are made of. Most of our web estate runs using popular technologies, like Drupal or WordPress, but not necessarily on a supported version. One of our current targets is to identify these and take appropriate action. Our findings have confirmed that a portion of our web estate is not actively looked after, a percentage that grows as a website gets older, which increases our security risks.

It’s not only the technology that is left behind, though. Content, in its own right, is not reviewed, updated or removed, leaving a large number of out-of-date or inaccurate pages. This reduces the trust of our visitors against our websites, since they are not sure what to trust.

Websites must follow a clear lifecycle

As you might have guessed already from my presentation title, “Websites are not forever”, I am a true believer that everything has a beginning and an end. And websites are no exception. Some of them evolve, get a redesign, upgrade or a relaunch, which is an ending on its own, but most of them need to fulfil their lifecycle by retiring at the proper point. A large part of our websites was launched in relation to a time-limited activity: a research project, a University initiative, a conference, event or course-related requirement, but when that activity stopped, there was rarely any action to retire the website content, too.

Artificial Intelligence (AI): the great amplifier

All of the learnings and risks are amplified by the emergence of AI technologies:

  • Out of date and legacy content is scanned daily and “pollutes” the accuracy of the information AI agents reply on our behalf to their users. Someone asking information about a specific degree area in the UK might receive false information about Edinburgh, and disregard our offer based on it.
  • AI tools improve their capability in scanning digital platforms for vulnerabilities, while the frequency of cyber attacks gets higher as time goes by. One can only imagine the risks of this technology in the hands of cyber criminals.

Our best defence is accurate, current content on well-managed platforms, in a well governed, compact web estate.

Where are we going next

We are in the beginning of this journey, and we are gaining momentum. The next phase of the audit is under way, the outputs being shared with the College and Professional Group Heads of IT, covering ownership, content accuracy and age, and technology. We will trigger a decision point whether to retain, move to EdWeb 2, keep and support, or retire ensuring appropriate archiving.

In parallel, a formal web estate project with a steering group is kicking off, we are working closely to map our web estate requirements against the University’s 10-year digital plan, and our web estate governance hub is being updated to better support our website owner community, with a new Web Trainer role to turn guidance into training.

The progress of this journey will continue to be covered in future blog posts, sharing more of our learning, best practice and, hopefully, significant progress in taming our Wild West Web Estate.

 

Shared challenges, shared solutions: what I learned at the UCISA Web Services Community Day

13 October 2026 at 13:42

In July, I travelled to Leeds for the UCISA Web Services Community Day, hosted at Leeds Trinity University’s city campus. It was the community’s first in-person event, and the theme was Shared Challenges, Shared Solutions: practical, honest stories from people who develop, deliver and manage web services across higher education.

The room brought together colleagues from the Universities of Sunderland, Birmingham, Leeds, Aberdeen and Edinburgh, with Leeds Trinity as host. Vendors Terminalfour and Zengenti shared tools, trends and time savers for doing more with less. I also sat on the closing panel.

Here’s what stuck with me.

AI is changing how students find us

Piero Tintori, CEO of Terminalfour, opened with how the student journey has changed. Prospective students moved from search engines to social media, and now to AI. There is push back too: some younger people distrust AI summaries, so trust and authenticity matter more than ever. Students still want fast answers, mainly about costs and career paths.

His challenge to the room was simple. Open an incognito browser and search for something like “study engineering in Scotland”. The results vary wildly, and you can’t control them. AI engines draw on many sources and often don’t choose your website at all. Reddit is increasingly treated as a source of truth, which leaves the door open to inaccurate or deliberately poisoned answers. Your analytics won’t clearly show when AI is involved either.

Piero framed his advice as “adopt and drop”.

Adopt:

  • Make your degree finder excellent
  • Write content for AI as well as for people
  • Prune old content, especially PDFs, because AI has no sense of dates
  • Look ahead to structured data (JSON-LD) and llms.txt to point crawlers to a source of truth

Drop:

  • Old or archived content, urgently
  • Over-engineered personalisation projects
  • Chatbots
  • Blind trust in robots.txt
  • Anything you can’t measure

He also noted that some US universities now use general AI tools in place of content quality platforms such as Siteimprove, Silktide, Semrush and Monsido. He suggested a standard may emerge that lets publishers charge AI companies for access to their content.

For any university with a large, long-lived web estate, the message is clear: what you remove matters as much as what you publish.

Putting AI and data to work

Dean Hale, Enterprise Applications Manager at the University of Sunderland, followed with a candid account of building trustworthy AI to process student personal statements.

Richard Chivers and Richard Saunders from Zengenti, the company behind the Contensis CMS, then tackled a problem every university web team knows: maintaining content quality at scale.

Their answer was Agent Skills, an open standard for giving AI tools a clear, reusable set of instructions. A prompt typed fresh each time gives different results. A skill is more reliable for repeatable tasks because it defines four things up front:

  • Task: what the AI should do
  • Context: the background it needs
  • Constraints: the guard rails it must respect
  • Output: the format the result should take

Zengenti has published a set of these skills for higher education content teams:

  • Alt text: write or audit image descriptions
  • Meta descriptions: draft page summaries for search
  • GEO audit: check how well a page performs in AI search engines, scored across five dimensions with a checklist of fixes
  • Staleness audit: flag outdated fees, dates, staff details and statistics
  • Refine for the web: turn raw copy into structured course content

Batch agents run the audits across many pages at once. The bigger idea is a shared skills library that teams, and potentially institutions, can build on together rather than each writing their own prompts from scratch. The skills are free to use and work in tools such as Claude. You can find them on GitHub: Contensis HE Content Skills.

The staleness audit links straight back to Piero’s warning that AI has no sense of dates. If AI engines will happily serve last year’s fees, finding outdated content before they do becomes a priority.

Birmingham: product thinking and knowing your estate

The University of Birmingham gave two talks that fitted together well.

In a lightning talk, Amy Commander, Web Product Owner, explained how her team has rethought the way it delivers web services. Instead of treating the website as a series of one-off projects, Birmingham runs it as a product, built on three principles:

  • Ongoing ownership: someone is always responsible for it
  • Iterative delivery: no big bangs
  • Funded as a product: steady investment rather than project-by-project bids

The team works in two-week sprints with an ordered backlog, user research and a dedicated QA tester. Notably, it does this without a scrum master. Work moves through a simple cycle of plan, build, release and review, and the team releases little and often.

What I liked most was the commitment to continual improvement over big-bang launches. Large redesigns carry large risks, and they tend to go stale soon after launch. Small, regular releases let you learn and adjust as you go.

Later in the day, Billy Fallows, Web Operations Manager, and Rob Fowles, Head of Digital Channel Management, explained why Birmingham started its web strategy with an audit of the whole web estate.

It wasn’t quick. The audit was a manual process, run from a spreadsheet, and took a long time. They kept it manageable by assessing every site against a clear set of criteria:

  • Alignment with the university brand
  • Content quality, flagging sites scoring below 50 in Silktide
  • Accessibility
  • Whether a GDPR statement was in place
  • Clear site ownership
  • Content age
  • Technology compliance
  • Audience size from analytics
  • Website complexity
  • Duplicate content

That evidence now underpins a web strategy built on four objectives and four enablers. The objectives cover audience needs, user journeys, high-impact content and alignment with institutional standards. The enablers cover governance, technology, measurement and the operating model.

Their next steps are to fill in missing data, tighten the criteria, contact site owners about a register of sites, develop policies to support that register, and act on the recommendations.

The lesson I took away is that you can’t set a credible strategy without knowing what you have. An audit is slow, unglamorous work, but it turns a sprawling estate into something you can govern. Ownership, in particular, appears on almost every list like this for good reason. A site with no owner is a site nobody will improve.

Building a content design playbook

My Edinburgh colleague Lauren Tormey, Senior Content Designer, shared how her team builds a content design playbook through a repeatable workshop format. Drawing on content strategist Colleen Jones, she described a playbook as a script for content methods and processes: a collection of “plays” for tackling common content challenges. The idea isn’t limited to content either. The GDS Service Manual, the Atlassian Team Playbook and the GDS social media playbook all work the same way.

Each workshop focuses on one style topic, such as links, and runs in three stages:

  1. Align on best practice. Everyone writes dos and don’ts on sticky notes, adding a question mark to any they’re unsure about. The team then groups similar notes and debates the question marks.
  2. Writing practice. The facilitator prepares a real piece of content that needs improving, sometimes with errors added deliberately. Everyone edits it against the practice the group has just agreed.
  3. Review outputs. Each person reads someone else’s edit, then the team discusses what they did differently and how to align.

Lauren was candid that the review stage often gets squeezed, because the first activity takes the longest. That’s the right trade-off: agreeing what good looks like is the most important part. The format is simple, repeatable and easy for any team to borrow.

The panel: shared challenges, honest answers

The day closed with a panel chaired by Claire Gibbons of Leeds Trinity University. I joined Jenny Tompflitt, Scrum Master at the University of Leeds, and Mike McConnell, Applications Operations Manager at the University of Aberdeen. Three institutions with different structures, and yet our answers were strikingly similar. That says a lot about how widely these pressures are felt.

What is the biggest challenge facing your team?

For me, it’s scale. My team looks after four key web services: the MyEd student portal, our EdWeb 2 website platform, Staff Profiles and Search. MyEd is built on aging technology and needs rebuilding. The website platform keeps growing. Two of the four services need refreshing. All of them need more resource than they have.

More and more of the university relies on central services, so demand keeps rising. Teams also tend to work in silos, solving the same problems separately.

Then there’s AI. Expectations are high across the sector, and there is real pressure to show progress. The challenge isn’t enthusiasm. It’s finding time for teams to properly explore the tools and understand where they add value, before being asked to deliver with them.

How are you coping with doing more with less?

My answer was to sharpen the axe before swinging it. That meant three things.

Streamline honestly. We asked teams to put everything on the table, then rebuilt our priorities from the bottom up. Once that was clear, we invested time in building staff capability and shared the load across sections, so no team solves things alone.

Borrow selectively. We bring in external help for specific pieces of work, but strategic thinking stays in-house.

Make technology work for us. Building services on the same technology pays off. On Pantheon, one update reaches more than 600 websites. MyEd will continue to adopt a headless approach on the same foundations.

The approach is as much about people as technology. When Staff Profiles was delayed, we involved stakeholders in the decision instead of simply announcing it. It was slower, but it built trust.

Where are you most optimistic?

Not the technology. The people, and a shift in how we lead.

Universities may compete for students, but we don’t compete on how we run our web services. That gives us something the private sector often lacks: we can learn from each other, collaborate and share ideas openly. Days like this prove it. I’m also seeing teams move from “launch and forget” to continuous improvement, as Amy described at Birmingham. Tight budgets are hard, but they also push us to streamline and focus on what matters most.

If I had to put it in one line each:

  1. Four services, one team, and no time to properly explore the AI everyone is telling you to use.
  2. Smart technology choices, selective expertise, and people who own the change.
  3. The people coming through, and leadership moving from compliance to commitment.

What I’m taking away

Three things:

  1. Old content is now a live risk. AI engines don’t know what’s out of date, so they will serve last year’s fees as readily as this year’s. Pruning, staleness checks and estate audits are no longer housekeeping. They protect the student experience.
  2. Continuous improvement beats big launches. Birmingham’s product model and our own panel discussion pointed the same way. Own your services, release little and often, and fund them as products rather than projects.
  3. Collaboration is the sector’s advantage. Every institution in the room faced the same pressures: rising demand, flat budgets and expectations around AI. We don’t compete on this, so we can share what works and avoid repeating each other’s mistakes.

Should you attend next time?

Yes. For a first in-person event, the Web Services Community Day delivered exactly what its theme promised: honest stories, practical ideas and plenty of time to talk with peers facing the same challenges. Thanks to Claire Gibbons and the team at Leeds Trinity University for hosting, and to UCISA for organising.

If you work on web services in higher education, join the UCISA Web Services Community and come along to the next one.

Websites are not forever, and neither is fragmentation: reflections from HE Connect 26

The annual HE Connect came to Edinburgh this week, and I had the privilege of opening it before spending two days listening to peers wrestle with the same problems we have. Here’s what stuck with me, from large University web estates to AI recommending (or rejecting) your university before you’ve even said hello.

Coming home to HE Connect

At the end of HE Connect 25 in Manchester, it was announced that the 2026 edition would be held in Edinburgh. I wrote then that I couldn’t wait to welcome colleagues from the UK and beyond.

Reflections from a conference focussing on digital leadership in higher education: HE Connect 25 – Blog post by Stratos Filalithis

On Tuesday 6th of October, digital leaders from across higher education and agencies specialising in the sector met at the Royal Society of Edinburgh, and I welcomed everyone with presenting on “Websites are not forever: what to keep, what to fix, what to retire.”

In it, I followed the lifecycle of a website, from the excitement of launch to the less glamorous questions of maintenance and retirement, and argued that most of our estates are in trouble because we’re much better at the first stage than the last. I also made the case that AI and security have turned forgotten content from an untidy habit into a real, current risk. Furthermore, I had the opportunity to do a 5′ lightning talk going through our work in digital sustainability and testing Artificial Intelligence’s (AI) capabilities in supporting accessibility testing.

A large room hosting approximately 40 attendees sitting in rows of chairs. A man is standing presenting in front of a large screen having a photo of a landscape with sea and forests.

On Wednesday 7/10, I presented a 5′ lightning talk covering our work in Digital Sustainability and testing AI’s capabilities against accessibility testing.

I’ll share more in a separate post, because this one is about what I was most looking forward to: sitting back, listening and learning from digital leadership peers sharing their challenges, experiences and approaches, and discussing with them in an honest, collaborative and constructive way.

HE Connect 26 programme and speakers

If there was one common thread, it was this: nobody designs fragmentation. It happens to us as “a result of disconnected and, sometimes, very sensible decisions”. The interesting question is what we do about it.

Coherence, not centralisation

That line came from Samantha Fanning, Director of Digital Experience at University College London (UCL), and it might be my favourite of the conference. UCL is a similar size to the University of Edinburgh, having around 50,000 students and 17-18,000 staff, so it was hard not to see our own estate in her slides.

Her advice was simple: don’t focus in superficial approaches to fix “the front door”, like a homepage. The issue is not the door, it’s the house itself. Part of UCL’s approach is a 3-space model, which covers all levels from trusted, owned and governed centrally, institutional knowledge and services, owned and governed centrally; to local knowledge and innovation. The principle to take away is to create shared foundations before seeking control, make ownership visible, and aim for coherence, not centralisation. UCL backs this with their own design system and experience framework. A well researched and supported design system is fundamental to implementing effective digital governance, and establishing one is one of our own objectives here in Edinburgh, too.

Johannes Nygaard, Chief Digital Advisor at the University of Copenhagen, showed what web estate transformation looks like. In 2023 they had one site serving everything from recruitment to science communication: 130,000 pages, 900 editors and 1,200 subsites. Two stepping stones, a new CMS and a new governance structure, signed off by the university’s senior management, included simple core principles: Every site targets specific external audiences, and who the most important are, resources should be prioritized based on importance of interaction and traffic, usage of templates for sites and pages. Perhaps the most controversial one in a University setting is that pages and sites with very little traffic would be closed, but it’s also the difference between a managed web estate and a digital museum.

Both of these sessions struck a chord with our work in Edinburgh, especially since the contain some of the possible answers to our own fragmented web estate challenges, and I have been encouraged to see what takes place in UCL and Copenhagen.

When AI is the front door

Piero Tintori, CEO of Terminalfour, brought numbers justifying the rise of AI usage in selecting a University programme: About 7% of prospective students go to an AI chatbot first for a specific institution request, with 18% of then having removed one from consideration based on an AI-generated result only. Still, 73% of parents name the college website as their top source, and 43% of applicants still start on a university website compared to 13% who start with AI. Most people still visit and trust our websites more than AI, but the latter covers the ground faster, and we will need to keep checking these numbers to keep track of if, and how fast, the prospective students and parents decisions change.

A very interesting sharing was that old content pollutes AI answers. Archived and outdated pages get used as sources, results vary from session to session, and the parts most likely to be wrong are the ones that matter most, like entry requirements, fees or key programme information. Piero’s answer was a move to content engineering: modelling, metadata, schemas and separating content from design, with AI helping to reduce the effort involved by ensuring the published content is accurate across all the web estate. My action will be to expedite action to archive and retire heritage content.

It’s clear that, especially in the age of AI, effective web governance and coordination is the key to address the evolving challenges and risks that carries a devolved web publishing environment.

Why is digital so hard?

Kris Purdy, Head of Digital Experience at the University of Glasgow, asked exactly that. His answer was even though digital sits in the middle of business, user and technology: “we built the digital, but we didn’t build the organisation to support it.”. Glasgow’s challenges are very similar to our own: many websites without a named owner, and uncertain plan for decision making, consolidation and retirement. Our own estate is larger, but the problem is exactly the same one, and I am very happy working closely with Kris to share how best to address these.

I really liked the mention of the “missing link” between strategy, which sits at board level, and delivery, which sits at team level. The defined step between approval and development, which translates strategy into “how”, is often the most critical part to unlock effective change, yet is missing either due to lack of funding, availability or prioritisation within our organizations.

This workshop triggered my interest a lot since I wanted to hear what the delegates had to say, especially those representing agencies as there could be insights directly related to our own web estate journey.

Governance is about people (again)

One unsurprising common theme across all sessions and informal discussions was that people is the catalyst and enabler to any change. This is not a technology challenge and has never been. Its fast evolution, though, like AI currently, amplifies the risks of not having a coherent and effective governance structure, alongside the appropriate technology.

This was a key takeaway from June Shannon’s and Paul Leigh’s sessions, both from the University of Limerick, too. In a very similar note, Helen Robertson and David Jones from GAIN Higher Education in their session, “What does your frontline know before your numbers do?”, also made a very good point: the person closest to the problem is the one closest to the solution. Finally, I thoroughly enjoyed Lucía Tornero González’s, who travelled from Madrid, about how Universidad Pontificia Comillas is approaching the graduate experience, creating everlasting moments for them and their families.

A big thank you to Janus Boye, who organised and facilitated the conference, and to every speaker for being so open about what works and what doesn’t. If any of this sparks a thought, a challenge or a question, I’d love to hear from you. Use the comments below, or get in touch directly at stratos.filalithis@ed.ac.uk.

My experience as a Web Governance Admin Intern

28 September 2026 at 15:38

Two years ago, I started this role with no understanding of what web governance meant. Today, I’m finishing my internship with a much stronger understanding of not only web governance, but also how a large university operates behind the scenes — from departmental structures and ownership to web accessibility, archiving, information security and digital responsibility.

I started with a huge amount of imposter syndrome, because I had no technical background, and this was my first experience in a professional workplace, so I was constantly questioning whether I was qualified to be there.

Looking back, I think that uncertainty was actually an important part of the experience, because it gave me the motivation to keep learning, ask questions, and grow into being confident in my role.

My day-to-day work

A major part of my role has been maintaining the University’s web registry – a central record of all the websites associated with the University and their ownership details. This involves regularly adding newly requested websites and ensuring that important information, such as the website owner and the according department, is accurately recorded.

This summer, as I transitioned into working full-time, I took on a new project to audit the web registry and verify whether the information held about each website was still accurate and up to date. This is particularly important because students, staff, and researchers can create websites using the University’s name, sometimes without being aware of the relevant legal, accessibility, and content requirements. Website owners can also leave the University without notifying our team, potentially leaving websites stray in the wider web and “orphaned”, so not only would our records of ownership be inaccurate, but also creates risks around the University brand, such as the possibility of university websites being hijacked.

To address these risks, I worked with large datasets and multiple local sources of information to identify discrepancies, investigate ownership, and keep the central registry accurate.

Some of my work during summer has included:

  • Progressing through the audit phase by manually reviewing all 2100+ website records, identifying and tagging the relevant departments, and verifying website owner status, e.g. Whether the owner has retired/left the university.
  • Gathering local website registries from different departments and cross-checking them against the central registry and updating records accordingly.
  • Supporting the wider process of identifying “Orphaned” websites that’s publicly available, created by students/researchers with the university brand, but may no longer have active owners or require further action.

It has been a great introduction to the importance of data accuracy and governance, particularly when data supports wider organizational risk management.

Communication, collaboration and working across teams

One of the biggest surprises of this role has been how much web governance is about people and communication, rather than just staring at an excel sheet.

A key part of my role involves coordinating and leading weekly governance meetings with teams across the University, including IT leads, Web Archiving, Digital Accessibility, and external suppliers. With the external registry supplier, I regularly liaise closely to identify and request new features and improvements to the registry. I’ve taken ownership of facilitating discussions, recording minutes, tracking actions, and following up actions.

Beyond this, I regularly communicate with individuals and teams across the University to respond to queries and provide information based on data held in the web registry.

For example, I’ve worked with:

  • The Web Accessibility Team & Web Sustainability Interns – supporting the integration of legal accessibility requirements & newly developed sustainability metrics into the central registry, and into the wider web governance framework.
  • The Web Archiving Team – helping identify websites and records that are ready to be retired or archived, while ensuring the relevant registry information is maintained.
  • UX Designers – collaborating on the creation of a Web Governance SharePoint site to raise awareness of website creation responsibilities amongst people who want to create their own websites, to address the root cause of inaccuracy in the web registry.

Opportunities to learn beyond my role

One of the things I’ve appreciated most about this role has been opportunities to see parts of the organization that I wouldn’t normally encounter in one specific role.

I had the opportunity to be involved in a university procurement process for the web registry supplier. I contributed to research reports on potential supplier candidate companies, and took minutes during committee meetings, helping track actions throughout the different stages of the process.

Another particularly meaningful experience was being able to sit on a panel for recruiting summer interns, and for my own role. Having been an applicant myself, it was fascinating to experience the process from the other side. I helped screen CVs and cover letters against a set criterion, contributed to decisions about who progressed to interview, then sat in interview panels and helped make final selections.

It gave me an insider perspective on recruitment – particularly on what interviewers look for, how candidates can distinguish themselves, and the interviewer’s thought process in identifying someone who will work well with them, which will be highly useful throughout my own future career.

Studying while working

However, balancing university alongside an internship has its downsides. Working while studying meant that I often had to divide my attention between two very different environments. There were also periods where the role could feel quite solitary, particularly because my work isn’t always team-based, and there were days where I could go much of the working day without speaking to anyone directly.

It was challenging at times, but it also pushed me to manage my own workload and become comfortable taking ownership of tasks without constant supervision.

Looking back

When I think back to starting this journey two years ago, it’s quite surreal to see how much has changed. I started without any real understanding of what web governance was, and with a lot of imposter syndrome about whether I belonged in a professional environment.

Yet I’m leaving with experience in web governance, data management & auditing, stakeholder management, recruitment, and supplier management – but most importantly, a lot more confidence in my ability to pivot into a completely new area.

I’m incredibly grateful for the mentorship, opportunities, and trust I’ve been given throughout this experience. I’ve built connections that I wouldn’t otherwise have had the opportunity to make, and discovered a career area that I genuinely would never have imagined myself working in when I started university. And I got to do all of that while studying at the same time!

Thank you so much to everyone who has supported, taught, and helped me grow throughout this journey.

Web Registry Development Intern’s September Recap!

By: gmcwalt2
11 September 2026 at 13:34

I’m Grace, the Web Registry Development Intern for the 2026 Summer! As my internship draws to a close, I discuss how my AI Supported Accessibility Testing, and my Web Estate Dashboard projects have progressed. The first project focused on investigating how AI can be used to automate accessibility testing websites. My second project aimed to produce a dashboard for non-technical audience so they could see their website statistics. I reflect on my project, my experience, and what I’ve learned.

AI Supported Accessibility Testing

Almost three months after I started, my internship is wrapping up. My Summer project aimed to investigate how AI can be used to automate accessibility testing, so we can make sure the web estate is in compliance with Web Content Accessibility Guidelines. Currently, most automated testing (programs like axe DevTools) catches approximately 30% of errors, I aimed to increase that accuracy and investigate where AI can be useful. I’ve learned a lot, but there’s still lots more for me to pick up! The goal was to get AI to test for WCAG violations more accurately, and see if it could be a useful tool in the testing process.

Findings

Rather mundanely, AI won’t be taking over the world anytime soon. AI supported accessibility testing still hovers around 30% accuracy.

Strengths

The agent is good at crawling through sites and identifying suspicious elements that commonly produce issues, things like a pop-up widget or a pdf. It also excels at anything related to markup languages, testing guideline 1.3.5, identify input purpose, for example, which looks to see if input fields are labelled correctly, so computers can autocomplete them. These black-and-white guidelines are easily digestible for AI, it’s when a human aspect in included that AI can stumble.

Weaknesses

In conversations with the accessibility team, it was noted that AI struggles with the “grey-areas” that pop up in the testing process. While the full list of WCAG guidelines is lengthy and specific, the primary goal is to make sites usable for all. A guideline may not explicitly outline why a website fails, but if a human finds it inaccessible, that means it’s inaccessible! An element’s context within a website can drastically change whether or not it’s WCAG compliant, this was something that agents struggled with. I found that agents are too scared to get something wrong to think critically or apply executive judgement.

Aside from that, guidelines that measure things like a logical tab sequence—measuring how intuitive it is for someone to navigate a website with a keyboard—should continue to be tested and reviewed by humans.

Methodology

In the beginning, I did some desk research to find the AI agent best suited for the task at hand. I investigated the different LLMs available through ELM, with varying success. They could analyse whatever screenshots I gave them, but that still required me going through a website and selecting information that was relevant. I pivoted to the ChatGPT software, which was then called Codex. Codex could exit its window and crawl through the site itself autonomously, more closely mimicking how accessibility testing is actually carried out. It was a bit of a learning curve, lots of failed audits that I got to learn from. Throughout the summer, I iterated a master prompt to feed to agents, tinkering away at it bit-by-bit. I made it modular, so it was easy to swap out guidelines based on what you wanted to test. Currently, the prompt sits at 7252 words, and each guideline is split into smaller sections.

A screenshot of a word document, split into green, yellow, cyan. and purple highlighted sections. An arrow labels the green section as "Quoted Guideline". An arrow labels the yellow section as "AI Specifications". An arrow labels the cyan section as "What not to do and common fails". An arrow labels the purple section as "Impact on users to include in final report".

The AI specifications section contributed the most to the wordcount. You have to be very specific about the exact path you want the agent to take. It’s good that you get to have specific control over the testing, less great when you have to soft-parent an agent through pressing the “Tab” key.

This prompt would then produce an audit report, this is distinct from a completed accessibility report. The audit was produced to help a tester identify issues, not to present findings to a wider audience. During my internship, I gave weekly updates to the accessibility team and I was consistently given really valuable feedback that I could integrate back into the master prompt. At the end of my internship, I started scoring the accuracy of the prompt against preexisting human accessibility reports.

Web Registry Dashboard

The aim of this project was to pull data from a registry service using its API capabilities and present it in a user-friendly dashboard. I wanted to make sure the entire process was cheap, secure, and easy to upkeep, qualities that can be tricky to balance all at once.

I split the project up into 2 phases. Phase 1 covered transferring the data from the registry to a PowerBI dashboard, which was a bit of trail and error, but was successful. Phase 2 covered adding specific filtered to the dashboard depending on the user, and these filters would be added autonomously, without requiring users to manually log in every time. Phase 2 was a lot trickier, and s still incomplete.

Methodology

Phase 1

This really tested, and expanded upon, my technical skills. Through my astrophysics degree, I do a lot of data analysis and presentation through Python. However, the data in a university setting is reliable, easy to obtain, and consistent, this isn’t the case with this project! It was really interesting working with data that has real-world implications and it changed the way I think about my data analysis. I used Python code to make my API calls—the thing that gives me the data from the registry—which confused me at first, but everyone on my team was happy to answer all my questions. I was able to pull the data from the registry and produce a PowerBI dashboard that presents all this data simply.

Phase 2This really broadened my experience with different types of data, especially sensitive data and the security that must come with it. Phase 2 results are still inconclusive, but good progress has been made.

A diagram of a flowchart with the steps: User logs into microsoft; DAX function userprinciplename(); PowerBI Looks at sharepoint list (or equivalent), finding corresponding details; Filters and Row Level permissions are applied; Dashboard!

Applying the filters to the dashboard is relatively straightforward. Phase 2’s main difficulty is accessing employees’ names and departments, data which is quite sensitive and requires high admin permissions to access. Naturally, any workflows would have to ensure employee data is handled securely. In order to produce a successful dashboard, the current web registry data would need to be completely reorganised. To create a robust dashboard, the data—including employee data, stored separately—would also need to be accurate.

What I learned

I’m still a long way from understanding the ins-and-outs of accessibility testing, but this project certainly built up my confidence in the subject. It encouraged me to think about the logic of these guidelines in creative ways, to make it better digestible for AI. After all, how would I train an AI to test a guideline if I myself didn’t understand it? While the project didn’t produce earth-shattering findings, the findings are still inconclusive. We should continue to explore tools to make websites more accessible, especially as AI continues to evolve.

The dashboard helped my technical skills grow, and taught me to come at an issue from many different angles as certain avenues were rejected. The dashboard project taught me that there sometimes isn’t a “right” way to do things and that sometimes you have to juggle conflicting considerations in a project.

Overall, I’m really grateful I got to evolve in this way and I’m excited to see what future projects can accomplish!

“I’m still not a coder”: A humanities student’s journey into Web Governance

By: Fan Fei
10 August 2026 at 14:25

A student in Philosophy and English Literature is probably not what most people picture when they hear “web governance administrator”. Angelina initially did not picture herself in this role either.  

Two summers ago, after finding an ISG vacancy through Unitemps, she joined the University’s web governance team only expecting a summer job. Recently, she graduated as part of the class of 2026. In this interview, Angelina reflects on how the experience has changed how she sees the IT sector, the value of her humanities degree, and her own career options.  

 

Q: What is the story of how you joined ISG, and specifically your current role? 

I was looking for a part-time job over the summer when I came across the advert on Unitemps. The role sounded interesting because it covered quite a wide range of things. I would be helping to keep track of the University’s web estate, but there would also be opportunities to work on side projects depending on what the team needed. 

My dad worked in IT, so I guess I had always found the sector intriguing. I just never thought I would have the right skills for it because when people see an IT job, the usual immediate associations are with coding, math and very STEM-based skillsets. None of which I had as a student in Philosophy and Literature. The thing that really caught my attention and prompted me to apply in the end was that the advert specifically stated that they were “NOT JUST looking for Computer Science students.” Indeed, working here for the past two years showed me that there is much more to digital service work than purely technical skills. 

 

Q: What does your role as a web governance administrator actually involve?  

My main project has been auditing the University’s web estate. The University owns a huge number of websites. Different schools, departments, services and groups might create their own sites, but those websites still need to follow University standards around things like accessibility, editorial content and data protection. Additionally, sometimes a website has been sitting there for ten years, and the person who originally owned it has retired or moved on. If nobody is actively responsible for it, that can become a security and governance risk. 

A lot of my job is thus making sure our records are accurate. We bring together lists from different departments, work out where each website belongs, ensure it fits guidelines and requirements, and track down its owner. If there is no current owner, we contact the department and ask them to appoint someone. In short, our work is looking after the quite important behind-the-scenes structure that a lot of ISG works sit on top of. 

 

Q: Was the work what you expected when you started?  

Only partly. From what I had heard from previous interns in my position, I thought I would mainly be looking after an existing list of websites. 

My manager, Stratos, wanted us to take a more thorough look at the whole web estate. Thus, we were not just checking that a website appeared on a list. We were asking whether it was under the right department, whether the named owner was still there, and whether there were other University websites that had never been recorded in this comprehensive collection. 

The role expanded quite a lot from what I had imagined. It was more challenging, but that also made it more interesting. I’m always looking for ways to develop new skills, so I enjoyed having work that made me think problem-solve, rather than doing the same administrative task repeatedly. 

 

Q: Is any part of the job more complicated than people would assume? 

Definitely. Almost every process is more complicated than it looks from the outside. 

One might assume the University already has one perfect, complete list of all its websites. In reality, the web estate is enormous. To build an accurate picture, you have to speak to departments, website owners, suppliers, and different University services. A task that sounds simple can involve a very long chain of communication. 

Last year, for example, we worked on a SharePoint site explaining what people need to know before creating a university website. I initially thought we would simply put the information onto SharePoint and finish it in about a week. That was not the case at all. First, we needed to work out which departments had relevant expertise. Then we had to gather their information, review it with managers, and also make sure the SharePoint site itself was accessible. There are so many stages of checking, reviewing, and going back and forth. 

It made me appreciate how much work happens behind the scenes. As a student, it can be easy to look at a university system and think, “Why isn’t this more organised?” But once I started working from the staff side, I realised how many people and processes are involved in making anything happen. 

 

Q: Has your background in humanities prepared you for this job in ways people wouldn’t usually expect? 

Yes, especially Philosophy. A lot of what I do academically involves taking an argument apart, identifying gaps in information and thinking about possible criticism. That transferred surprisingly well into the auditing process. My degree taught me critical thinking. I became very good at asking “what if” questions. What if the website owner has retired? What if somebody else has taken over, but the record was never updated? What if a site exists but has not been included in any of our lists? Humanities subjects taught me to consider different possibilities of scenarios, which enabled me to predict potential hurdles and thus prepare solutions in advance or respond accordingly. 

It may sound cliché, but my degree taught me a lot about efficient and effective communication. In Philosophy and Literature tutorials, we constantly discussed ideas, explained our perspectives, and responded to each other’s ideas. It transferred directly to when I lead meetings with suppliers. I can explain why we need something, keep the discussion focused, and emphasize the information points that matter most.  

 

Q: What surprised you the most about working in digital services? 

How nice everyone is. I thought it would be a very intense environment where everyone knew exactly what they were doing and had strict expectations for you to match their pace. Instead, everyone has been really easy to talk to. 

 The working environment is one of the things I have loved most about the role. My manager Stratos also made it much easier to settle in. When I started, I was slightly overwhelmed by everything I had to learn. He is patient and very good at explaining not only what I needed to do, but why we were doing it. That made the work feel collaborative. It did not feel like I was just being handed tasks. I understood what we were working towards as a team. 

 

Q: Which part of your internship experience stood out to you the most? 

Aside from my work tasks, I joined the panel that recruited this year’s summer interns. I was involved in reading CVs, shortlisting candidates, conducting interviews, and making final decisions. As someone who had only recently been on the other side of the table, it was really interesting to see what employers actually notice. 

Obviously, your experience and practical skills matter. You need evidence that you can do the job. But being able to communicate and collaborate also makes a big difference. When interviewing you, employers are also imagining what it would be like to work with you. You want them to be able to picture you as part of the team.  

 

Q: Congratulations on graduating. Looking forward, do you think the internship impacted your future career plans? 

Before this role, I always thought I would probably follow a more typical route that people picture for Literature students, like journalism or teaching. However, my first ideal choice currently would be to continue working in web estate. I would also be interested in other governance or risk-management roles, now that I have experience working in maintenance of a large set of information and containing risks around websites and data. The internship has helped me see past the stereotypes of disciplines and fields, and showed me career paths into a sector that I didn’t even realise were possible. 

 

Q: What advice would you give to students and new student interns? 

For university students in general, try to expand your scope and get experience outside the classroom as much as possible. One of the experiences that unexpectedly helped me get this role was being Competition Secretary for the University Volleyball team. I was managing the administration of a national-level team, scheduling competitions, booking halls, and arranging transport. It had nothing to do with websites or coding, but it showed that I could organise things, communicate with different parties, and manage a large estate. You never really know which experience will lead you to something else, so keep exploring things while keeping your academic work on track.  

To myself two years ago, and also to all future interns, I would say do not be afraid to ask for more opportunities. I asked whether I could join the recruitment interviews. I asked whether I could be involved in procurement work with external suppliers. Even when you do not have a speaking role, ask for the chance to be in the room, even just to listen in. Sometimes you would have to put yourself forward, because not all opportunities are automatically included in your job description.  

Starting as a Web Registry Development Intern

By: gmcwalt2
25 June 2026 at 15:38

Hiya! I’m Grace, and I’m studying astrophysics and I’m going into my 3rd year. I’m the web registry development intern and I started over the Summer of 2026. This Summer I’ll be working with LittleForrest, utilising the data it pulls about the University’s web estate, and using its APIs to present data to staff members at the University. I’ll also be training AI to test how accessible websites in the web estate are. Both these projects allow me to engage in topics that I’m really passionate about; digital accessibility and succinct data presentation. But more importantly, they both make me pick up lots of new skills!

First Impressions

My first day I didn’t really know what to expect, I knew I’d be working with data, but this would be the first time I’d be working with an institution as large and respected as The University of Edinburgh. I was armed with an EliteBook and a sparkly new lanyard, and was briefed on my projects.

Almost three weeks in and I’ve got into a good rhythm, though it was quite a learning curve. Fortunately, I’ve evolved from nodding sagely in meetings as I try to google what all the acronyms mean to now contributing confidently! Aside from the technical skills I will be picking up, I’m really keen to improve my public speaking skills, which is something my friendly line manager—Stratos—has really encouraged and given me opportunities to do!

Officially, my title is “Web Registry Development Intern” which, while correct, can be a bit vague when I introduce myself and doesn’t fully explain what I do day to day.

What I actually do

During the coming months my time will be split between two projects.

Web Registry Development

The University has a massive web estate, which I’m sure every student is vaguely aware of. I didn’t realise just how much fell under the University’s purview, and the diversity of websites. Lots of people are—rightfully—utilising what the University has to offer, but pulling their own website statistics from a massive array of data from an application like LittleForrest can be unintuitive. LittleForrest is a web governance tool i.e., it parses through all the websites the University is responsible for and deciphers who owns it, when it was created, and other properties.

My task is to create something that can wrangle the unruly web estate and present it cleanly, effectively, and succinctly to technical and non-technical audiences (emphasis on the non-technical). This will be presented in a dashboard that allows a login so users can see what is relevant to them, while also allowing filtering, so staff at the University can easily measure the performance of their websites. I am keen to give back to the University community while doing some concise data presentation and make the dashboard as seamless as possible.

AI Supported Accessibility Reporting

My second project doesn’t necessarily fall under the title of a “Web Registry Intern”, and is a project Stratos introduced after I waxed poetic about digital accessibility during my interview. The University has an AI platform called ELM, and I’ll be working closely with it to prompt it to test websites to see if they adhere to WCAG guidelines and aid in the reporting process. If all goes to plan, AI will be able to reliably evaluate how accessible a website is, and report its findings.

A screencap of an ELM AI response. ELM output: Based on the provided screenshots and DOM snippet, the pause mechanism successfully meets accessibility standards. Visual Intuitiveness: The close-up screenshot shows a universally recognized double-vertical-line pause icon. It is visually clear and easily identifiable as a media control. Screen Reader Semantics: The DOM reveals a natively semantic <button> element, which automatically provides the correct role and keyboard focusability. Furthermore, it contains aria-label="Pause video", ensuring screen reader users receive a clear, descriptive name for the control. AI VERDICT: PASS

WCAG, Web Content Accessibility Guidelines, is a set of criteria that websites have to meet in order to meet accessibility requirements, and often a website is assessed (mostly manually) and the findings are compiled into a report. This can later be compiled into an accessibility statement.

Working with AI is a lot of iterating prompts, as each new response paves the way for a new error. Figuring out how to reword a thought process that is very instinctive for humans into something digestible for AI forces me to think creatively, and I’m really enjoying the freedom I’m given. I had a surface-level grasp of digital accessibility, as I had previously tried to implement WCAG guidelines in my own personal website, but talking with people who really know what they’re talking about made me realise how frequently websites aren’t accessible.

When I was receiving training there where many examples where obvious accessibility violations were completely overlooked by reputable websites, so I’m really glad I get to work on something really important and that clearly deserves more awareness.

My Takeaways

Everyone I’ve interacted with has given me ample opportunity to be curious. I’m being introduced to many new ways of thinking so being able to badger someone with questions without judgement has been really encouraging. I’ve got two really engaging projects that are going to keep my busy this summer and I’m excited to see what I can do by August. The University hires lots of interns each year, and it’s definitely an intern-friendly environment.

It’s clear this internship is not just about what you can do for the University, but what the University can do for you.

 

 

 

 

 

 

❌
❌