❌

Reading view

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

Scottish Web Folk 2026: a canny, reflective and honest conference

I’ve had the privilege of attending the Scottish Web Folk conference for the last three years and this year’s event was as informative and candid as always, tackling the topic of ‘Human vs Machine’.

At other conferences and in other industry presentations, excitement about what the machines, specifically AI, can do, often whips up a don’t-get-left-behind fervour. But at this event, I think it would be fair to say that the machines were being viewed with a canny, human eye. We are deep into our new AI era and have an increasingly solid understanding of its possibilities and parameters for safe use in web.

We’ve been here before

In his keynote speech, Andrew Millar from the University of Dundee kicked off the ‘Human vs Machine’ discussion by looking back at points in our industrial history where technological leaps had forced change in the labour market, and then made valuable the associated, human, skills that would correctly manage the new technology. The printing press, for example, made redundant scribes and copyists, created a need for typesetters, and had the knock-on effect of requiring judgement and authority to manage the wider dissemination of the printed word. When computers arrived in offices, the filing clerks that were able to shift from paper to software found their analytical and decision-making skills could usefully harness digital categorisation and reporting. Not long after inception, the internet brought new levels of digital publishing reach, and the associated friction between volume and credibility, but the human vs machine tension has taken a new turn with the introduction of AI-generated web content and AI search.

What I took from the keynote speech was not just that we’ve lived through technological change and adapted, but that we’ve been incrementally building the human muscle required to manage the current technological era where AI is ever more dominant. Judgement, authority, analysis, decision-making and credibility are going to be central to managing AI into maturity.

Highlights of the day

My thoughts were focused on advocacy and responsibility as the conference unfolded. What do we already know about wielding our new technologies well (or facing the fall-out afterwards)? A few sessions in particular stood out.

Just because we can doesn’t mean we should

Stratos Filalithis from UoE and Kris Purdy of the University of Glasgow gave an ‘unscripted’ presentation that shared their frustrations of uncovering enormous legacy web estates. Both Universities, beyond their central platforms, had experienced a two-decade boom in affiliated web publishing without fully centralised or localised content management.

Stratos and Kris shared their strategies to build an accurate picture of their Wild West estates, and then spoke of the challenges ahead of defining ownership and instilling governance to create a supported and managed herd. Not just ‘unscripted’, but ‘unfinished’, the honest, unpolished session offered no pat answers but was a resounding cheer for the humans that tackle backlogs and runaway technologies every day. Collaboration, sharing and never accepting defeat are still singularly human approaches.

We already know how to write for AI

Under-managed, Wild West web content poses a risk to reputation because it potentially serves redundant, out-of-date or incorrect information. Well-managed content, however, seems to be largely AI ready, so it’s heartening to hear that existing skillsets are still valuable here.

Paul Costello and Rob Allen from Numiko showed in their work for the University of Oxford that the findability strategies that have served SEO are still central to GEO (generative engine optimisation; optimising for AI chatbots like ChatGPT or Claude) and AEO (answer engine optimisation; optimising for AI search).

Nick Daniels, Katie Spearman and Mel Batcharj from the UoE UX team presented core approaches to writing for AI, and these are already embedded in existing content design practice. Clear, concise content, meaningful headings and links, and accessible text all create AI-friendly content. If you missed the talk at Dundee, and the session at the UoE, their blog is well worth bookmarking for actionable takeaways.

June Content Improvement Club: Is your content AI ready? – Website and Communications Blog

We have to design technologies for operators as well as end users

As technology and its associated processes mature, we have to design for its operators as well as its end users. This is high on the agenda for me as service manager for the University’s web platform, supporting our internal user community to deliver content for their external users.

Lauren Tormey’s session set out to apply design practice to the processes of an internal team creating user-centred content for UoE Degree Finder. In incremental stages, she workshopped a playbook with an already expert Prospective Student Web Team to

  • stress-test existing content guidance
  • uncover new contexts where ‘If X then Y’ had not yet been defined
  • empower the team through live editing workshops so that everyone was equally experienced in applying the styles as defined in all contexts

With major revisions overdue on our self-service resource, the EdWeb 2 Hub, I have direct takeaways from this session to recreate our existing content stylesheet and editing practices. The platform has evolved significantly in the 18 months since the Hub was initially published, but the team updating the Hub while also supporting the user community day-to-day is tiny. Workshopping our existing styles and processes to update the content might feel like a diversion under our current time pressures, but it’s also an opportunity to stress-test our content practices and invest in the team. It’s important that we are equally and consistently skilled at managing updates, whether working at volume during intense platform evolution or in a more settled pattern of rolling revisions.

Final thoughts

In his keynote speech, Andrew Millar quoted an episode of Doctor Who where an AI bot was nudging the world towards Armageddon. The Doctor observes that it’s not the machine that’s the problem, but the pressures and choices around it.

As professionals working in the higher education web space, it’s our responsibility to employ that canny, human eye to embrace the technologies that benefit us when used correctly. Are we using them because we should or because we can? Are we thinking of the legacy that our actions now will leave? What knowledge have we already accumulated that can inform our use of new technologies?

And how do we ensure that everyone using our technologies, whether operators or end users, is supported and protected from pressures to do more faster so that collectively we all contribute to the successful maturation of a new technology? I came away from the conference with the sense that as long as we keep sharing our experiences of past, current and new technologies, and are honest about our challenges and approaches to managing them, our choices can be positive.

Scottish Web Folk 2026: UX team reflections

With others from the Website and Communications team, Nick and Mel headed up to Dundee to attend the Scottish Web Folk conference. In this post, they share their reflections on the day.

Nick’s reflections 

This was my fourth trip to Dundee for the Scottish Web Folk conference and my third time presenting. Scottish Web Folk is a great chance to hear from people working in digital roles in higher education, and catch up with how people across the sector are approaching similar challenges. 

We presented about optimising content for AI summaries 

This year, Mel Batcharj, Katie Spearman and I presented about AI summaries, such as the ‘AI Overview’ that Google now presents at the top of a search results page. These summaries take information from our websites and repackage it for users, who in some cases no longer click through to the websites themselves. 

In our presentation, we talked about how to create content that is optimised for these summaries, and how we created a Content Improvement Club session to address this topic. 

We emphasised that much of the guidance for creating content optimised for search engines hasn’t completely changed in the age of AI. It’s still important to write clear, structured content that addresses user needs and presents people with the information they need to take their next step. It’s also still the case that following good  digital accessibility practices will help AI tools and search engines to process the information included in your content. 

Read Katie’s write-up of our  Content Improvement Club training session ‘Is your content AI ready?’ 

Speakers discussed the theme of ‘Human versus machine’ 

There were various talks looking at how we can use AI to support and inform our work with websites in higher education. 

In the panel discussion, Marta Krukowska (Web and Digital Manager at Bangor University) described her experiments with using AI tools to interview colleagues to gather information for course pages. If asked to describe their course, colleagues sometimes provided vague information. For example, they might talk about how the university provides access to “state-of-the-art facilities”. But the AI interviewer could push back and ask for the names of specific facilities, and what their availability means for students. This turned out to be a more efficient way to get the information needed to write marketing copy for a course. 

The panel also addressed questions of how prospective students are using AI tools to support their search for a university course. The discussion made me reflect on how difficult it can be to identify a starting point for a complex user journey like this. It’s easy to fall into the trap of thinking that a user journey is a linear process or a series of steps, but this frequently isn’t the case. When people are thinking about what they want to study and where they want to study it, there are typically a wide range of information sources feeding into that decision. The information is coming in from these disparate sources over a broad period of time. So it’s probably not accurate to say that the journey starts with an AI search, even if that forms part of the information environment that a prospective student is using. 

The Prospective Student Web team presented about their content playbook and how they’re appraising degree finder 

Two presentations I particularly enjoyed during the day were from our Edinburgh colleagues Lauren Tormey and Pete Watson. 

Lauren was presenting about how her team had put together a content playbook: a set of patterns that staff can follow when working with content. The playbook helps content designers to take a consistent approach when using page elements such as feature boxes, pull quotes and page summaries. It was interesting to hear Lauren’s account of how they found alignment within their team to produce the guidance in the playbook. I’d sat in one of the alignment sessions myself and liked how everyone had had a chance to put forward their views by editing the same page of content. In her talk, Lauren described how meeting up to discuss a piece of content helped to clarify shared standards and supported a more consistent approach to editorial work. 

Pete’s talk was about how he has been appraising the performance of Edinburgh’s degree finder. Pete used a scorecard similar to the one Lou Rosenfeld describes in his article ‘Stop redesigning and start tuning your site instead’. The scorecard lays out your most important audiences, and for each one, a prioritised list of their tasks and information needs. The final column on the scorecard is a grade for how easy it is to complete those tasks or find that information on your website. 

The challenge then was to find a robust way to give these grades. To do this, Pete created a set of marking criteria of the type you might see associated with educational assessments. With this in hand, he ran a series of usability tests to see how easily people could complete tasks on Degree Finder. The result was a table showing how effectively we’re supporting prospective students to complete their key tasks, and highlighting where further development effort is needed. 

Read Pete’s blog post about appraising the new postgraduate study website 

Thanks to the Dundee team for hosting the event 

As always, the day was brilliantly organised, with a wide range of interesting talks. We’re still learning about how AI is changing our use of digital tools, and this event was a good chance to reflect on how this is having an impact on those of us who work on websites in the higher education sector. 

Mel’s reflections 

This was my second time attending Scottish Web Folk in Dundee, but my first time presenting. I’d been looking forward to returning, as it’s always a welcoming room and a great opportunity to hear what others across the sector are working on. 

We took our AI research into a wider conversation 

Our session, ‘AI search summaries: a new lens on old content problems’, built on a Content Improvement Club training session we’d run recently. Preparing that training was the first time I’d really explored how AI relates to the content we produce, and it involved a lot of research. So it felt like a nice full-circle moment to bring some of that learning to Scottish Web Folk and share it as part of a wider discussion about AI. 

Our presentation focused on AI and content design, while some of the other sessions took a more technical angle. It was interesting (and reassuring!) to hear that our points resonated with others, particularly the idea that well-structured, maintained and accessible content matters for AI as well as for people. 

It was also a lovely surprise to find Claire Gregory from the University of Dundee in the room. Her UCISA talk, ‘Feeding the bot: making content work beyond the webpage’, had been a really useful source when preparing our training. 

Watch Claire Gregory’s talk: ‘Feeding the bot’ 

We also had questions about the training itself and how we get people involved. Our sessions have developed quite a bit over the past year, so it was nice to have a moment to reflect on that and chat about the process with a room of peers. 

Andrew Millar’s opening talk put AI in a wider context 

Beginning the day, Andrew Millar’s got us thinking about how we approach new technology. He took us through a timeline of major technological turning points, from the printing press to the web, and asked what became less scarce, what became more valuable and who lost out. With the printing press, for example, copying text became easier, but judgement and trust became more important. 

We’d actually considered using a timeline in our own presentation, so it was interesting to see a similar approach being used elsewhere. It felt like a useful way to tackle the AI elephant in the room, putting the changes we’re seeing into a wider context rather than treating AI as something entirely without precedent. 

