❌

Normal view

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

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.

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.

❌
❌