A new acronym has really stuck with me from Andrew’s talk: GIGO, or ‘garbage in, garbage out’. It’s a simple idea, but an important one in the context of AI. If the information we’re putting out there isn’t good in the first place, we can’t expect the systems using it to produce reliable answers. Definitely relevant to what we were talking about! 

Andrew also talked about how, more than ever, we need to advocate for users who aren’t in the room. That really resonated with me. I don’t think the rise of AI search tools means we should start rewriting everything for bots. Rather, it’s another ‘audience’ to consider, while keeping our human audiences at the centre. The things we already think about as content designers (understanding user needs, using plain language and making content accessible) still matter.  

The morning panel discussed making university information work harder for prospective students 

The panel discussion was another highlight for me. I enjoyed the conversational format, which offered something a little different from listening to a series of presentations. 

A key part of the chat was around how prospective students’ questions go well beyond course details. They’re also thinking about the cost of living, student welfare and the practicalities of studying, including whether they’ll be able to work alongside their course. These priorities are changing, and universities need to be upfront about the answers rather than burying the lead. 

This is particularly important as AI search tools may draw on information from outside university websites, such as forums and online discussions. If universities don’t provide clear answers themselves, AI may turn to other sources that aren’t always accurate or complete. There’s an opportunity here for universities to answer people’s questions directly and reliably. 

I also enjoyed hearing about Marta Krukowska’s (Bangor University) example of using AI to introduce a bit of friction when gathering course information from colleagues. Rather than accepting vague descriptions, AI could push people to dig deeper and provide more specific answers. I liked this idea of using AI not simply to speed things up, but to challenge people to provide the useful detail that prospective students actually need. It was another example of finding a suitable use for AI that wasn’t about creating content. 

A day of shared learning 

Overall, it was a really good day and well worth the early start. The ‘Human vs machine’ theme could easily have made the day all about the latest AI tools and technologies. What I took away instead was how much of the conversation came back to the human side. 

Big thanks again to the Dundee team for hosting.

Scottish Web Folk 2026: Humans vs Machine

There is no doubt that there has been a step change in how Higher Education has delivered web services over the past few years. However, stepping foot in the University of Dundee’s conference hall for another Scottish Web Folk, I’m delighted to report that it’s still very possible to fill a room with brilliant people who are happy to nerd out about our work!

You can read about my previous experience here:

Scottish Web Folk 2025: Challenging times, brilliant people

Old rules no longer apply

As is tradition, the University of Dundee’s Andrew Millar, opened the conference with a presentation which presented the theme of the day: “Human vs Machine”.

He put forward the idea that the amazing technologies which are transforming digital services also come with significant risks and challenges.

For example, indicators which were once used to assess the effectiveness of a web service can no longer be relied upon: Page views are less relevant now that many users will find an answer from a chat bot without visiting a website. A site’s ranking in search engines is less relevant now that a chat bot can find answers from anywhere on the web. And so on.

There is tension between the perception of human- and AI-generated content

While there is undoubtedly an increase in the use of chat bots to find information, a recent Gallup survey of 14-29 year olds found that only 3% trust work solely made by AI, 28% trust AI-assisted work, and 69% trust work made without AI.

Andrew Millar presenting a slide which includes the statistics of the trustworthiness of AI among Generation Z

In a panel discussion, Marta Krukowska from the University of Bangor described a situation in which an image purchased from a major vendor and used on their website turned out to be AI-generated. This caused some reputational damage in the student community as it put the doubt in users’ minds that other content might also be AI-generated.

The perception of these technologies is clearly in flux and are likely to shift significantly over the coming years. While it may be beyond us to influence this process, Millar put forward what he sees as our role:

  • Advocate: Speak for the user who is not in the room through research, accessibility, and plain language.
  • Defend: Protect accuracy and our voice. Ensure that what AI says about us is correct. Guard our data and intellectual property.
  • Decide: Own what is published in our name through approval thresholds, escalation, and a working stop button.

Digital practitioners have moved from theory to practice

Ensuring that our web content is correct and parsable by AI tools is essential going forward.

Only thinking about human users can have unintended results

Rob Ryder-Richardson from the University of Dundee described a situation in which something that was designed to help human users had unintended consequences when interfaced with AI.

Their course information pages dynamically displayed different data depending on the geographical location of the visitor – good for humans, but AI crawlers are almost exclusively based in the United States.

Therefore, when asked about course entry requirements, some chatbots were confidently asserting that the University of Dundee only accepts US SATs and that UK-based qualifications were ineligible.

The solution was to essentially develop a dataset which AI crawlers could use to find information, invisible to human users who would likely find such information unnecessary and overwhelming – structured in a way which is clear and unambiguous.

AI can be used proactively to improve the quality of web services

Richard Saunders from Zengenti described the benefits of developing a collaborative toolkit which team members can use to assess their webpages proactively to improve quality.

As a manager of a service which contains a surprising amount of content, one of the biggest challenges I have is ensuring that this content is accurate, pertinent, and accessible. While this task is currently done manually, there is certainly benefit in automating this task with AI skills.

In contrast with using one-off prompts, AI skills are plaintext workflows which provide a consistent instruction to the LLM. These work best when each one is focused on one particular outcome, and so developing a library of these within a team can provide a toolkit which can be used to consistently audit a website’s content.

I look forward to applying new best practice

While the technical implications for AI often dominate the conversation, Scottish Web Folk reminded me that successful digital transformation is fundamentally a human endeavour. Two sessions from the University of Edinburgh highlighted to me that before we can deploy such technologies, we must first master collaboration.

Neil Allison presented a masterclass on delivering effective workshops. Too often, digital teams conflate “meetings” and “workshops” and gather stakeholders only to disseminate information rather than create it. He outlined common pitfalls that cause a workshop to be ineffective: such as a lack of clear objectives, prominent voices stifling creativity, and lack of tangible outputs.

A slide featuring a diagram of a good workshop: the opening phase is divergent, the exploring phase is emergent, and the closing phase is convergent

Lauren Tormey delivered a case study on developing content design playbooks. Tormey explained how to co-create a set of best practices using a repeatable, structured workshop format.

As part of a team who hopes to deliver significant changes to our digital services in the near future, I found this talk to be invaluable and look forward to employing these strategies in my workshops soon.

We have a responsibility to help deliver better, future-proofed web services

AI is no longer a distant, theoretical concept, but an immediate operational reality. The path forward requires focusing on both delivering effective technology and ensuring excellent collaboration on the human level.

To take this forward, I propose the following action plan:

  • Ensure our success metrics are defined according to user requirements.
  • Audit our content for AI readability.
  • Deliver excellent workshops to determine our course of action.

Or in other words:

Advocate. Defend. Decide.

Key Takeaways from Scottish Web Folk 2026

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?’

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.

Lola the Cafe Boat – Review

Over the past few months we have been traveling on our canal boat, and 3 times we have seen Lola the Cafe Boat moored up, unfortunately one once was the boat trading, else I would be even larger than I am now. Today we went to the RCTA Tipton Floating Market, which is a small affair along side the canal just after The Fountain Inn on the Old Main Line Canal in Birmingham. At the end of the…

Source

What I learned in my summer internship researching digital content accessibility

In this post, User Experience team intern Hannah Watson shares her work over the summer researching digital content accessibility with the EdWeb 2 publishing community.

Introduction

As part of my internship with the User Experience Service, I have been investigating digital accessibility at the content level across University web pages, particularly on EdWeb 2 sites. Digital accessibility at the content level is about applying principles of accessibility to how web content is written and formatted. This includes, but is not limited to, content features such as heading levels, links, and alt text. It does not include anything that is not involved with content design or that is controlled at a higher level by the Content Management System (CMS), such as font, font size, or colour contrast.

Research aims and scope

The specific research questions for this project were:

  • How do web publishers learn about digital content accessibility?
  • What do web publishers know about digital content accessibility?
  • How do web publishers implement digital accessibility requirements and principles in their content?
  • What challenges do web publishers face in creating digitally accessible content?

More comprehensively, I was investigating the accessibility of:

  • Heading levels
    • Ensuring that heading levels are used correctly
    • Not using heading levels for emphasis
  • Links
    • Clear and concise link text which describes the linked destination
    • Link text which makes sense on its own
    • Avoiding URLs on web pages
  • Lists
  • Alt text
    • Clear link text that describes the image
  • Images
    • Ensuring that all images have appropriate alt text
    • Avoiding images of text
  • Videos
    • Including human-corrected captions with any videos uploaded to web pages
    • Making sure that transcripts are available for all videos uploaded to web pages
  • Italic, bold, and underlined text

For more detailed guidance on these topics, please refer to the University of Edinburgh editorial style guide.

Editorial style guide | Information Services

This research has been necessary for the User Experience team as it allows us to identify which areas of content accessibility are challenging for web publishers. From this, the team can adapt guidance and training to provide extra support on these more challenging areas where possible.

Research methods

Interviews with web publishers

I started my research by setting up short, informal interviews with six University web publishers. In these interviews, I asked the publishers about their experiences of creating digitally accessible content. The aim of these conversations was to understand how publishers learned about digital accessibility and what challenges they face when making content as accessible as it can be. During the interviews, we referred to web pages that these publishers work on to get concrete examples that illustrate the topics we discussed. Through these interviews, I was able to identify a number of trends, particularly in the challenges that the interviewees and their colleagues face.

Survey of EdWeb 2 publishers and the Web Accessibility Special Interest Group

Following these interviews, I created a survey to further investigate the findings and collate more supporting evidence for these findings. The survey consisted of 10 questions, three of which were demographic based as a filter, with a final question asking permission to follow up with those who responded.

The other six questions asked about:

  • which actions the participants took to make their content digitally accessible
  • what resources they used to do so
  • what challenges they face in doing so

The findings from the survey were effective in making the information gathered in interviews more robust and provided further evidence for some trends that were identified previously.

To publicise this survey, I sent a brief statement explaining my research into two Teams channels, the Web Accessibility Special Interest Group and the EdWeb 2 Community. Overall, the survey received five responses, and while this is a limited number, I found that it helped to support the findings from the interviews.

Analysis of Effective Digital Content workbooks

The final method of research that I used to learn about the digital accessibility of content on University web pages was by looking at pages that were submitted within Effective Digital Content workbooks as part of the course. The course requires learners to choose pages from a University website and assess the effectiveness of the content. By looking at the pages that learners selected, I was able to use active examples and make note of content accessibility issues that were present on live pages. This process also highlighted a number of trends.

This method of research was also useful in that it provided two separate sources of data. Firstly, the answers in the workbook helped me to gauge learners’ understanding of the principles covered in the course. Secondly, the web pages linked by those taking the course allowed me to have live examples of content to assess against content accessibility principles. While there was not necessarily overlap between the answers in the workbook and the pages submitted as part of the workbook (as some people may not have been fully or at all responsible for the content on those pages, or the content could have been updated since the workbook was submitted), it was useful to see these things separately.

Findings about accessibility

Combining findings from all areas of research for this project, I have identified a number of trends in the accessibility of digital content.

Headings, alt text, and links are the principles most often put into practice by participants

In the interviews and the survey, participants were asked what principles of accessible digital content they actively used when designing content. More than half of participants mentioned three principles in particular, with all participants mentioning at least two, which were:

  • using the correct heading levels
  • adding meaningful alt text to an image
  • writing clear and descriptive link text

Interestingly, while these principles were mentioned frequently by participants, and evidenced by the websites that we discussed in interviews, they are also principles that are often missed on University web pages. This is discussed in more detail in the corresponding sections further on in this post.

PDFs are hard to avoid

One standout finding from the interviews was that web publishers sometimes struggle to find an effective alternative to PDFs. While PDFs are not necessarily accessible, they do have benefits which make them useful for publishers. For example, they are downloadable, searchable, and cannot be easily edited without permission from the owner. There are ways to make PDFs more accessible, such as avoiding decorative images, adhering to accessible content design principles within the PDF, and checking colour contrast. However, the interviewees were more in favour of finding a way to turn their content into a webpage as this is more likely to result in accessible content.

Out of the survey responses, three also mentioned that they had recently chosen to publish content as a web page rather than as a PDF, highlighting their knowledge that a web page is preferable in terms of accessibility. However, their personal preferences or how difficult they found this is unknown as I was unable to follow up with these participants.

Heading levels are often skipped and headings vague

Across web pages that I assessed for correct heading levels, there were several which skipped heading levels throughout the page content, such as going straight to a heading 3 without that heading being nested within a heading 2 section. Additionally, headings on the University web pages that I investigated were often generic, instead of being specific about what a page or section will contain, which is the recommended approach.

The fact that the web publishers who were interviewed and surveyed were aware of the importance of correct headings levels and specific headings, and that the majority of these publishers have attended a staff training or used the editorial style guide, suggests that the guidance provided is accurate and useful for publishers.

To increase the use of correct heading levels, as well as clear and descriptive headings on web pages, participant responses suggest that increasing the reach and engagement of existing training and resources involving headings would be effective. This includes training provided by the User Experience Service, such as Effective Digital Content or Content Improvement Club, and the University of Edinburgh editorial style guide.

Alt text is well written but sometimes missed

In three of the interviews, and in two survey responses, participants mentioned that they struggled to find the time to add alt text to images on their web pages. However, participants in the interviews also stated that they understood the importance of alt text, and what writing meaningful and clear alt text involves. This is reflected in the answers in Effective Digital Content workbooks. The course contains a question asking learners to write meaningful alt text for two images, and this question is often answered well. This suggests that web publishers understand how to write alt text, and that the obstacle in doing so is more likely to be related to time and resource.

One way that time constraints on adding alt text could be improved is to reduce the number of images on a web page, which will not only make this task more manageable but also is also more sustainable.

Explaining acronyms and abbreviations is common

All five responses to the survey stated that they had explained an acronym or abbreviation recently. Although this did not come up in the interviews often – only once – the survey responses suggest that this is common practice for web publishers who are familiar with digital accessibility principles.

Link text is frequently inline or not descriptive

Participants stated that they understand the importance of clear link text as a principle and make effort to implement this into their content. However, similar to headings, this sentiment is not reflected across numerous University web pages. In some of the pages submitted as part of the Effective Digital Content workbooks that I investigated, there were frequent occurrences of inline link text, or link text that does not clearly describe the linked destination.

To increase the writing of link text on a separate line, as well as clear and descriptive link text, participant responses suggest that increasing the reach and engagement of existing training and resources involving links would be effective. This includes training provided by the User Experience Service, such as Effective Digital Content or Content Improvement Club, and the University of Edinburgh editorial style guide.

Findings about staff experience and engagement

A trend from both the interviews and survey responses is that for many of the people involved with this research, their knowledge of digital accessibility started with a personal interest. Specific examples of this that participants mentioned include learning about accessibility as a student (and then going on to be an accessibility advocate for a student society) and working with disabled students and learning through experience.

During the interviews, multiple staff members mentioned that they believe, through their experiences, that a large part of issues with creating accessible digital content at the University surrounds communication. A combination of factors was discussed that had communication at the centre, including:

  • the importance of digital accessibility not being widespread enough.
  • consistency about expectations between schools or areas of the University, such as one page being edited by multiple schools or areas and having different standards.

Job-based constraints were also mentioned frequently, such as limited time to add alt text to all images on a web page and working on a page where the lead publisher takes a design forward approach which can sometimes clash with accessible content principles. These answers were also reflected in the survey responses, with all of the responses mentioning either one or both of these problems.

What resources do web publishers use for learning about and developing their digital accessibility skills?

The primary resource that participants mentioned using to learn about digital accessibility and develop their skills was University-provided staff training, with 10 of 11 participants mentioning this. Effective Digital Content was specifically mentioned twice, and Content Improvement Club three times. In the interviews, two participants mentioned more general staff training, with one survey response saying the same. In the survey responses, three participants also said that they used training provided by the Disability Information Team.

The Web Content Accessibility Guidelines 2.2 (WCAG) is another resource that was frequently mentioned by participants, with six in total saying that this is a resource that they use as guidance on accessibility.

The University of Edinburgh editorial style guide was mentioned by five participants as a resource that they used to provide guidance on digital accessibility, in which the guidance reflects what publishers learn in training courses, meaning that information they take from the style guide is in line with accessibility and content design training.

What I learned from researching content accessibility approaches in EdWeb

I learned a lot during my time researching how web publishers at the University of Edinburgh approach creating accessible digital content. I thoroughly enjoyed the opportunity to work with staff from a variety of different areas of the University. This helped me to learn how to identify commonalities in interview and survey responses despite the areas of work being distinct. I also enjoyed this because I was able to learn much more about the work that goes on across the University and what the work of other teams involved.

I also particularly enjoyed the format of my internship being a combination of individual work and working with other members of my team and the Disability Information team. This balance allowed me to set my own goals while still getting the opportunity to work and learn collaboratively as part of a team, prioritising my tasks between my own and those that I was working on with others.

A limitation of my work was that it was much easier to contact and work with staff who have a genuine interest in the subject area of accessibility, which does not lead to research that is representative of how University staff approach digital accessibility as a whole. Having done the research that I have so far, a continuation of the research would be most beneficial if it focused on the experiences and approaches of staff who are less familiar with digital accessibility requirements and principles, as this would create a more well-rounded understanding of web publisher accessibility approaches at the content level.

Furthermore, another limitation of the work was the time constraints which have restricted my ability to develop solutions to issues identified during the research period. This was expected to a degree, as the solutions depended on the outcomes of the research, which has taken the majority of the 12-week period. The positive outcome of this is that the research and findings will provide the User Experience service with information that allows for both further research and for adaptations to guidance and training if it is deemed necessary.

Conclusion

This research has helped the User Experience Service to assess their training and the resources that are available for publishers to learn more about digital content accessibility. Keeping in touch with the publishing community through projects like this helps the team to direct their effort to real challenges that publishers face on a day to day basis.

The research completed throughout the duration of this project will be supported and advanced by further investigation, particularly by communicating with web publishers who are less involved with digital accessibility as a whole. This will likely help in providing more concrete solutions to digital content accessibility issues across EdWeb 2 pages.

Hearing about approaches to student voice at the Learning and Teaching Conference 2026

In June, I headed over to the Nucleus Building to attend the University’s Learning and Teaching Conference. The theme of the conference was student voice, and I was there to present about how the Careers Service and the UX Service had involved students in the design process for a recent website development project.

Emily McIntosh’s keynote “Nothing about us without us”

The day kicked off with a keynote from Emily McIntosh, Chief Student Officer at Harper Adams University. Emily set up the theme of student voice and covered some important distinctions for us to keep in mind throughout the day. Emily compared two ways that students are involved in decision-making processes: representation and partnership.

Representation is where staff within a university create something – a new policy, for example – then show student reps and ask for their opinion. While this is better than not involving students at all, it can lead to student reps feeling that they are responding to decisions that have already been made. The input from student reps sometimes comes at late stage, and can lead to tweaks but not necessarily substantive change.

Emily suggested that “you said, we did” posters can be indicative of this sort of approach. She contrasted this with examples of universities working in partnership with students from the beginning. In this way, students are actively involved in helping to shape services and policy. Emily described this as a relational, dialogic culture of ongoing collaboration, where students and staff work on problems together. This approach is sometimes described as co-design.

For me, there were some clear analogies in what Emily was describing to processes we advocate for in user-centred design. For example, bringing user input into the early stages of a design process is generally more effective than getting the same input later in the day. In addition to this, user-centred design often emphasises the benefit of ongoing collaboration and continuous iterative improvement, keeping users involved before and after the launch of a product.

Working in partnership like this is not necessarily a simple thing to achieve. But I appreciated the message: incorporating students into how we decide to do things as a university brings some significant advantages. Whatever the practical challenges of implementing this approach, moving from designing-for to designing-with offers us opportunities to better meet service users’ needs.

Highlights from the rest of the day

The rest of the day made me think about issues around student voice.

Neil Speirs (Widening Participation Manager) raised the issue of working class students often being absent from student voice projects. Neil’s talk made me think about how good quality user research often depends on recruiting a diverse group of participants. Recruiting the right research participants can be difficult. We see that all the time in our work. But without a diverse range of voices, user research can miss important perspectives and draw an incomplete picture of what matters to users of a product or service.

Neil Speirs speaking in a lecture theatre in front of a slide titled A neutral proposition

Neil Speirs presenting at the Learning and Teaching Conference. Slide reads: “A neutral proposition? We must be aware that student voice does not stand as a neutral proposition. Without democratic and participatory structures and cultures, student voice projects in learning and teaching will not provide democratic and participatory outcomes. We might reflect on the class based inequalities that are ‘baked into’ (Major et al, 2023) our structures, cultures, policy, curriculum and pedagogy. Which students are readily able to participate and benefit from student voice projects? Which students are invited to take part? Do we even notice? Is it the usual suspects? Do all students know the rules of the game and therefore why and how it might be advantageous to partake in student voice projects? Is the working class student voice heard in these spaces?”

Clare McKay (Student Recruitment and Admissions) and Christine Emmerson (Communications and Marketing) talked about how student recruitment markets can help us to anticipate student needs. One important point they made was that marketing is not just about promoting courses and programmes. It’s also about understanding our audience and whether there is a need. This resonated with aspects of UX work, where an understanding of user needs can tell us not just how to communicate information, but also whether that information is needed in the first place.

Jenna Fyfe and Carine Abraham (Edinburgh Medical School) talked about research they had done with alumni networks. Their project focused on alumni from three online postgraduate programmes at the Medical School. Alumni described how they create networks with each other following graduation, and how they often retain an interest in maintaining contact with programme teams from the University. This contrasts with a picture where alumni wish to maintain contact with university-wide structures. I found this interesting, because we sometimes think of people outside the University seeing us as a single entity unified by an overarching brand. In contrast, the alumni in this research weren’t thinking about a monolithic institution. Instead, they retained an interest in personal connections with a small, specific part of the University.

My talk was about our work with the Careers Service

In my talk, I gave an overview of how the Careers Service developed their website in 2025. In particular, I highlighted how the User Experience Service assisted with the design of collaborative activities that brought student voice into the work. I wanted to show how bringing student input into this sort of design activity makes the work better, and I talked about the benefits that the Careers Service achieved by approaching the project in this way.

You can read more about our collaboration with the Careers Service elsewhere on this blog:

Blog posts about work by the UX Service and the Careers Service

Reflections on the day

I thought there was a lot of value in holding a conference like this, with most of the speakers being staff and students from the University of Edinburgh. Presenters were speaking from a broadly similar context, which meant the talks had a high level of relevance to our work. There were a lot of familiar faces and it was good to catch up in the breaks with colleagues I hadn’t seen for a while.

My main takeaway was that student voice projects often have a lot of crossover with user-centred design approaches. In both cases, we’re interested in making things better by involving end users. I felt it was a great opportunity to hear about how student voice projects have been informing colleagues’ work at the University.

About the conference

University of Edinburgh Learning & Teaching Conference

Degrowth Gathering – Building the UK movement

Saturday, 17 October,  9:30-5.00 Degrowth is both a transformative movement and a critical framework, aiming to ensure social justice and well-being for all, with human activities being in alignment with ecological limits. However, degrowth in the UK currently exists as an informal network rather than a cohesive movement. This one-day event will bring together those… Continue reading Degrowth Gathering – Building the UK movement

June Content Improvement Club: Is your content AI ready?

Our June Content Improvement Club session focused on AI. In particular we discussed the changes in search behaviour, how that’s impacting the way people consume content and some of the things you can do to make your content ready for this new search landscape. Attendees also got the chance to work in groups to put some of our top tips into practice.

This topic clearly resonated with with our community, as it was fully booked shortly after being advertised, so we ran a second session to enable more people to attend.

Changes in search behaviour in the wake of AI overviews

We started off the session by providing a bit of context around what has led to the change in the way people now search for information.

AI overviews help answer your question on the search results page itself

In 2024 AI overviews were launched by Google to answer search queries directly on the search results page. AI overviews take snippets of content from relevant webpages (often combining multiple sources) using Google’s existing search index and the same ranking systems as regular search.

Since their introduction, AI overviews have rapidly increased and are now a prominent feature on the majority of search results pages. U.S data from the end of 2025 shows that overviews appear in over 60% of all search queries, doubling from 2024.

New Data: Google AI Overviews Now Appear in 60% of Searches

The information source is attributed using tags, which contain a link to the website itself. However, we are seeing a trend of people finding the information they need and relying on the overview without visiting the website where the information originated. This is known as ‘zero click behaviour’.

Screenshot of an AI search summary about how to apply to the University of Edinburgh, with the University logo displayed. There is a circle around the source tag for emphasis.

Example of an AI overview

 

 

 

 

 

 

 

 

 

The rise in ‘zero click behaviour’

The introduction of AI overviews has meant that people have started to become accustomed to getting an instant answer on the search results page. People are more often relying on overviews, rather than clicking a link to a relevant webpage to locate the information themselves. This means fewer people are making it to your webpage and if they do it may well be later on in their search journey.

In Q1 2026 studies report that 65% of searches on Google did not result in a click to anywhere.

Zero-Click Crisis Worsens – SuperPrompt

This figure is predicted to be significantly higher for those using mobile when searching.

Also statistics from 2025 show that 80% of people used answers directly on search pages and 50% relied on AI summaries for answers.

Zero-click searches reshape marketing strategies in 2025

These changes in search behaviour do require you to think a bit differently about the way your content is being used. This is summed up well by Guus Goorts, an education marketing coach, who says:

LLMs [Large Language Models] increasingly visit  your website on your audiences’ behalf.

Ways to make your content ready for AI

In the session we focused on the things that you can do to optimise your content for AI. Hopefully you will be glad to know that much of the evergreen content design advice we provide still stands strong in the face of the new AI search landscape.

Clear, self-contained content gives AI better material to work with

As AI can sometimes take just snippets of your page or grab sentences out of the wider context, one step you can take is to try to make sure that content makes sense even outwith its surrounding context.

The more self-contained and specific your content is, the more likely it is that AI systems will interpret it correctly and present accurate information to users. You can achieve this by avoiding:

  • non-specific or generic headings that rely on page context, but do not make sense when lifted off the page – for example ‘Funding’ rather than ‘Postgraduate funding options for international students’
  • references to content elsewhere on a page such as ‘see below’ or  ‘as mentioned above’ as AI may retrieve the sentence without the content it refers to
  • vague descriptors in the form of unclear or missing subjects such as ‘This must be submitted with your application’ as if the surrounding text is missing, neither the reader nor AI knows what ‘this’ refers to
  • videos without transcripts, captions or summaries as AI tools cannot watch video content, they process text far more reliably than video

Answer questions directly and avoid unnecessary preamble or woolly language

AI predicts likely answers from the content it finds. It can potentially miss the answer if it’s buried in long winded sentences, or not clearly explained.

In the session we gave the example of a prospective student asking: “What accommodation does the University offer?”

We provided two example bits of content that the AI could draw from.

Example 1 : ‘Our accommodation includes single rooms, shared flats and accessible housing.’ This contains the answer directly, it names the accommodation types and it can be lifted into an overview without losing meaning.

Example 2: ‘There are lots of options of different accommodation with various numbers of rooms depending on your needs.’ Whilst this sounds friendly it doesn’t provide much useful information. Phases such as ‘lots of options’ and ‘to suit your needs’ take up space without answering the question.

Content that is well structured and accessible is still key

Making sure your content is both well-structured and accessible is still key when we are looking at how AI will use and interpret it.

Frequent, meaningful headings add structure

Headings are one of the main ways people navigate content, they act as signposts, helping users quickly identify relevant sections and understand what information sits underneath them at a glance.

Frequent, meaningful headings also play an extra role in supporting the AI-generated summaries we know are becoming increasingly common. This is because headings help AI understand the structure of a page by breaking content into logical, retrievable chunks.

Headings also create a hierarchy that shows the relationship between different pieces of information on a page. Therefore, you should always mark up headings with the correct heading level, rather than using bold, underline or larger font sizes. AI also uses the heading hierarchy to:

  • understand, summarise and cite your information
  • work out which topics are primary, which are subordinate, and how information is grouped together

You can read more about using headings effectively in the style guide, our previous blog post and also on Caroline Jarrett’s ‘Editing that works’ website.

Accessible content and AI overlap

Content that has been made accessible is a big step towards being AI-ready as screen readers and AI systems rely on many of the same signals, although the outputs are different. Therefore many of the things you hopefully already do to make content accessible will also help AI understand it. We can demonstrate the overlap by looking at headings, link text and alternative text.

Headings: screen reader users use headings to navigate the page structure, whilst AI tools will use them to understand and prioritise your content.

Link text: descriptive link text provides context and helps screen reader users decide where to go next, whilst AI tools will use this link text to help interpret page meaning and relationships between content.

Alternative text: well written alternative text helps users who cannot see images extract meaning from them, whilst it also provides text that AI can use to understand image content.

You can read more about how to make your content accessible in Mel’s blog posts from previous Content Improvement Club sessions:

Descriptive link text supports users and AI

Descriptive link text is important for users as it helps them understand where the link will take them at a key decision point. This is increasingly important for AI too as AI search and retrieval tools use links and their surrounding context as signals to understand the relationship between different pieces of content.

Therefore, a link labelled ‘Accommodation options for postgraduate students’ provides a much stronger signal than ‘Learn more’ as it helps AI understand both the destination content and how it relates to the current page.

Descriptive link text also helps AI-generated summaries and citations. When AI retrieves content to answer a question, it attributes the source(s). Clear link text can reinforce what a linked page is about and strengthen the connections between related topics.

You can read more about writing effective link text in the style guide and Caroline Jarrett’s ‘Editing that works’ website:

Write for humans, using plain language

In the age of AI, it’s still important that we write for humans first and foremost. This means using language that your users understand within your content and explaining terms they might not know. Short paragraphs and sentences will also help.

Google’s advice for content to be successful with Google Search is to focus on creating ‘people-first content’, rather than content made ‘primarily to gain search engine rankings’.

Creating Helpful, Reliable, People-First Content | Google Search Central 

You may find Nick’s blog post from a previous Content Improvement Club useful on this topic:

Now you’re speaking my language – what we covered in the February Content Improvement Club session

We worked in small groups to put the theory into practice

After our whistlestop tour of advice to help make content AI-ready, we then worked in small groups, using pages that attendees had brought along to the session. We each picked one or two areas to focus on and shared suggestions to improve the content and talked about what was perhaps already working well. This created some interesting discussion and allowed attendees to gain feedback and new perspectives on their content from colleagues they may not usually work alongside.

Frequently Asked Questions – the debate continues

The debate around the effectiveness of Frequently Asked Questions (FAQs) is one which has been circulating for some time within the content design world. It has reared it’s head again in relation to AI, given the rise of the ‘answer economy’ where people are typically asking more focused questions and looking for a quick answer.

The main point of contention is whether or not we should be writing more content in a question and answer format. There are different views on this topic, we’ve seen advice to use questions in your content that aim to match the questions that users are asking AI tools.

On some interpretations of this advice, you could read this as a call for more FAQs on websites. We’d like to urge caution before you take this approach though as FAQs aren’t without their problems.

FAQs can often:

  • duplicate content that you have elsewhere on the site – this causes problems for site maintenance and search engines don’t tend to like it
  • answer questions that aren’t really frequently asked
  • make content hard to scan because they push keywords away from the left of the screen as they often start with ‘Can, What, How, Where’

So in summary, don’t rush to change all your headings to questions and create more FAQ sections. If you do use questions, answer them without waffle.

The University of Bath have written a helpful article about this topic.

Why AI doesn’t need Frequently Asked Questions (FAQs) | Digital Content and Development

Content maintenance is more important than ever

The final point we covered was the fact that content maintenance is more important than ever. This is because all published content can be cited by AI to generate an answer regardless of when it was last reviewed or updated. Therefore ensuring that you know what live content you have and whether it’s up to date is key if you want AI to bring back accurate information in response to search queries.

Duplicate content can also confuse AI, so regularly auditing your content to make sure there is effective cross referencing between pages and that the same information doesn’t appear on multiple pages, will again make it easier for AI to interpret and find what it needs.

How to hear about future sessions

We promote these sessions via our mailing list. If you’re interested, please sign up:

Join the UX and Content Design mailing list (University login required)

Suggest a topic for a future session

We’re keen to continue covering topics that colleagues across the University would find useful. It would be really helpful if you could let us know any ideas you have using this form:

Suggest a topic for Content Improvement Club (University login required)

Other training that we offer

More training is listed on the User Experience Service website:

Training | User Experience Service

What I learned at UX Scotland 2026

UX Scotland is an annual two-day conference for people working in user-centred design. This year, I went along to the John McIntyre Centre to hear about the latest developments in UX. In this post, I’ll write about my highlights from the conference.

Object-oriented UX in action: rebuilding a public sector website with structured content

Joey Gartin presenting at UX Scotland 2026. Slide shows text System model in action. Slide has a strange pink and yellow tinge to it.

Joey Gartin presenting at UX Scotland 2026. Weird slide colours courtesy of my phone.

The challenge: dividing up content and naming groupings

Out of all the talks I saw, this was the one that I found the most interesting. Joey Gartin, a content designer at Renfrewshire Council, told a story about a multiyear project to redesign the council’s website. It started with a familiar situation: the council had a large website that people found confusing and hard to use. Users couldn’t find things, and when they could, it wasn’t always easy to understand.

Renfrewshire Council needed to work out a better way to divide up and group the content on their website. Then they needed to name those groups in a way that made sense to people.

I enjoyed hearing about this because this is one of those problems that never seems to go away. When we work with digital content, whether that’s designing a homepage or tidying up a shared set of folders and files, we’re constantly looking for ways to group things. Then we’re also constantly looking for names for those groups that will make sense to people.

OOUX involves favouring nouns over verbs

Renfrewshire Council approached the problem using methods from Object-Oriented User Experience (OOUX). This is an approach to digital product design that focuses on establishing the things (or ‘objects’) that matter to your users. The approach emphasises the importance of working out the nouns involved in your service before you move on to the verbs. I’d read a bit about it a while ago on Duncan Stephen’s blog:

Duncan Stephen writes about how the Scottish Government have used OOUX approaches

The argument in favour of focusing on nouns is that this approach is more closely aligned to how people think. When you walk around a supermarket, you have a shopping list of objects. To reflect this, a supermarket is typically organised into sections that reflect broader groupings of those objects: Fruit, Vegetables, Pasta, Cake, and so on.

In a similar way – the theory goes – people often approach websites with a list of nouns in mind. They are therefore scanning webpages for keywords that match these nouns.

But many council websites use a hybrid of verb-based groupings and noun-based groupings. So you get sections called Pay, Apply, Report and Request forming a core part of their information architecture. Here are two examples.

The City of Edinburgh Council:

Screenshot of the homepage of the Edinburgh Council website, showing links reading Click to pay, Click to report, and Click to request. Other panels show links to Council tax, Bins and recycling, and roads, travel and parking.

West Lothian Council:

Screenshot of the homepage of the West Lothian Council website, showing links reading Pay for it, Apply for it, Report it. and Request it.

 

Renfrewshire have not adopted this model. While their page titles often start with verbs, the groupings for these pages overwhelmingly use nouns:

Screenshot of the homepage of Renfrewshire Council website, showing sections titled Council tax, Bin collection day, School dates and Renfrew Bridge.

Renfrewshire Council

Joey cited the City of Sydney as another public body using this approach:

Screenshot of the homepage of the City of Sydney website, showing sections titled Frequently accessed, Waste and recycling, Building and construction

City of Sydney

OOUX helped Renfrewshire Council to create templates

With your objects figured out, the next step of an OOUX approach is to work out:

  • the relationships between objects
  • the calls to action that objects offer users
  • the attributes that make up objects

Joey talked us through this work. He also talked about how Renfrewshire Council used this as a foundation to create templated designs for common page types.

For example, take these two pages, both categorised as ‘service requests’:

Because they’re both service requests, you can see common sections on both pages.

For example, on the ‘Report a housing repair’ page, you have sections called:

  • Before you report a repair
  • How to report a repair

And on the ‘Graffiti’ page, you have:

  • Before you report it
  • How to report it

Joey showed us how this works behind the scenes. Renfrewshire Council use custom content types in Drupal to help structure the content writing process. So if you’re a content editor writing a service request page, you’ll be prompted to add a section on ‘Before you report it’. This helps content writers know what they need to include in a page. It also brings consistency to the website, which ultimately benefits users.

My reflections on how templates could work at Edinburgh

At Edinburgh, we use content types in our Drupal-based CMS EdWeb to create News and Event pages. So it was interesting to see another public sector website using a more extensive set of content types in Drupal. It made me reflect on how this approach might work for us. The context is so different: at Renfrewshire, it sounded like they had a more centralised approach to content management. The bulk of Edinburgh’s content publishing model is more devolved, which makes templated approaches to content more challenging. But there are clearly benefits available when you can make it work.

So lots to chew on from this talk, and it was a fun presentation to boot.

Other highlights

Sara Wachter-Boettcher on burnout

Sara Wachter-Boettcher’s keynote, “You don’t need more grit: breaking the burnout cycle in UX” was a run through of how and why burnout affects designers working in tech. It was a useful reminder to appreciate the limits of our influence within an organisation, and to be careful not to attach too much of ourselves to our job. It was cool seeing Sara in person. Her book Content Everywhere was one of the first things I read when I started in my role, and I thought it was really good.

Sara Wachter-Boettcher

Craig Abbott on AI and accessibility

Craig Abbott spoke about the risks and opportunities of using large language models for website design and fixing accessibility issues. One point that stood out was that LLMs are trained on some pretty ropey data. WebAIM estimate that 95% of the top million websites have detectable WCAG 2.2 failures, and these are the kinds of site that LLMs are trained on. So if you ask an AI to create a website, it will often produce something that superficially looks ok but is packed with accessibility problems.

The WebAIM Million: The 2026 report on the accessibility of the top 1,000,000 home pages

Craig showed us an example of a website he’d quickly created with AI and talked through the accessibility problems. He also showed us his other experiments. He’d had inconsistent results using AI to detect heading level failures or write alt text that took the context of an image into account. But he’d had some successes with using AI to complete more technical tasks with testable results.

Craig Abbott

James Chudley on digital sustainability

James Chudley presented on bringing sustainability practices into digital design. The highlight for me was seeing his experiments with visualising page weight across a website. Taking inspiration from an infographic using colour bars to illustrate rising global temperatures, James had applied a similar idea to visualising where a website is using more energy-intensive design choices.

James has posted his slides here:

James Chudley: Presenting ‘Beyond human centred design’ at UX Scotland

Another great conference

UX Scotland was a good chance to hear from some leading lights in the field, catch up with people and hear about some case studies that are relevant to us at Edinburgh. The two days were well organised and it gave me a lot to think about as we continue to support UX and content work at the University.

UX Scotland

Redesigning the ‘Understand what your content is for’ module of the Effective Digital Content course

A year on from the relaunch of our Effective Digital Content online course, we’ve recently made some improvements, particularly in relation to the ‘Understand what your content is for’ module. We’ve rewritten the module, moving from a video to a text-based format.

In this blog I’ll share a bit about the updates we’ve made and the thinking behind them.

Over the last year we identified ways to improve the module

It was always our intention that the course would follow a cycle of continuous improvement, where it would evolve when we identified ways to make it better for learners.

Over the past year, we’ve learnt quite a lot about what makes a module effective through our work to adapt the course for external audiences. Although this project has paused for now, the work has allowed us to improve the course for University colleagues.

We’ve also continued to learn about people’s preferences in how they like to consume information, as well as the environmental impact of the content we create and maintain.

Developing a proof-of-concept course for external audiences gave us a fresh perspective

When exploring how we could evolve the course for external audiences earlier this year, we had to think about new ways to teach certain concepts. The video in the first module explaining the importance of understanding the audience and purpose of your content was one of the areas we knew would need most work. The video had been produced many years ago, specifically for University staff and therefore contained various terms and references that wouldn’t be appropriate for an external course.

We knew how important it was to get this module right as the principles it teaches underpin the rest of the course topics. It involved going back to the drawing board to consider the key learning outcomes of the module and the practical skills we wanted to teach. This process provided the opportunity to re-imagine what the module could become and importantly whether we needed video to convey key messages.

Screenshot of notes from a Miro board showing the key learning outcomes we decided on for the module, as well as sticky notes to identify what outcomes come from: reading the text, doing the set exercises, selecting own web content and doing activities on that content, and getting feedback on exercises on own content.

Planning the learning outcomes for the module on a Miro board.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Ongoing user research showed video was not always the preferred format

We were also aware from speaking to colleagues who had taken the course and in usability testing of the new module, that video was not always their preferred method of obtaining information. Some colleagues mentioned that their preference would be to view or download the transcript instead of watching the video in full, even if the video was relatively short. The benefits of this approach were that they could digest the information at their own pace and be able to refer back to relevant points more efficiently, rather than having to locate the correct place in the video.

These insights, alongside the time intensive process involved in producing and maintaining a new video influenced our decision to reconsider whether a text-based format would work better.

The environmental cost of media use cannot be underestimated

We’ve also been learning through ongoing research into digital sustainability about the environmental cost of media use, particularly images and videos. We’ve learnt the importance of considering the value that the media brings before choosing it as a medium to communicate your message. You can read more about this work in my previous blog.

Videos and images – when do they add value and not just page weight?

As a result, we’ve been questioning whether the video we previously used in the course enhances clarity, context or understanding, or whether we could convey the same information without it.

The module has evolved but the underlying principles remain

We came to the conclusion, based on user feedback and our own inclinations about how to improve the module, that we would remove the current video in the internal course and replace it with a freshly written text format module.

The underlying principles of the module stand true – that the starting point is always to think about the audience and purpose of your content. As a result, the accompanying workbook activities for the module remain unchanged.

There are a few new additions to the module

We’ve added in a new section to explain the key concepts of user needs and business needs, which should help to provide a good foundation for later modules. There are also some more practical University related examples of key concepts.

The previous iteration of the module didn’t have any interactive elements. We’ve received positive feedback on the quiz questions we’ve included in other modules of the course so we decided to include two multiple choice quiz questions so you can check your understanding as you go.

How to take the course

If you’d like to take the Effective Digital Content course, you can find more information on our course page, including a link to enroll through People and Money.

Effective Digital Content

Representing the University at UCISA Women in Tech 2026: My takeaways and reflections

I was pleased to have a talk accepted at the annual UCISA Women in Tech (WiT) conference. I went to Newcastle for a day of talks, workshops and networking. I left with a better understanding of the WiT community , and a reinforced appreciation of the need for inclusivity in Higher Education.    

UCISA is an industry body supporting digital professionals working in the education sector. I have been actively involved in UCISA since 2022 when I helped set up the UCISA UX Group and became co-chair of this UK-wide community of practice. I’ve organised many UCISA UX events but had not attended one of UCISA’s flagship annual conferences, the Women in Tech event, until this year. My presentation about our project on staff profiles resonated with attendees, I learned a lot about diversity and representation in the sector from attending the other talks and I enjoyed connecting with other Higher Education professionals over shared inclusivity challenges. Here, I reflect on my highlights from an interesting day.

Sharing our staff profiles work piqued interest from other universities

As well as the clear focus on inclusivity, one of the themes of this year’s WiT was real-world applications and problem-solving. I felt our staff profiles project spoke to this theme, so I submitted a talk to share what we learned from research and the steps we have taken towards finding a new profiles solution.

My session was well received – perhaps unsurprisingly, colleagues from other institutions shared the same concerns and challenges in designing a profile solution that showcases staff in the best light, keeps them findable in searches, and yet remains easy for staff to update. I valued the chance to make new contacts, exchange ideas, and learn about other institutions’ diverse approaches to the ‘profiles problem’. I resolved to stay in touch as we take steps towards implementing a profiles solution at the University, recognising just how universal this need is across the Higher Education sector, and seeing an opportunity for meaningful collaboration.

Read more about the staff profiles project in the blog post series:

Collected blog posts about staff profiles project

Results of a 2025 WiT survey revealed risks and opportunities

One of the core activities of the UCISA WiT committee is to regularly collect data to understand diversity within IT departments across the FE/HE sector. At the conference, WiT committee co-chairs Christi Hopkinson and Katie Wilde shared a preview of the results of the 2025 survey, completed by more than 200 respondents from 66 institutions, with 74.5% of the respondents identifying as female. Several findings stood out from the preliminary report in terms of risks and opportunities.

There’s a risk of retention due to barriers to progression

Responses to a question about progression routes revealed significant proportions of respondents had started in IT in the following areas:

  • First/Second Line Support
  • Application Support
  • Business Analysis
  • Project Management
  • Web Development

Responses to a follow-up question about the roles respondents were currently working in showed continued representation in these areas, which indicated a degree of stasis when it came to progression in the sector. Areas where women were underrepresented included:

  • Infrastructure
  • Security
  • Enterprise Architecture
  • Senior Management.

The survey results showed a third of respondents had considered leaving their institutions or the sector, citing pay, workload and progression as popular reasons motivating them to think about moving on. Common blockers to progression included:

  • Lack of available higher-grade roles
  • Promotion structures tied only to management, not technical excellence
  • Career pathways not transparent
  • Women having to ‘prove more’ to progress

There’s potential to be gained by investing in non-technical skills

Most respondents cited the following skills as important for the roles they were currently in as well as for progression:

  • Problem solving
  • Communication
  • Analytical skills
  • Customer service
  • Business analysis
  • Strategic thinking

This spread of skills reinforced the value of focusing training and development on non-technical abilities to complement technical skills, and to ensure expertise was appropriately directed to deliver on broader institutional goals.

There’s room to improve on diversity, inclusion and discrimination

Responses to questions about inclusion and belonging revealed positives and negatives about the workplace respondents were part of.

On the positive side:

  • 79% felt valued as part of a team
  • 67% felt they were treated fairly and equitably

On the less-positive side:

  • Only 34% felt the leadership reflected diversity in the workforce
  • 41% felt there were opportunities for careers advancement
  • 46% felt their organisation supported under-represented groups
  • 47% were satisfied with their organisation’s diversity initiatives

The spread of these numbers provided a clear steer of areas to focus on to achieve less exclusive, and better-balanced IT workplace.

Achieving inclusivity starts with individuals and requires thinking beyond statistics

The survey data gave a snapshot of the current state of inclusivity in the sector, however, anecdotes from individual presenters painted a more vivid picture of what inclusivity could look like. The WiT programme included several women sharing stories of their induction into tech and reflecting on their individual progression routes. It was refreshing to see the diversity of pathways they had taken and interesting to hear about what they had learned along the way, and their tips for success.

Monica Jones, Chief Data Officer at the University of Leeds acknowledged that career progression paths rarely run smoothly, and advised setting personal goals and milestones to work towards, to be best-prepared for promotion opportunities when these came up. Julia Lloyd, College Manager – Business and Law, at the University of the West of England, emphasised the benefits of ‘quiet leadership’ and shared tips to create space for different voices – such as thoughtful structuring of meetings, design of communication channels and rewarding contributions over confidence. A joint talk ‘The Not-So IT Crowd’ from Catriona Blair, Joanna Addison and Sasha Titus from the University of Kent, and a session by Amber Mothersille from the University of Northampton emphasised the value of non-technical skills in technical roles – recognising the need for empathy, trust-building and adaptability to strengthen teams and build excellent digital services.

Breaking barriers requires breaking old biases and habits

A final takeaway from attending the WiT event was a call-to-action to question the way we work – specifically to foster inclusivity by making room for new ways of thinking and for fresh perspectives.

In an interactive exercise led by Katie Wilde, we considered five roles necessary for the operation of successful teams (the Navigator, the Connector, the Builder, the Challenger). In a period of honest reflection, we shared the roles we naturally adopted in team settings, and the roles we tended to overlook or disregard. Going through this exercise was a good leveller as well as a reminder to make room for diversity in everyday team settings instead of relying on familiarity.

The day closed with a thought-provoking talk on male fragility, delivered by Jake Dovey, a UCISA mentor. Drawing on personal anecdotes experienced through his involvement with UCISA, Jake’s talk described instances where men had overreacted defensively to being challenged and where women had inadvertently softened situations to avoid potential conflict and ‘keep the peace’. Jake challenged the women in the room to recognise these instances going forward, and prompted a call-to-action for all to recognise these harmful patterns and call them out to collectively help break the disruptive cycle.

Final thoughts – WiT26 was less about women and more about inclusivity

WiT26 delivered a packed programme which encouraged me to think outside my work in UX and more broadly about the joint responsibilities we all have in creating and fostering an inclusive work environment. I came away with recommendations of books to read and concepts to learn more about, and a heightened awareness of embedding inclusive practices in my day-to-day work and activities. I am keen to see the full results of the WiT 2025 survey and to remain part of the WiT community going forward.

 

Studying ITIL Foundations: What I learned and what I questioned

Working in information technology, I have been aware of ITIL for a while but had never formally studied it. I attended a three-day training course and passed the ITIL Foundation exam. Here, I share my reflections and my review of ITIL.

ITIL (Information Technology Infrastructure Library) originated in the 1980s, developed by an agency of the UK government as a way to standardise IT service management practices. It’s now owned by AXELOS and used globally across a range of industries, including Higher Education. The University of Edinburgh uses ITIL to structure aspects of organisational governance as well as many of its processes. I was curious to learn about ITIL as I felt it would help me make sense of the way some things work within ISG.

Read more about ITIL:

ITIL website

I studied the ITIL 4 Foundation course, which covers concepts like the Service Value System, value co-creation between provider and consumer, the four dimensions of service management, guiding principles, and key ITIL practices like the service desk, service request management, incident management and change management. Going through the course and completing the exam, I came away with several reflections about ITIL and its application to modern digital services.

First rule of ITIL: It’s not supposed to just be about IT (but it mainly is)

For a discipline with IT in its title, it was surprising to learn that ITIL is actually intended as a more generic service management framework, supposed to be applicable to non-technical as well as technical services. ITIL’s IT roots were clear, however, as many of the examples intended to ground the abstract concepts related to management of very traditional technical services, and it was hard to visualise practices like deployment management applied to non-technical realms. Conversely, it was difficult to visualise ITIL flexing to be applicable to the management of emergent technical services, such as machine or AI-based services with rapidly evolving operating models.

Service dominant logic, continuous improvement and systems thinking were familiar

Many of the ITIL artefacts are expressions of service value, based on a fundamental concept that value from a service can only come if it is co-created. In other words, if a service is not used, it cannot create value (no matter how good it is). I’d previously learned about Service Dominant Logic, (described in 2004 as a marketing concept by Stephen Vargo and Robert Lusch), so it was interesting to make the connection between these two disciplines. Whereas Vargo, Lusch and others focus on value dimensions, and the interplay between operand and operant resources, however, ITIL delineated service value through models like the Service Value System and the Service Value Chain.

Continuous improvement was another key ITIL focus, but guided by artefacts like Service Level Agreements and practices like Service Request Management, and motivated by efficiency and compliance focused targets rather than user-focused improvement drivers like UX or CX.

Systems thinking was another thread running through ITIL, however, it seemed limited in its use to describe sequences of inputs and output from different activities in value streams – without inclusion of Soft Systems Methodology (described by Peter Checkland in 1989), universally useful as a way to diagnose problems.

ITIL’s terminology tended to overwhelm the logic and the purpose

Naming things is hard and changing the names of things can lead to even more confusion. When it came to the words used in ITIL, it seemed that those who developed ITIL had thought long and hard about what to call the models, processes, practices and so on. For the uninitiated coming to ITIL fresh, however, it was natural to question why things were named in certain ways and to forget and mix up the terms, as well as question the absence of certain concepts. There seemed little scope to mould the rigid ITIL glossary to real-life scenarios, instead it seemed at risk of institutions trying to fit ITIL rather than the other way around.

Considering this conundrum, I was reminded of work I began a while ago to reduce jargon in Drupal, and of my ongoing work to shape the Web Sustainability Guidelines to be universally applicable. In both instances I had learned of the difficulty in choosing the right words and phrases to meaningfully describe abstract concepts, and therefore could appreciate the length of time it could take small changes to take effect in such a well-established standardisation mechanism as ITIL.

Read about my work on Drupalisms in this blog post:

De-jargoning Drupal – working with the community to open up Drupal’s terminology

Read about my work on the W3C Web Sustainability Guidelines in this blog post:

Shaping the future of the sustainable web: The advent and development of the W3C Web Sustainability Guidelines

 

Drupal In A Day: What we learned (and what we still want to learn): reflections from the UX team

Drupal In A Day (DIAD) is an in-person training event, designed as a beginner-friendly hands-on introduction to Drupal, the open-source content management system. When the University hosted DIAD, several of the UX team took the chance to attend.

As content management systems go, Drupal is one of the mainstays. It’s been around for 25 years and is particularly famed for its robustness, reliability and flexibility – so much so it’s trusted to power websites of enterprises, governments and higher education institutions around the world. It’s open-source so there’s no proprietary lock-in – the functionality, features and innovation available in Drupal comes from a thriving worldwide community of contributors – as individuals, agencies and organisations.

One of the best places to learn about what Drupal is, what it stands for and what it aims to achieve is the blog site of its founder, Dries Buytaert.

Dries Buytaert blog

In 2025, Hilmar Kári Hallbjörnsson taught the first Drupal In A Day on the final day of DrupalCon Vienna.  Hilmar had been teaching Drupal to students at the universities of Reykavik and Iceland for many years and felt strongly that teaching Drupal to new generations, to inform them of its capabilities, and to inspire them of its potential was something the Drupal community needed, as a way to nurture the longevity and sustain the future of Drupal. Through a tremendous effort, he made the first Drupal In A Day happen in Vienna in October 2025. It was very well-received, successfully establishing the Drupal In A Day format going forward.

Read more about the first Drupal In A Day in Hilmar’s blog post from 2025

Drupal in a Day: Vienna 

Hilmar travelled to Edinburgh to deliver Drupal In A Day with our own Web Development Team Manager, Gareth Alexander at the start of June 2026.  Nick (Senior Content Designer), Shlok (AI and UX Innovation Intern) and Hannah (Digital Content Style Guide Intern) from the UX team signed up for the event along with other LTW interns and staff from the wider University with an interest in learning about Drupal. Here, they reflect on their experiences of the day.

Nick’s reflections 

I attended this training to bring my understanding of Drupal up to date. The last time I set up a Drupal site was in the early 2010s, and a lot has changed since then. With Drupal providing the backbone to EdWeb 2, I wanted to get to grips with some of the terminology and concepts that underpin conversations within our team about what our central CMS can do. 

I was particularly interested to learn more about Drupal CMS, a new service that helps you set up a Drupal site more quickly and with less need for technical understanding. 

After getting the required software set up on my laptop (thanks Kirsten), I clicked along with Hilmar and Gareth as they walked us through the various sections of Drupal CMS. We worked through steps to create a new content type and we created different Views to display the same content. We tweaked image formats. We also learned how to attach tags to a piece of content and how these tags can act as a filter for overview pages. 

By the end of the day, I hadn’t suddenly become a Drupal expert. But I did have a better understanding of how EdWeb 2 works behind the scenes. In particular, I felt like I knew more about how EdWeb 2 takes the content you enter when you create a page and presents this in different ways elsewhere on a site. 

Alongside that, I would now feel more confident in setting up a new Drupal CMS site, and I now have a better understanding of what this system offers in comparison to other ways of operating a website. 

Finally, the day gave me a better sense of how the community aspect of Drupal is central to how this project keeps going. Hilmar and Gareth emphasised that there are various events in the calendar where people working with Drupal can meet up and collaborate. That’s a powerful message: that anyone is invited to learn more, become part of the community and contribute to how this system works. 

Shlok’s reflections

Before starting my internship, Drupal was a completely new concept to me. I did not really know what a content management system was, how Drupal worked, or why it was used by universities and other large organisations. Because of that, Drupal In A Day was a really useful introduction for me. 

I thought the format worked well because going through everything in one day helped keep a flow of information. It was quite intense and sometimes fast-paced, but that also meant we were able to cover a lot of concepts in a short amount of time. I would say I was able to follow around 70% of the session, which felt like a good start considering Drupal was completely new to me. 

One of the parts I found most useful was the introduction to Drupal itself. It helped me understand what Drupal is, what a CMS is, and why the University uses it. I learnt that Drupal is valued because it is stable, secure, flexible and open source, which makes it suitable for large and complex websites like those used by universities. This helped me understand why Drupal is still used by many major institutions. 

I also found it interesting to learn about the Drupal community and the different ways people can work with Drupal. Before the session, I assumed Drupal was mainly for developers. However, I learnt that people can build careers around Drupal in different ways. Some roles involve coding and development, while others focus more on design, content, user experience, training or project work. That helped me see Drupal as more than just a technical platform. 

One point that really stood out to me was when we were told that Drupal has a steep learning curve at the start. This was useful to hear because it made the difficulties I was facing feel expected. Since many people find Drupal challenging in the beginning, it was reassuring to know that not understanding everything straight away was normal. It made me feel more comfortable continuing to learn. 

During the practical parts of the day, I learnt about some of the basic Drupal features, such as creating and managing content pages. At first, this was quite confusing because the concepts were new to me. However, as the day went on, I started to become more comfortable with the terminology and the way Drupal is structured. 

Another part that I found very helpful was the follow-up assignment where we had to build something from scratch. After learning so much in one day, I think it was important to have a task that allowed us to apply what we had learnt. It helped me consolidate my knowledge, see which parts I had not fully understood during the session, and become more comfortable with Drupal before starting work on my internship prototypes. 

One thing I would have liked to learn more about was the command line and the use of terminal commands. We touched on some setup and development processes, but I think spending more time on what the commands do and how they fit into the Drupal workflow would have helped me. I would also have liked to learn more about the coding side of Drupal, especially how to build custom Drupal modules. This is particularly relevant to my internship because my work is focused on AI and innovation within Drupal. 

If I could suggest one change, it would be to make Drupal In A Day into a two-day or three-day format. The first day could stay mostly the same, giving everyone a broad introduction to Drupal. The second day could be a slower guided session where participants build something with support from the instructors, similar to the assignment we were given afterwards. A third optional day could focus more on coding and custom module development for those who want to explore the technical side further. 

Hannah’s reflections 

I signed up for the Drupal in a Day training with very little knowledge of the CMS beyond working with existing EdWeb 2 sites, such as when creating prototypes of Style Guide pages or writing blog posts. So, I was interested in increasing my knowledge of Drupal as well as gaining the ability to build a site. Before the training began, I was unsure how well I would follow the instructions as a beginner, but Hilmar, Gareth, and all of the members of the Drupal community who were present at the training were extremely helpful, informative, and patient when it came to giving assistance at points where I was confused or behind. 

Once I had overcome a technical error with my laptop and decided to use Drupal Forge, I was able to follow along with the instructions being provided and replicate the Artist biography pages that Hilmar and Gareth were demonstrating. The course was fast-paced and detailed, and while maintaining this pace was a challenge, it made the course engaging and the product of the day felt like a genuine accomplishment. 

With the knowledge that I gained throughout the training, I feel that I have a strong foundation that will allow me to continue to develop my skills in building a Drupal site further in the future. In particular, I think the example site that we were creating during the training was incredibly useful in that it allowed us to try out several different aspects of building a site with Drupal, such as different content types, tags, and images, as well as exploring some different design options as well. 

I was impressed to learn about how community centred Drupal is, and that contributions and developments to Drupal are made by users and members of the community. Gareth and Hilmar’s explanations of how this works really helped me to understand why Drupal is as adaptive and intuitive as it is (such as in its security and bug fixes), which is that these developments are a direct result of user experience. Furthermore, Gareth and Hilmar also emphasised the flexibility of Drupal, due to the ability to install ‘recipes’ that customise the functionality of sites that you are building. 

Overall, I think Drupal in a Day was an extremely useful and practical training session that has equipped me with the skills to build a basic site and further develop these skills whenever I have the chance.  

Emma’s reflections

When it comes to Drupal, I am largely self-taught – pretty much everything I know has been gleaned from reading, attending/watching sessions from Drupal events, and (predominately) pestering people in-the-know with my questions. When Drupal In A Day came to the University, I pondered whether I should attend. I’ve contributed to the community since 2022. I’m on the Drupal leadership team. Surely I should know Drupal by now? I took a split second to reflect and realise that you never fully know Drupal. There’s always something new to learn, something to challenge what you thought you understood, or something to clarify an area you weren’t quite sure about. Conscious of not taking a space away from a complete Drupal beginner, I opted to sit in on the event, to follow along, while working on other things.

The day combined practical exercises with general Drupal knowledge. Hilmar and Gareth began with the basics, covering key parts of the process to get started and familiarise with Drupal – like setting up DDEV, using Drupalforge and creating a Drupal.org profile. As the day went on, it was great to see quick progression to experiment with some of Drupal’s flagship modules, especially Drupal Views which holds huge power for presenting and displaying structured content in a range of adaptive ways.

Drupal CMS, Drupal’s low-code product provided the playground for learners. Having worked on Drupal CMS since it began, I found it heartening to see it being used to introduce Drupal to new audiences, to help them learn what Drupal has to offer and to help them start ideating on how they might use it. Adopting a UX perspective, I tuned into comments from fellow attendees about Drupal CMS, noting observations to follow up and logging areas for UX improvement to carry forward in my ongoing Drupal UX contributions.

Reflecting on the day as a whole, it helped attendees achieve what is often the hardest thing about Drupal: Getting started. All too often people new to Drupal can find it overwhelming, and they find when everything is possible it’s hard to choose a direction. Drupal In A Day sets learners on a path to start discovering Drupal and making it their own, in other words, planting a seed from which the community can continue to grow.

What we learned from Power BI training

In May, Mel and Nick from the UX team attended two days of Power BI training with QA. The training covered the basics of using Power BI Desktop and, through a mix of instructor-led and independent exercises, gave us a chance to transform data and build visualisations.

Mel’s reflections

Before the training, I’d only ever experienced Power BI from the other side, seeing polished dashboards and interactive visuals without really understanding how they were built. By the end of the training, I felt much more confident using Power BI and excited to start applying it in my work.

Learning through doing

The sessions suited the way I learn best: having a go, clicking around, experimenting and working through exercises rather than just watching demonstrations. Having the training in person made a big difference, as we could troubleshoot problems together and ask questions whenever we got stuck.

I also appreciated the pace and structure of the training. Our instructor, Jason, talked through each step clearly and acted as a guide throughout, explaining not just what to do, but why we were doing it. His knowledge of the system really came across and the sessions felt approachable rather than overwhelming.

Movie datasets solidified my understanding

The most enjoyable part of the training for me was working with the movie dataset. We pulled together information from sites like Box Office Mojo and Rotten Tomatoes to consider how data from multiple sources can be combined to tell a richer story. In doing so, the relationships between datasets, transformations and visualisations became much clearer.

This was  the point where I had the “eureka” moment of understanding how all the different pieces of the puzzle connect together within Power BI.

Keen to keep the Power BI momentum going

Since the training, I’ve been keen to build on what I learned by applying Power BI to real project work. I recently used it to explore qualitative survey data relating to digital design tools, using techniques from the training to clean and organise the data. The training materials proved especially useful, particularly the exercise workbook, which gave me something practical to refer back to.

Working with a familiar dataset made the process feel much less intimidating. It was rewarding to apply what I’d learned so quickly in a real project context.

Nick’s reflections

I thought this training was excellent. I’d seen Power BI dashboards before but didn’t know what you have to do behind the scenes to create them. I attended this training to learn a bit about how Power BI works and improve my skills around working with data more generally.

How Power BI can support UX work

I was interested to see how Power BI could support our work in the UX Service. We work with data that supports our administration of training sessions and our online course Effective Digital Content. We also sometimes deal with sitemaps and analytics, which can include a daunting amount of information. All of this data needs to be tidied up and visualised so we can quickly understand it and use it. While we can do some of that in Excel, spreadsheets have their limits and I wanted to find out what Power BI has to offer.

What we learned

The training involved clicking through activities with our instructor Jason. I found this was a good way to get to grips with the software, and I gradually built up a rough conceptual model of what was going on within Power BI.

In the session, we learned how to:

  • ingest data from sources such as spreadsheets and webpages
  • combine data from different sources
  • tidy up data
  • do operations on data
  • visualise data

In person training worked well

Doing the session in person meant we got to catch up with colleagues in our department while completing the training. It also made it easy to get pointers when something didn’t work. We could quickly ask a colleague to help with the minor problems that inevitably crop up when you’re learning to use a new piece of software.

I came out of the training with an appreciation of what Power BI can do, and a better understanding of how it works. I’d recommend this training to any colleagues at the University who are interested in learning more about working with data.

Why enterprise brands are backing WordPress in 2026

Our recent event, WP:26, was a deep dive into the future—and I was completely fired up to see us gather technologists, publishers, and platform leaders to explore the key patterns shaping WordPress in 2026 and beyond. We packed an afternoon full of talks and discussions, covering the massive impact of AI, accessibility, enterprise publishing, and evolving web standards on the essential role of a CMS.

To cap off a day of critical insight and conversation, we hosted a truly amazing final panel discussion, ‘Why we’re backing WordPress in 2026’, with an exceptional line-up of speakers.

Although Executive Director of WordPress, Mary Hubbard, was unable to attend live, she was kind enough to provide a video intro to kick us off:

“The question isn’t just which CMS should we use; it’s ‘which platform can and will evolve with us?’ WordPress’ enduring strength is its ability to adapt to changing demands and evolving organisational needs… What really sustains the platform is the ecosystem around it, the community, the contributors, and the organisations pushing it forward in production every day.” – Mary Hubbard, Executive Director, WordPress

The panel consisted of:

Meeting the challenges of enterprise publishing

The core of our discussion centred on how and why enterprise brands are actively choosing and investing in WordPress as their platform of the future. The conversation was grounded in the reality of the challenges faced by media companies in 2026—from managing content at a massive international scale to navigating a rapidly shifting technological landscape.

We heard first-hand accounts of how WordPress enables huge international publishing brands to meet these challenges. The consensus was clear: the platform’s adaptability, open nature, and robust ecosystem are its greatest assets when faced with the demands of an enterprise environment.As Gabriel Koen, SVP, Technology at PMC, noted:

“WordPress does a great job of staying modern… the fact that we’ve been able to build on top of it for almost two decades and still see it as the platform for the next several years is pretty remarkable.” Gabriel Koen, SVP, Technology, PMC

From Drupal to WordPress: The CERN example

One of the most compelling threads of the discussion—and something that really excited me—was the story of CERN, the birthplace of the world wide web, and their decision to embrace WordPress after moving from Drupal.

Joachim Valdemar Yde, Web Manager at CERN, provided amazing insight into how one of the world’s most significant scientific organisations chose to standardise on WordPress after a year-long, 14-requirement evaluation against alternatives like Wix and Squarespace. He stressed the importance of having a system that allows their users—scientists and researchers—to be content creators, not web developers.

The move by an organisation like CERN highlights a major shift: WordPress is no longer just a blogging tool, but a flexible, scalable, and future-proof enterprise platform ready for the next generation of web challenges.

Enterprise-grade solutions for what’s to come

The panel also addressed the essential role of enterprise-grade solutions and partnerships in preparing brands for the future. Steph Yiu noted a surge in new enterprise interest driven by AI, which I think is a really important shift:

“AI is forcing innovation across every business… We want to build on a future-proof platform. Closed just isn’t going to cut it for me anymore. I want to build on an open stack.” – Steph Yiu, CEO of WordPress VIP

This perspective underscored that enterprise adoption isn’t just about the open-source software itself, but also the world-class hosting, support, and strategic development partners that turn a flexible CMS into a mission-critical business platform. It’s the combination of the open-source core and the mature, robust ecosystem that provides true peace of mind for global brands.

The conversation also touched on the critical transition of AI from experimentation to production. Gabriel discussed using AI behind the scenes for content translation and processing vast print archives, while Umer shared News UK’s focus on leveraging AI to streamline print and digital publishing workflows to “take entire swathes of effort out of your business.”

If you want to make a dent with AI, you have to take entire swathes of effort out of your business and I think that’s really where the fundamentals are for us at the moment. We’re still a print business and it’s a huge part of our revenue stream, although it’s sort of counter to the WordPress ethos, WordPress is where we do all of our authoring for our print content or certainly where we want to move all of our authoring for our print content alongside our digital content. So, a big part of what we’re working on at the moment is how we streamline workflows. – Umer Ehsan, Director of Technology – Content, News UK

The Future-Proof Platform for Enterprise

If there was one idea that framed the end of WP:26, it was this:

WordPress is the definitive, future-proof platform for the enterprise web.

The final panel discussion reinforced the core message of the day: WordPress is evolving, driven by an open community and backed by the world’s largest digital brands. The platform’s ability to evolve, adapt to modern challenges (be it AI, headless architecture, or new publishing models), and maintain a stable core is why we—and so many others—are backing it for 2026 and beyond.

The collective backing of the panelists, from the platform’s governing body to global publishing and scientific institutions, offers an undeniable picture of its long-term viability and central role in the future of the web.

For me, this event was a tremendous success. We dove deep into the patterns shaping WordPress, and I’m immensely proud that we’ve once again brought together such a vibrant, community-driven event. My sincere thanks go to our incredible panel—Gabriel, Umer, Joachim, and Steph—for generously sharing their time and such critical insights with us. It’s the passion and commitment of people like them that truly sustains the platform and continues to push us forward in production every single day. I couldn’t be more hyped about what we’ll achieve together in the years to come.

Ready to explore all the insights and research from WP:26? Access the full WP:26 Event Replay page here and download our supporting market analysis report, ‘WordPress in 2026: The dawn of the intelligent CMS’.

The post Why enterprise brands are backing WordPress in 2026 appeared first on Human Made.

Why accessibility is fundamental in 2026

At WP:26, Human Made’s virtual event exploring the future of WordPress, much of the conversation focused on what’s changing across the web. AI is accelerating workflows, enterprise platforms are becoming more complex, and expectations around digital experiences continue to rise.

But in the middle of all that change, one session brought the conversation back to something more fundamental.

In a conversation with Rian Rietveld, we explored accessibility not as a compliance exercise or a checklist, but as a core part of how we design and build for the web. It quickly became clear that while the tools and technologies around us are evolving rapidly, the question of who we are building for remains just as important as ever.

Throwing off the shackles of compliance checklists, Rian delivered a clear and focused take on how accessible design fundamentally impacts your audience reach and revenue. Across an insight-packed 30-minutes, she guided us through the current state of WordPress accessibility, the awesome WP Accessibility Knowledge Base project she’s been working on, and—crucially—the highest-return investment teams can make today.

Read on to get the key moments and insights from Rian’s session.

From compliance to commercial reality

One of the most striking themes from the session was how quickly the conversation around accessibility is shifting. What was once framed as a compliance requirement is increasingly being recognised as a commercial imperative.

Excluding users with disabilities doesn’t just create a poorer experience, it actively limits your audience. As Rian pointed out, that audience is far from marginal. In fact, the cost of getting accessibility wrong is measurable, with billions in lost revenue each year in markets like the UK alone.

For teams building on the web, this reframes the challenge. Accessibility is no longer about meeting minimum standards or ticking regulatory boxes. It is about ensuring your product is usable by as many people as possible, not only because it is the right thing to do, but because it directly impacts reach, engagement, and ultimately, revenue.

Accessibility, AI, and search are converging

One of the most interesting parts of the discussion was how accessibility is increasingly intersecting with other concerns that teams are already prioritising, particularly around AI and search.

As highlighted throughout WP:26, machines are playing a growing role in how content is discovered, interpreted, and acted upon. Whether it is search engines, assistive technologies, or AI agents, all of these systems depend on the same underlying signals to make sense of the web.

Those signals are not new. They include things like semantic HTML, clear heading structures, meaningful labels, and predictable interactions. In other words, the same practices that have always underpinned accessible design.

What is changing is the level of importance. Accessibility is no longer a separate consideration running alongside SEO or AI readiness. It is becoming part of the same foundation. If content is not structured in a way that machines can understand, it becomes harder to find, harder to interpret, and ultimately less useful.

That convergence raises the stakes. Getting accessibility right is no longer just about supporting specific users. It is about ensuring content works in an increasingly machine-mediated web.

Actionable strategy: The highest-return on investment

If advising a digital leader, Rian shared the single highest-return investment in 2026: 

  1. Training people: Train your designers, content creators, and developers on how to build accessible products. Most accessibility is “just decent code, decent HTML.”
  2. Prioritise keyboard navigation: A website and all its functionality must be able to work with the keyboard only. This is the essence of accessibility and should be a non-negotiable testing priority.
  3. Contribute to the Knowledge Base: Rian encouraged the community to get involved with the WP Accessibility Knowledge Base to create one central source of truth for all WordPress accessibility documentation.

“If you create only for perfect people, people who have perfect eyesight, are clear of mind, can move their hands, are web savvy. Well, then you say, okay, only those people are allowed in my web shop and the rest of the people I don’t give access to and the rest of the people are quite a lot of people. So you have to take into account that you build for everyone, not only for perfect people.” – Rian Rietveld, Web Accessibility Specialist.

Ready to explore all the insights and research from WP:26? Access the full WP:26 Event Replay page here and download our supporting market analysis report, ‘WordPress in 2026: The dawn of the intelligent CMS’.

The post Why accessibility is fundamental in 2026 appeared first on Human Made.

AI: the impact on search, discoverability & strategy

On 12 March 2026, WP:26 assembled the brightest minds in the WordPress ecosystem to explore the trends actively redefining the platform. From AI-driven workflows and the agentic web to accessibility and the future of search, we went beyond the surface to unpack what’s changing and what it means for building with WordPress at scale.

One of the most insight-packed sessions came from Alex Moss, Principal SEO at Yoast, who provided a focused examination of the search landscape’s rapid evolution.

From SEO to AI Search Optimisation: Catch up on the replay of the session and read on to get the strategic takeaways from our essential WP:26 session on AI’s impact.

Throwing off the shackles of buzzwords and new acronyms, Alex delivered a clear and focused take on how the arrival of AI has fundamentally impacted search, content discoverability, and content strategy for all of us. Across an insight-packed 30-minutes, he guided us through where the industry has been, what’s happening right now, what the future might look like, and—crucially—what actionable steps enterprise teams can take today.

Read on to get the key moments and insights from Alex’s session.

The generative shift: from clicks to decisions 

The native search experience has been disrupted by Large Language Models (LLMs), moving from a list of 10 links to a model of retrieval and generation that delivers conversational, contextual, and increasingly personalised answers. The focus for publishers is now shifting from maximising clicks to driving decisions and selections via AI agents.

The rise of GEO (Generative Engine Optimisation)

Alex introduced GEO, defining it as:

“optimising content for generative AI search environments, like LLM-powered engines to make it discoverable, trustworthy, and authoritative.” – Alex Moss, Principal SEO at Yoast.

The key takeaway? “Good SEO is good GEO”, because the core principles correlate.

Actionable strategy: The four pillars for SEOs

Alex detailed the four crucial areas to focus on this year, including:

  1. Editorial standards: Mediocre content will not survive. Content must be unique and human-driven, but it must also be machine-readable (e.g., concise conclusions, proper headings, lists, evidence, and citations).
  2. Discoverability and EEAT: The goal is to assist the AI agent in synthesising the answer. This structural shift requires adherence to the EEAT framework (experience, expertise, authority, trust) to ensure your brand is validated by the system.
  3. Data integrity: Structured data is more important than ever. Technologies like Yoast Schema Aggregation and Cloudflare’s /crawl endpoints are emerging to allow LLMs to ingest an entire site’s structured data at once, leading to greater efficiency and fewer hallucinations.
  4. Success Metrics: Clicks and impressions are becoming less valuable. Discovery is the new valuable metric, and SEOs need to update their reporting to track how the brand is being seen and cited across different LLMs.

“If you’re one of those companies where if I go to the about page and read three sentences and I still don’t know what you do, that’s for the human. That’s not for the machine. Make sure that everything’s machine readable and make sure that everything’s concise, everything is structured well.” – Alex Moss, Principal SEO at Yoast.

Ready to explore all the insights and research from WP:26? Access the full WP:26 Event Replay page here and download our supporting market analysis report, ‘WordPress in 2026: The dawn of the intelligent CMS’.

The post AI: the impact on search, discoverability & strategy appeared first on Human Made.

❌