❌

Normal view

There are new articles available, click to refresh the page.
Today — 18 November 2026Main stream

10 Lessons Learned from Auditing 100 Online Stores

17 November 2026 at 14:57
We audited 100 top online stores and found up to 68% use fake timers, hidden fees, and dark patterns to force sales. The plot twist? These sneaky tricks actually trigger a massive 70% cart abandonment rate and destroy your long-term customer trust.
Before yesterdayMain stream

Scottish Web Folk 2026: UX team reflections

11 November 2026 at 10:24

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.

Some of the World’s “Best” Websites Are Actually Terrible

10 November 2026 at 15:09
Some of the world’s most celebrated websites are gorgeous, innovative—and absolutely miserable to use. Somewhere along the way, web design started rewarding hidden menus, hijacked scrolling and visual tricks over the one thing that actually matters...

Vulnerability that lets hackers SSH into Linux devices is under active exploitation

9 November 2026 at 19:41

Hackers are actively exploiting a recently discovered critical vulnerability that allows them to log in to privileged accounts on many Linux systems, multiple researchers are reporting.

The vulnerability, tracked under the name *sshole, arises from the interaction between OpenSSH and a code library known as musl. Linux systems that use both of these packages and meet certain other requirements can be hacked to give unauthenticated access to high-privilege accounts in a matter of seconds. *sshole became publicly known last Thursday and quickly stoked concerns it could lead to widespread compromise of Linux machines. Four days later, the prediction shows signs of becoming real.

Attackers conducting "mature intrusions"

Security firm Greynoise said Monday that honeypots it maintains in Southeast Asia have come under attack by a group it’s tracking as GT10. The group conducted “mature intrusions" into the systems, which Greynoise uses to detect attempted or successful attacks in real time. Greynoise subsequently gained access to a GT10 server that revealed potential other victims and some of the tools used in the campaign. A backdoor the group is using in the attacks contains Chinese language comments and appears to be generated with the use of AI.

Read full article

Comments

© Getty Images

Just do it for me? Balancing human and AI input in content improvement

6 November 2026 at 14:07

Working with student interns and contributing to the Drupal community, I’ve experimented with AI in various  tools designed to support content improvement. I reflect on what I’ve learned about peoples’ preferences for engaging with AI tools and consider wider design challenges for web content to support co-browsing.

Writing good quality, user-centred content has always been a challenge, and accordingly, a suite of tools evolved to address this; Hemingway, Grammarly and many more. With their ability to learn patterns and predict word sequences, the advent of LLMs provided a new direction for content improvement. Where previous tools had used fixed rules, algorithms and formulas to flag content problems and score sentences, LLMs changed the playing field as they were able to be prompted to rewrite and create text and to adapt words and sentences not only in line with fixed rules, but also aligned to different interpretations of style.

The UX Service’s content design course, Effective Digital Content, and our ongoing Content Improvement Club meet-ups are both designed to help staff publishing digital content for the University. It’s been encouraging to see a positive uptake for both training formats, however, we realise we can do more to help staff publish the best quality content they can, and to this end, for the past few years it’s been a privilege to support a series of interns in the UX Service to look at how we can innovate and apply AI to the persistent challenge of writing good quality, user-centred content.

Thinking beyond – embracing the spirit (or grasping the nettle, depending on how you look at it) of AI innovation, it’s sensible to note that, more broadly, the browsing landscape of the web is increasingly shifting to include AI agents as well as humans, giving cause to consider what using AI to design content to be consumed by AI might look like. That’s the subject of another blog post (or several).

For now, as I begin another phase of work with a new student in the role of AI and UX Innovation intern (Viktor Sharha), it felt timely to pull together what I’ve learned so far.

Designing, creating and editing content happens in various ways

When designing any user-centred assistive features, a good place to start is the current workflow or user journey people adopt to achieve the task in question. In other words, to look at the stages content editors currently go through to make sure their content is as good as it possibly can be.

One of my earliest research tasks when I joined the University was to usability test the Editorial Style Guide, to find out how publishers used it to keep their content consistent in EdWeb. This work gave me insight into the type of workflows publishers followed to get compliant content published. Some publishers worked in Microsoft Word, using the in-built spelling checker for typos, and cross-checking against a printed-out copy of the style guide for University-specific errors before pasting content into the EdWeb body text. Others went straight to EdWeb, checking their content line-by-line with a PDF version of the guide. Others relied on colleagues giving their work the once-over before pressing publish. Some used Grammarly and Hemingway, some didn’t.

Overall, there wasn’t a dominant content-publishing workflow, with unified friction points waiting to be alleviated through a standard user-centred design process. Instead, there were varied approaches, habits and ways of working which people had adapted over time to suit their specific circumstances and to address the areas they found difficult as individuals. Tools were used at different stages of the process, and to a greater or lesser extent depending on personal preferences.

Therefore, designing content improvement tools isn’t one-size-fits-all

It follows that, since people follow different pathways to create, design and edit content, tools to assist this process need to be developed in different ways to suit varied preferences. Since 2025, interns in the UX team have prototyped our own different content improvement tools to test with publishers, and we’ve also tested open-source tools that exist already, developed within the Drupal community. From our testing and research, we found pros, cons and nuances associated with different tools. The summary below pulls together detail of the tools and how they compared.

Tool 1: Drupal Editoria11y – no AI, flags errors in the editing interface

Editoria11y is a Drupal module built by John Jameson from Princeton University that automatically checks content inside the editorial interface. It was originally designed to catch accessibility issues, but it can be configured to check content against other rules too, such as institutional style guide conventions.

What it does and how it works: Editoria11y checks content as authors type, and also on previews and published pages. It includes an indicator bar to show how many issues are on the page and has inline markers to show where each issue is, as well as a dashboard summarising site-wide errors. When an issue is opened, a pop-up modal explains the problem and suggests a fix.

What worked well: In tests, publishers were able to make sense of the inline markers and understand how these related to the indicator bar for the whole page. They liked the tracked change visualisation in the pop-up modals, and were able to work through successive modals, accepting or ignoring the suggested changes.

What needed improvement:  Some publishers found the number of markers overwhelming, and since the pop-ups covered the text, it was difficult to judge each recommendation in context. In the pop-ups, some of the rule descriptions used formal grammatical terms (such as ‘ordinal suffixes’) which were unfamiliar to some publishers meaning they were confused about the problem to be fixed. Since rules were applied mechanically, there were instances where errors were missed, or where awkward fixes were suggested (such as swapping ‘1st floor’ for ‘1 floor’ due to straight removal of the ordinal suffix) – these degraded publishers’ trust in the tool.

Read more about what we found testing Drupal Editoria11y

Embedding the rules: What we learned UX testing a style guide helper tool built with Drupal Editori11y

Tool 2: ELM-powered content design chatbot – with conversational advice

This tool was developed by student Mostafa Ebid during a 2025 summer internship. It connected ELM, the University’s AI platform, to EdWeb2, so publishers could get help with their content by conversing with the University’s suite of LLMs without leaving the Drupal editing interface.

What it does and how it works: This tool sits in a chat sidebar next to the main Drupal editorial interface and offers three modes: Write Content, Design Content and Proofread. In response to a user prompt to improve content, it activates an orchestration of agents (each with specific tasks such as checking the style guide, structuring pages, profiling audiences) which read the page content and act on it accordingly, publishing the revised content in the chatbot window.

What worked well: In tests, publishers understood how the tool could be used as a writing partner, and were impressed with the way it restructured content with headings, bullet points and calls to action and hyperlinks.

What needed improvement: When faced with the empty chatbot interface, some publishers weren’t sure where to start, and they didn’t notice the three modes to work on content. Some were also unsure of the sources the chatbot was using for its revised content and skeptical that the revised content contained hallucinogenic content. They would have appreciated tracked changes to be able to pinpoint what had changed and found the long thin sidebar chat interface awkward to review the updated text. The chatbot was also limited to reviewing body text content, whereas publishers needed it to review content in other page components used in Drupal.

Read more about what we found developing and testing the ELM-powered content design chatbot:

Initial insights from UX testing our Drupal AI content assistant tool

Tool 3: QuillMark v1 and v2 – some AI, clusters errors with correction suggestions

QuillMark was an AI-enhanced tool which worked in Drupal to check content against the University’s Editorial Style Guide. Shlok Gupta built and tested two iterations of Quillmark during his 2026 summer placement as AI and UX Innovation Intern.

What it does and how it works: QuillMark sits in a side panel of the Drupal editorial interface and scans content on the page in two stages. The first stage uses code-based pattern matching (without AI) to catch straightforward errors. The second stage brings in AI to find deeper issues (such as passive instead of active voice) and to suggest fixes. Findings from both stages are displayed in the side panel – each finding describes the problem, links to the relevant rule in the style guide and offers an ‘Apply fix’ button (which can be reverted). Findings are grouped by category, and this panel also includes an indicator of the environmental impact and cost of the scan.

What worked well: In tests, publishers understood that the tool was there to help them correct content on the page, they liked the environmental and cost indicator, the suggested fixes and the links to the style guide reassured them that the tool was applying University-specific rules.

What needed improvement: Publishers reported feeling overwhelmed by the number of findings on a single page and they wanted a way to deal with related findings and fixes in bulk, to avoid going through them one-by-one. Related to this, they wanted

Read more about what we found developing and testing the QuillMark tool:

QuillMark, iterated. How user research helped us evolve an AI-enhanced Drupal style guide assistant

Tool 4: Drupal AI Content Review – full AI, with a plan provided to improve content

As part of the Drupal AI Initiative, I’ve contributed to shaping the self-explanatory Drupal AI Content Review module. This module plugs into a Drupal site, references content rules and good practice from context items in Drupal Context Control Center (within the same site) and uses the configured AI provider to review site content

What it does and how it works: The feature reads the page content and checks it against criteria set by the site owner, such as tone and voice guidelines, inclusive language rules and target readability levels. These rules are stored in the Drupal Context Control Center, along with examples of good and bad content. The review gives the page a score for each criterion and recommends fixes to improve it. Accepted recommendations become an improvement plan, which is applied in the editorial interface. Re-reviewing the page shows the updated scores, with the option to keep making improvements. Over time, the rules can be refined by adding more examples of good and bad content to the Context Control Center.

Read more about Drupal AI Content Review on Drupal.org

Read more about the Drupal Context Control Center on Drupal.org

View a demonstration of AI Content Review in a mocked-up university website as part of the Drupal AI demo on the Drupal Forge platform

What worked well:  In tests of this module within the AI demo, people liked seeing the red, amber and green indicators against page content for an easy visual highlighting areas to be worked on, and they liked being able to select a checklist of recommended improvements to apply to improve their content.

What needs improvement: The screens explaining the recommended improvements were difficult to scan read, and it was also difficult to compare the original text and the text with the recommended improvements side-by-side (despite colour shading to denote which was which). The stage where the recommendations were turned into an improvement plan felt like an unnecessary extra step, it would have been better to have implemented the recommendations directly. Also, it was presumed that implementing the plan would have corrected all errors resulting in a score of 100%, without the need for further work and re-review. Finally, it wasn’t immediately clear how to use the Drupal Context Control Center and the AI Content Review together.

When designing AI-enhanced tools, consider three AI design maxims

Taking on board variations in blending human effort and automated operations, there are three approaches to designing AI features and AI-assisted workflows worth considering. These are defined below, with ideas for how they may apply to content improvement.

1.      Human-in-the-loop

In this set-up, humans typically share the task-load with AI – actively working alongside an automated operator to supervise or influence actions, and to approve AI decisions before they happen (ensuring AI outputs are not released without the green-light from a person).

Human-in-the-loop tends to be adopted when:

  • there is a need for human judgement to get something correct
  • the consequences of an error could be high-profile or damaging
  • trust in an automated tool is still being built, and the boundaries of its capabilities are still being realised
  • the goal is for the system to facilitate shared learning between the person and the automation

For content improvement, human-in-the-loop is appropriate in these scenarios:

  • ensuring correctness of important factual data – for example, prices, dates, contact details, terms and conditions
  • checking the tone of sentences in line with inclusive language guidance
  • verifying accuracy of high-stakes published content such as legal information, policy wording or written instructional content
  • rewriting complex topics in plainer language
  • writing meta descriptions or page summaries to be accessed by search mechanisms
  • translating content into other languages

2.      Human-on-the-loop

These systems involve the AI or automator acting on its own, with the human reviewing and spot-checking at intervals, monitoring output quality over time, and intervening to correct failures periodically, where required.

Human-on-the-loop tends to be adopted when:

  • there is a high volume of low-risk tasks to be completed, which would be tedious for humans to do themselves
  • consequences of errors are minimal
  • there’s a need for tasks to be completed quickly, and including human-input at each task would be too time-consuming
  • consistency is required across tasks, and there’s a risk of human error introducing variability

For content improvement, human-on-the-loop is appropriate in these scenarios:

  • fixing straightforward style rule violations such as correcting spelling errors
  • categorising and tagging text content (for example, to facilitate its discovery in search)
  • scanning content for readability and accessibility, to flag or report areas to be addressed

3.      Human-out-of-the-loop

In this arrangement, the human sets up the AI to act autonomously, and leaves it to proceed, with no routine review.

Human-out-of-the-loop tends to be adopted when:

  • there are very low-risk, behind-the-scenes tasks to be completed where errors have little or no consequence and can be fully reversed

For content improvement, human-out-of-the-loop is appropriate in these scenarios:

  • autocorrecting typing errors
  • detecting content duplication
  • auto-optimising media content to defined parameters

Choice, pacing and transparency are constant design requirements

Testing four different tools has showed that options always need to be available, whatever balance of human and AI the tool includes. People approach AI differently based on preferences and past experiences. Some love nothing more than a good grappling of a sticky sentence, some just want an agent to do the work for them, and many sit somewhere in between, happy to have some AI help as long as they have the final say.

Alongside humans in, on and out of the loop, it’s important to remember the fourth option: human only, where people can choose to do their content unaided, using the methods they relied on before AI came along. AI shouldn’t be forced on anyone, so all tools need to come with a ‘no thanks to AI’ option.

AI is a fast-evolving and non-deterministic technology, so at any point in time it may work differently to the way it did before.  Responding to challenge from a design perspective, it’s important to factor in pacing. People need to be taken through how a tool works, and the options available. They need time and space to experiment and try it out, so they can learn for themselves how it can work for them. Pacing not only matters in the way tools are introduced, but also in the way their outputs are presented, to avoid the overwhelm that comes when AI does the heavy lifting all at once, and so people know what changed and how, and they have a way to accept, decline or edit what it produced.

If people don’t trust an AI tool, they won’t use it. Earning trust requires transparency, explainability, relatability and reliability – so AI tools need to be upfront about what they can and can’t do, with clear, intuitive interfaces and labels. Reliability will always be hard to promise given AI is probabilistic, so instead of accuracy guarantees which may fall short, a better approach is to design for experimentation, so people can find their feet and make their own judgements.

Designing for humans and AI together – metadata, markdown and MCPs

Looking at the broader digital landscape, the challenge widens from designing tools that help humans make content to designing websites with content ready for both humans and agents to use.

In co-browsing, people are increasingly arriving at a website with an agent alongside them, handing off some tasks while keeping control of others and wanting to see what their agent is doing. That means firstly deciding which tasks belong to humans and which one to AI, and secondly designing for each. Humans need intuitive interfaces. Agents need data they can read and act on without ambiguity:

  • metadata, such as schema markup that tells an agent what a page is about, who it’s for and how it connects to other content
  • markdown versions of pages and llms.txt files, which give agents clean, structured text without layout and navigation getting in the way
  • MCPs (Model Context Protocol servers), which let sites expose what they can do as well as what they say, from simple actions declared directly in HTML to more complex ones written in JavaScript – in preparation for use by the emerging WebMCP browser standard.

Labels matter for humans and agents alike, because words are becoming a currency that machines read as well as people. Alignment on terminology facilitates the creation of a single source of truth, to prevent the human experience from drifting from the agentic experience. On another level, humans need a way to consistently communicate with AI – to give AI the rules and instruct it and to train it with new insight. ‘Rosetta stone’ mechanisms like the Drupal Context Control Center will play an important part in designing for human and AI interaction and collaboration and I am excited to keep working and researching in this area to address these evolving design challenges.

 

Meet *sshole, the vulnerability that lets hackers SSH into Linux devices

5 November 2026 at 23:09

Devices running some configurations of Alpine Linux, and possibly other distributions, are affected by a decade-old vulnerability that allows attackers to log into devices with no password.

The vulnerability exists in the interaction between OpenSSH, the code library implementing SSH connections, and musl, a lightweight alternative to the libc library that, unlike most other Linux distributions, is used in Alpine. Further, OpenSSH using musl (pronounced muscle) must not use PAM (pluggable authentication modules), a framework that handles user authentication and account-access checks. Alpine is a lightweight, widely used Linux distribution. Other platforms may be affected if they use the same configurations.

One connection, works every time, needs no retries

There are two other conditions necessary for successful exploitation. First, a system must have at least one user account that’s accessible using a password that is hashed using the SHA256 or SHA512 functions. Second, the target system account must be configured to be passwordless, by way of specifying a "*" in the password field in /etc/shadow, the Linux file where password hashes are stored. Passwordless accounts are commonly used for accounts that use certificate-based authentication. This setting is common for certain types of accounts.

Read full article

Comments

© Getty Images | Sergey Balakhnichev

Show me your sources! What students make of content provenance data, AI signifiers and sparkles

5 November 2026 at 16:01

The line between human-made and AI-generated content is blurring fast. I added a disclosure indicator to an AI-powered search tool and tested it with students, which taught me about perceptions of AI-influenced content and what signals authenticity. I reflected on the need for a shared language around provenance and disclosure.

Estimations of the proportion of AI-generated content on the web vary and are becoming progressively difficult to measure. New legislation advocates for disclosure of AI use, but the nuances of communicating how AI has been used within a feature, and detailing the finer points of the provenance of AI-generated content both remain a challenge.

Earlier in 2026, I took part in a study to design a C2PA provenance indicator into a prototype AI searchbot. I revisited my designs to test them with students, to assess if this authenticity data made sense and to understand its impact on students’ potential trust of the AI searchbot. In this blog post, I describe what I tested and what I learned, and make broader considerations of designing with provenance data, the impact of AI legislation and what makes people trust AI features.

People’s trust in technology depends on explicit and implicit factors

The ISO 9241-210 standard for UX defines user experiences as ‘a person’s perceptions and responses that result from the use of anticipated use of a product, system or service’, which sums up the influence trust can have on the way a person experiences a technology.

I was interested to explore more about the relationships between human trust and AI, so I read a selection of papers on the topic and extrapolated four factors that commonly affect how people trust AI technologies:

  1. Transparency (surface and presumed credibility)
  2. Reliability (earned and reputed credibility, how consistently it works and how dependable it is)
  3. Explainability (how clear the purpose of the AI is and how clear it is how it works)
  4. Relatability (how well the AI supports the person’s interests, how easily they can use it and how it resonates with them)

When it comes to designing AI features people trust, and communicating how AI has been used within those features, it’s important to try and convey each of these factors in ways that make sense to the user in context. In other words, striking a delicate balance of providing sufficient trust indicators to allow people to make reasoned judgements, without going overboard and running the risk of confusion or skepticism.

The EU AI Act has set out obligations to disclose AI usage

From an ethical perspective, advising people that they’re using an AI feature has always been the right thing to do, in order to foster a sense of user trust. Legislation published in August 2026 made the requirement to disclose AI usage more explicit and provided more detail. Article 50 of the EU AI Act details Transparency Obligations for Providers and Deployers of Certain AI systems and includes recitals which cover areas including the following:

  • Designing AI systems to ensure users know they are talking to AI
  • Marking content from AI systems (text, images, videos, audio) so it is detectable as such
  • Informing people of AI systems that include emotion recognition or biometric categorisation
  • Disclosing deepfakes (audio/video/image content that has been manipulated as well as public-interest text, unless human-reviewed with editorial insight) as AI-made
  • Clarity, timing and accessibility of AI disclosures – to be provided at the first interaction or exposure and to be clear and accessible.

With this legislation now in place, it’s anticipated that a growing number of ways to disclose AI usage will emerge, making AI disclosure as mainstream as AI features.

I adopted the C2PA digital content provenance standard into an AI searchbot prototype

When it comes to icons that disclose AI usage, sparkles, neurons, and robots are all widely used, but they only signify that AI is present or available, they don’t provide any detail of how it has been used or how it has shaped content. C2PA is an established provenance standard which has been designed to convey progressive levels of content provenance data. I incorporated C2PA to disclose how AI was used to shape synthetic chatbot responses in a search feature and wrote about my process in an earlier blog post:

How can people trust AI-generated content? Designing provenance data into our prototype AI searchbot

I concluded this design work with a resolve to test my designs with users to understand the following:

  • if they cared about seeing provenance data about the AI searchbot response
  • if they grasped the concept of provenance data
  • if they understood what the C2PA Content Credentials icon signified
  • if the names for the different categories of data made sense to them

Drawing on my recent reading into trust factors, and taking into account the new EU AI disclosure guidance I also wanted to use my designs to understand more about how users make sense of AI features, and what affects their trust of them in context.

Testing revealed students’ responses to progressive levels of AI disclosure in the searchbot

In a simple test, I asked the student participants to imagine they were in a scenario where they had used the AI searchbot to find information from a website. I then showed them mock-up screens with the indicator in progressive levels of disclosure, going from the C2PA ‘CR’ logo, to ‘content credentials’, ‘About this response’, ‘Certification data’, ‘Digital source data’ and ‘Transformation processing data’. At each stage, I asked them to speak aloud to describe what they saw, what they thought it meant, and how it resonated with them.

Screenshot showing the AI searchbot interface showing all the provenance data available

Screenshot showing the AI searchbot interface with progressive levels of provenance data on display

The C2PA icon was unfamiliar but content credentials made more sense

Students’ first exposure to the provenance data was as the C2PA ‘cr’ icon which was displayed at the opening interface of the searchbot (when the searchbot was ready to receive a user query). On its own, the icon was pretty meaningless to them. One felt it could be a watermark, others thought it was a button to make the chat window bigger, others said they would Google ‘cr’ to find out what it was. The next level of disclosure was a signifier that read ‘content credentials’, which appeared once the searchbot had received a query and produced a response. Students found this indicator more meaningful – they felt it was a way to verify where the response came from, and said they would be inclined to press it to find out more.

The level 1 disclosure ‘About this response’ was too vague to be useful

When asked what they thought they would find in the section ‘About this response’, students were largely unsure. Some thought it would contain a hallucination warning, others thought it would contain sources. When they read the generic descriptor about the C2PA provenance data, which explains that the response was AI generated and had content credentials and assertions to demonstrate authencity, they felt it was too vague to be useful to them, and didn’t feel it was telling them anything new. They were unfamiliar with ‘content credentials’ as a term and by the language, they reasoned that this message was aimed at a legal team rather than someone reading the output of the searchbot.

‘Certification data’ wasn’t a term that resonated with student participants

Reading the label ‘certification data’ students had mixed ideas of what this section would contain. Some felt it would reveal intellectual property details, some thought it would show licensing agreements relating to data entered in the searchbot, and others thought it would explain how the searchbot handled data. There was a further expectation that this section would contain the sources behind the searchbot response.

When they expanded this section to see the identity data (name of the organisation certifying the content) and the associated timestamp of when the content was certified, they were unclear what was being certified (the output of the searchbot or the AI model), and how they would use this information. Some reasoned that the responses from the AI searchbot were stored in a database and that this certification data could help keep track of a bank of these responses.

‘Digital source data’ made more sense to them

Of all the data categories displayed, ‘Digital source data’ was the one students gravitated towards. This is where they assumed they would find the links to the sources used to create the AI searchbot response, and their assumptions were correct. For many students, seeing the links to the sources proved the authenticity of the AI content more strongly than any other sections of the data they had seen. As well as the source links, this section included the C2PA Actions assertion (which recorded the stages used to create the digital content (or asset) including the AI model used). Students recognised the AI model but questioned the terminology ‘Actions assertion’, thinking it would be more straightforward to just list the AI model used.

In the ‘Transformation processing data’, detail of the AI prompts was of particular interest

Preconceptions of what they would find in the ‘Transformation processing data’ section varied from a logical set of steps to show how the responses were formed from source data, to details of how data inputs would be used to train AI models, to sustainability data showing energy expenditure in the formation of the AI searchbot responses. When they saw information labelled ‘Search mechanisms’ which detailed how embeddings were created and a vector database was used in semantic matching, most students felt this was too much technical detail. Some who were familiar with the process felt this section would be more appropriately labelled as a technical stack, rather than search mechanisms. The ‘Transformation processing data’ section also contained the AI prompt, and most students responded positively to this, saying they felt it gave them a fuller picture, it helped them understand ‘the personification of the AI’ and made the process more transparent.

The effectiveness of my C2PA designs largely depended on students’ existing knowledge

Reviewing the findings together, I concluded that my designs partly succeeded in communicating details of how AI had formed the searchbot responses, but this depended on students’ perceptions and what they knew already, as well as what they wanted to know. Overall, my designs fell short when it came to instilling a sense of trust in the students, largely due to unfamiliarity with the C2PA terminology, the challenges of targeting implicit trust factors and the partic.

Students familiar with AI responded positively, but others wanted a non-AI option

The C2PA indicators focused on the provenance of the AI-generated searchbot responses, but for some students this was irrelevant as they wanted a choice to be able to not use the AI feature at all. Several students were skeptical and negatively pre-disposed to AI features based on their previous experiences and concerns about the environmental cost, and therefore upon seeing the sparkle icon realising the searchbot was AI-powered they were sought for a way to turn it off, or to make a choice about whether to use it or not. This reinforced the need to ensure AI features are a choice, and in the case of the AI searchbot example, an alternative way to achieve the same task is provided.

The C2PA terminology was off-putting to students

As they read the data in the different categories, students felt alienated by some of the C2PA language, particularly terms like ‘content credentials’, ‘provenance’ and ‘assertion’. When they were able to see contextual detail associated with these terms, most were able to fathom what the terms meant, but I concluded that including these terms in the designs and in the labels of the different data categories was giving students an extra unnecessary hurdle of jargon to overcome before they could reach an understanding of the data presented to them.

Some C2PA data was clear and useful, other data felt unnecessary

The four categories of data resonated differently with the students, and, based on their reactions, some of these data sources felt unnecessary to show data provenance.

Most students found the source links useful, and what they expected in the category labelled ‘Digital source data’. They also found the AI prompt useful, but they didn’t expect to find it in ‘Transformation processing data’. Almost all felt the notification that the response was AI-generated (in the ‘About this response’ section) was unnecessary. Other data points that students felt confused and nonplussed by included the ‘CR’ logo, the identity data, the certification data (including the timestamp), and the technical terms describing the response-generation process.

Some of the data students were expecting was missing

As they reviewed the different categories of data they were presented with, students commented on data they would have expected to see. This included: environmental impact data, information about how input data would be used to train AI models, and details of how the data was processed and held by the searchbot feature. While these data points largely fell out of the realm of content credentials, it was interesting to understand the types of data students looked for when making judgements about whether to use and trust this type of AI feature.

The C2PA designs targeted some trust factors but not others

Re-examining factors that affect trust highlighted that trust is heavily influenced by implicit factors or emotional cues which are specific to individuals. Targeting subjective trust factors such as relatability, (which depends on how well something supports a person’s interests and resonates with them) was very difficult to achieve without research to understand the nuances of the target audience. Some students were reassured by the mention of AI models involved in generating the content, but for others, this merely caused confusion.

Targeting explicit trust factors like transparency and explainability in displaying content provenance was more straightforward, but it meant striking a balance. Providing too much technical detail about the production process, although this was intended to build trust by being upfront, could end up causing confusion and therefore result in the opposite effect, as I observed in the student tests.

Conveying reliability remains a challenge when AI is involved. Since AI is probabilistic, its results are variable, and in the context of a feature like an AI searchbot, it was not possible to make assurances in the provenance data. Instead, I used the progressive disclosure levels to encourage exploration and a gradual building of understanding, to help people come to their own conclusion about whether to trust the AI-generated content. I saw this working in the student tests, as they made reliability judgements about the AI responses when they saw the source data revealed.

Provenance indicators should replace the sparkles and it’s time for a unified AI vocabulary

The C2PA standard is several years old, yet content provenance is still a relatively unfamiliar concept. With new AI legislation published and the advent of more formalised requirements to disclose AI usage and application, I predict more rhetoric and discussions around disclosure, authenticity and provenance, to evolve the language and terminology around these concepts and to make them more mainstream.

Those who consume AI-generated content want to know how it was made, and the sources it came from, and those who use AI to generate or shape the content they publish have an obligation to disclose how AI was used, to ensure transparency from both perspectives. When designing AI features, consistent labelling will play an growing part in conveying meaning. As people become more familiar with AI, they will rely on these labels more and more to make judgements and decisions about AI features and AI-influenced content.

This small study has re-emphasised the importance of choosing terms and wording labels carefully, to strike a balance between technical and non-technical and to provide just enough detail to resonate with audiences but not so much that it confuses them. It highlights the need for a unified vocabulary for AI, to effectively communicate about its usage and application. As AI usage progresses, I expect provenance indicators and associated design patterns to continue progressing, and I’m keen to keep a close eye, to keep iterating on ways to display provenance data. I look forward to seeing sparkles replaced by more meaningful signifiers of AI usage and disclosure.

QuillMark, iterated. How user research helped us evolve an AI-enhanced Drupal style guide assistant

2 November 2026 at 10:25

AI and UX Innovation Intern Shlok Gupta and I worked together to build and test Quillmark, an AI-powered Drupal content design tool that tackles the persistent problem of keeping content consistent with the University’s style guide. This post covers how we iterated from version 1 to 2.

Leading a UX Service, it’s critical to stay informed about the latest technologies, as these dictate user expectations and perceptions. I recognised the potential for AI to transform publisher experiences of using Drupal when Drupal AI experts Freely Give came to work with our team in January 2025. Since then, I’ve been committed to experimenting with AI application in content management, both through my involvement with the Drupal AI initiative and by supporting a succession of interns in my UX team at the University.

As a technology, AI is becoming increasingly mainstream. That said, its rapid rate of evolution and flux means adopting it consistently remains a challenge, as does designing AI features that are centred around user needs and expectations. AI features can be built and released in a matter of days, but can just as quickly become superseded and obsolete as technologies and capabilities change, and user expectations and perceptions of AI features can vary widely depending on individual experiences, trust factors and preferences. Continuous research is necessary when developing any user-centred software, but it’s particularly important when designing user-centred AI features, which I wrote about in a related blog post:

Stop chasing, keep researching: Why continuous contextual learning is the only way to build useful AI features

In the spirit of continuous research, the students who occupy the AI and UX Innovation Intern role in my UX team spend as much time testing as they do building. Shlok Gupta joined the team from May – August 2026, in which time he prototyped and tested two versions of an AI-enhanced style guide checker tool in Drupal. Shlok described his process to build and test Quillmark v1 in two blog posts, and also produced a video to show it in action:

Building QuillMark: testing a Drupal style-guide assistant with web publishers

Quillmark: the technical details behind my Drupal style-guide assistant

View a video of Quillmark v1 on MediaHopper

In this post, I continue the story, to explain how version 2 was built based on feedback from version 1, and what we learned testing version 2 with publishers.

QuillMark v1 had a non-AI stage and an AI stage and the ability to flag and fix errors

Shlok designed QuillMark v1 to have two stages as a way of making most economical use of AI time and tokens. Stage 1 used basic pattern-matching and code-based rules to catch straightforward style-guide errors without AI, and stage 2 then brought in AI to find and recommend fixes for deeper issues. This meant AI resource wasn’t spent identifying and resolving simpler problems that didn’t need it. The screenshots indicate how v1 worked.

Screenshot showing Quillmark v1 (in the right-hand panel of a Drupal site) ready to review content

Screenshot showing Quillmark v1 (in the right-hand panel of a Drupal site) ready to review content

From right-left, four screenshots showing detail of the QuillMark guide in the right-hand panel before a scan, the panel expanded to show the guide, results of a stage 1 scan and detail of selected stage 1 findings

From left to right, detail of QuillMark in the right-hand panel – before a scan, expanded to show the guide, results of a stage 1 scan and detail of selected stage 1 findings

Three screenshots of QuillMark, showing the panel ahead of running the stage 2 scan, combined results of the stage 1 and stage 2 scans and detail of selected stage 1 and stage 2 findings alongside each other

From left to right: the panel ahead of running the stage 2 scan, combined results of the stage 1 and stage 2 scans and detail of some stage 1 and stage 2 findings alongside each other

QuillMark screenshot showing how a finding from a stage 2 scan mapped to a sentence in the passive voice highlighted in the editorial interface

QuillMark screenshot showing how a finding from a stage 2 scan mapped to a sentence in the passive voice highlighted in the editorial interface

QuillMark screenshot showing the highlighted sentence changed to active voice - which resulted from pressing the ‘Apply fix’ button on the finding

QuillMark screenshot showing the highlighted sentence changed to active voice – which resulted from pressing the ‘Apply fix’ button on the finding

Tests revealed the need to simplify QuillMark v1

In the tests of QuillMark v1, participants were asked to read a guide about how the tool worked, use it to scan some pre-prepared content and then review the resulting findings and say how they would act upon them. The results indicated several areas for improvement.

All participants understood that QuillMark v1 was a tool to help them correct content errors. Despite being directed to read the guide upfront, however, some participants were unclear of the difference between stages 1 and 2.  Having run stage 1, participants were uncertain what stage 2 of the tool would do. Some identified the AI detail in the stage 2 labels and therefore realised that stage 2, unlike stage 1 used AI, but others thought stage 2 was the ‘repair’ or ‘fix’ stage to follow stage 1 as the diagnostic stage.

As they reviewed the different categories of finding in the right-hand panel, most participants said they felt the amount of information was overwhelming, and difficult to scan read. They especially found it difficult to interpret abstracted recommendations to fix errors, preferring to receive suggested fixes through the ‘Apply fix’ option. As a way to reduce the overwhelm, some participants said they would be inclined to go and fix several of the errors manually first, and then rescan, so that the tool only presented them with the errors they missed themselves.

Other observations from the test participants fell into two categories, lack of understanding of how Quillmark worked, and feedback on how they felt it could work better for them.

Participants were confused about how to use QuillMark and how it worked

Several aspects of participants’ behaviours indicated they weren’t sure how QuillMark worked. These were as follows:

  • There was some confusion over how to start QuillMark running. Participants did not immediately realise that the Stage 1 and Stage 2 buttons would start the tool. They looked for a button that said ‘Run’ or similar. When they worked out how to activate the different stages, they were unclear about what was happening in each.
  • Several participants raised questions about the cost and environmental impact of running the AI stage of the tool, saying this would affect whether they would choose to use it.
  • There was a lack of clarity from participants about whether QuillMark was using generic grammatical rules to flag errors and make recommendations or if it was using the specific University of Edinburgh style guide rules
  • Several participants did not initially recognise that QuillMark could suggest fixes as well as flagging errors.

Participants suggested ways to change QuillMark, to help it support publishing practices better

When they had got used to working with QuillMark, several participants suggested ways they felt it could work better. There were as follows:

  • A request to be able to apply bulk fixes to recurring errors, rather than addressing them one-by-one (for example, removing full stops in repeated headings or switching sets of times from the 24 hour clock to the 12 hour clock)
  • An ask from several participants to be able to preview fixes offered by the ‘Apply fix’ buttons before accepting them to change the text in the editorial interface (however, they soon realised they could switch between the ‘Apply fix’ and ‘Revert fix’ buttons to achieve this).

QuillMark v2 worked in the same way but the interface was simpler

Taking on board the feedback from the QuillMark v1 tests, Shlok made a version 2 which included several changes:

  • A single ‘Scan’ button to start both stages of the tool working, replacing the need for publishers to run stage 1 and stage 2 scans in sequence
  • Progress indicators that appeared once ‘Scan’ had been pressed, to communicate what was happening, and to affirm that the editorial style guide was being checked
  • Inclusion of an ‘Advanced settings’ panel giving users the option to decide whether to include deterministic error scanning and fixing and the use of AI to suggest replacements
  • A panel that estimated monetary cost and environmental impact of each scan resulting in the findings

View a short video demonstration of QuillMark v2 on Media Hopper

The screenshots indicate how v2 worked and show the differences between v1 and v2

QuillMark screenshot showing the tool in the right-hand panel ahead of a scan being run on a page of content titled ‘Research projects’

QuillMark screenshot showing the tool in the right-hand panel ahead of a scan being run on a page of content titled ‘Research projects’

Series of QuillMark screenshots, from left to right, showing the tool with the guide displayed, and the successive stages once ‘Scan’ has been pressed – reviewing, preparing, checking editorial style rules and then the notification that QuillMark has completed the scan.

QuillMark screenshots, from left to right, showing the tool with the guide displayed, and the successive stages once ‘Scan’ has been pressed – reviewing, preparing, checking editorial style rules and then the notification that QuillMark has completed the scan (showing that AI suggestions are included in the ‘Advanced settings’ pane

Tests showed v2 was better, but still had room for improvement

The testing protocol for QuillMark v2 remained the same as for v1, however, this time participants were asked to use the tool on three separate pages of University website content, to give them more practice of engaging with the tool to learn how it worked.

Participants found it easier to understand how QuillMark v2 worked

With the new blue ‘Scan’ button, participants were more easily able to get started with running QuillMark. Since it was running an AI and a non-AI stage QuillMark v2 took longer to produce findings than QuillMark v1, but the newly added progress indicators kept participants informed about what was happening.

The indicator with the data about environmental and monetary costs was noted by all participants, and some said this was welcome information to help them make responsible choices about AI use.

Participants were still directed to the guide, which some wanted to refer back to once they had got started with the tool, to remind them of how it worked.

There were fewer questions about the source of the rules powering Quillmark v2 than for v1, and several participants verified that the tool was using rules from the University editorial style guide by pressing the ‘Link to rule’ button on individual findings (which connected to the relevant page or section of the style guide).

Some still found the interface and display overwhelming

Although QuillMark’s interface had been simplified by the removal of stage 1 and 2 indicators, participants still commented it contained a lot of textual information and was difficult to scan. Some were unclear what the different labels in the findings meant (Errors vs Warnings vs Notes), and several found it easy to miss some of the tool’s functionality simply because there was too much to read through.

Participants were still uncertain about the ‘Apply fix’ button

As they worked through the individual findings, participants were able to recognise the need for corrections that had been highlighted, but some did not appreciate that QuillMark v2 offered a fix as well as flagging the error.

As they used QuillMark v2 to scan a page about research projects, the tool flagged an instance of poorly worded link text (‘Project Website’). The ‘Apply fix’ button contained a suggested improvement (‘Visit the Hillforts Atlas website’) but several participants did not select this, instead they manually addressed the error themselves, by checking the link destination and then writing appropriate link text. Those that did notice that ‘Apply fix’ had made a suggested improvement were happy to accept it and apply it.

Screenshot showing a QuillMark v2 finding flagging poorly written link text

Screenshot showing a QuillMark v2 finding flagging poorly written link text

Screenshot showing QuillMark v2 a fix to improve poorly written link text applied in the editorial interface

Screenshot showing QuillMark v2 a fix to improve poorly written link text applied in the editorial interface

They still wanted repeated findings to be consolidated, to be addressed together

Some categories of findings contained recurring instances of the same issue. Participants wanted these to be grouped or summarised instead of being listed individually, as they wanted to address all the findings on a particular issue together in one action (either dismissing them or applying suggested fixes), rather than going through them one-by-one. This problem was particularly prevalent on pages where the content followed a structural pattern, for example a series of headings all written in non-sentence case (with misuse of capital letters) or a labelling convention applied consistently to rows of a table (for example numerals in sequence).

Screenshot showing individual instances of an error flagged as separate findings in the QuillMark v2 interface

Screenshot showing individual instances of an error flagged as separate findings in the QuillMark v2 interface

There was concern over saving progress when working through lots of findings

In the tests, one of the pages scanned by Quillmark v2 generated 166 findings to be addressed. As participants worked through those in a particular category (for example ‘Links and calls to action’) they felt uncomfortable that they were unable to save as they went, seeking some reassurance that their work was being logged sequentially. They looked for a ‘Save’ button associated with each individual finding, and some wrongly assumed the ‘Dismiss’ button saved the change they had made (whereas in actual fact, this button removed the finding from the list to be addressed).

QuillMark was unable to reconcile multiple errors on the same content

In some instances, a piece of content contained multiple style guide errors, so it appeared in separate findings in separate categories. An example was ‘Prof Smith’s website’ used as a piece of link text. This error appeared in the ‘Spelling, wording and abbreviation’ category, flagged for the incorrect use of ‘Prof.’, but also in the ‘Links and calls to action’ category, flagged for unclear link text.

When participants encountered an error in one finding, they corrected it there, but then when the same piece of content was also flagged for another error in another category, Quillmark v2 had already noted that the content had been changed, and had no way of layering on another, different correction. In these instances, a warning flag disabled the ‘Go to field’ preventing participants from going to the incorrect content, therefore forcing them to try and find the location of the incorrect content themselves, which they found disorientating and tricky, especially in long pages of content.

Screenshot showing the blocker message that displayed when there were multiple errors on a single field of content

Screenshot showing the blocker message that displayed when there were multiple errors on a single field of content

Participants wanted QuillMark to fix heading levels and reposition inline links

Errors relating to content structure, such as incorrect heading hierarchies and inline links were flagged by Quillmark, but the tool was unable to suggest an automatic fix to apply. Several participants said they would have liked for an autocorrect functionality for these errors, since they found them difficult and fiddly to manage within the EdWeb2 editorial interface.

The next iteration of the tool will focus on one category of style rules: Links

Since the last round of tests on QuillMark v2, Shlok completed the internship, and was succeeded by Viktor Sharha in the role of AI and UX Innovation Intern, to continue the work on the Drupal style guide checker tool. Taking all the findings from the tests of QuillMark v1 and v2 together, I concluded that the most pressing problem to address was that of overwhelm.

When a page contains many errors or style guide violations, there is a dual design problem: Firstly how to detail each error, the root cause and the suggested fix, so that publishers understood what was wrong and how it can be corrected, and secondly to do this concisely, taking up the minimal space possible, to avoid publishers having a long scroll through multiple errors with the associated cognitive load.

Going forward, it made sense to focus on the first problem of presentation of individual findings first, and to do so at a site level (recognising that publishers may not do their checking on a page-by-page basis), before scaling this up to design for multiple errors. To maintain a tight remit, and to focus on the style guide violations which are highest priority to fix, we have decided to specifically look at links, to consider how the tool can spot instances of poor link text, how it can describe ways to improve these, and the options for applying automated fixes.

Using a survey to understand digital design tool usage across the University (as part of the Figma design component library project)

2 November 2026 at 08:24

This year, as part of the Figma component library project, we researched how colleagues across the University use digital design tools in their work. This post explores how we approached the research, from designing and distributing the survey through to analysing the responses and identifying emerging themes. 

In a previous blog post, intern Kaile Liu introduced the wider Figma project, and its aims and objectives: 

What I am working on as a Digital Developer Intern (Figma) 

Request access to the project brief for more details:

Figma project brief

We needed to understand how digital design work happens across the University 

To begin with, we needed to understand how staff across the University design, collaborate and deliver digital work. 

There are a wide range of tools, workflows and practices currently in use. Understanding these existing ways of working would help us explore where Figma fits within the wider digital landscape, rather than looking at Figma in isolation. It also supports the work we are doing to improve our Figma component design library.

To hear from colleagues across a wide range of roles and disciplines, we chose a survey as the main method for this research.

Five questions framed our research 

As well as understanding what tools people use, we wanted to find out how those tools support their work and where there may be opportunities to improve existing ways of working.  

Our research was underpinned by five key questions: 

  • What tools are people using day-to-day? 
  • How do those tools support their work? 
  • Where do people experience challenges or inefficiencies? 
  • How do teams collaborate when creating digital content and services? 
  • Where are there opportunities to provide better support, guidance and training? 

These questions helped us build a broader picture of digital working practices across the University. Additionally, working this way allowed us to look beyond any individual or singular tool.

Hearing from more than just traditional design roles was important 

Design work happens across many different roles at the University, including roles not traditionally associated with design or that do not have ‘design’ in the job title. For example, a communications officer creating digital content, a developer sketching a wireframe, a UX practitioner co-creating a prototype or a learning technologist building online resources may all be making design decisions as part of their work. 

This meant looking beyond traditional design roles and hearing from colleagues who use digital design tools in different ways.  

Initial conversations helped us shape the research 

Before designing the survey, we carried out an initial set of user interviews with staff from across the University. We also drew on existing University communities and communities of practice to understand the different roles involved in digital design work. These conversations gave us an early view of how colleagues use and collaborate through digital tools. They helped us identify the groups we wanted to hear from and shape the questions we wanted to ask in the survey.

Adapting our survey to broaden our understanding of ways of working

Based on these interviews, we recognised that a single set of questions would not capture the differences between roles particularly well. Instead, we adapted the survey so that respondents would answer shared questions and then be filtered to questions relevant to their role and ways of working.

This, in essence, would give us a more consistent set of responses while still allowing us to explore some of the differences between roles.

Role categories allowed us to tailor the survey 

We created a filter with seven options: 

  • Marketing and Communications 
  • UX and Human-centred Design 
  • Graphic and UI Design 
  • Developer 
  • Project or product manager 
  • Research 
  • Other (for participants who did not feel represented by the other groups) 

Participants selected the options that best reflected their work, determining which role-specific questions they were shown. They also provided their job title.

The survey combined common and role-specific questions 

The survey consisted of three main sections. The questions included a mixture of multiple-choice and open-ended responses. This allowed us to identify broader patterns while also giving colleagues opportunities to explain their experiences in more detail. 

The opening section included five common questions about participants’ roles, the types of digital design work they do and the tools they use, including tools for collaboration, diagramming and presentations. 

The middle section included around four to six role-specific questions, depending on the participant’s selected group. These explored aspects of digital working relevant to each group. For example, marketing and communications colleagues were asked about the tools they use when designing marketing materials, while developers were asked about the tools and approaches they use during the design phase of projects. 

The closing section included 15 common questions focused on colleagues’ experiences and expectations of digital design tools, including Figma. We asked which tools colleagues would be likely to use, whether they experienced challenges with their current tools and how their work might be affected if they lost access to Figma. 

We wanted the survey to reach as many colleagues as possible

We distributed the survey primarily through existing Teams channels and University communities, which helped us reach a wide range of roles. These included groups focused on marketing and communications, human-centred design and digital development, as well as distribution via heads of IT. 

The survey received 55 responses  

We heard from 55 staff across a range of roles. Based on the categories participants selected when completing the survey, these were as follows: 

  • Marketing and Communications: 20 
  • Developers: 10 
  • UX and Human-Centred Design: 6 
  • Graphic and UI Design: 3 
  • Project or product manager: 2 
  • Other: 14 

Although seven categories were available in the survey, no participants selected ‘Research’ as their primary category, so it is not shown in the breakdown. 

The ‘Other’ category included colleagues working in areas such as product and project management, learning technology and academic support. 

We refined the groups when analysing the responses 

The survey categories gave us a useful starting point, but participants did not always recognise themselves within the roles specified (even when their job title directly reflected one of the options). For example, a participant selected themselves as ‘Other’, but their job title indicated that their work was within graphic design.

In order to evaluate the responses effectively, we revisited participants’ selected categories alongside their job titles and descriptions of their work.

This helped us six create groups that gave us a more useful basis for comparing responses:

  • Developers and technical specialists 
  • UX practitioners 
  • UI and graphic designers 
  • Marketing and communications staff 
  • Product and project managers 
  • Learning technology and academic support staff 

Some of these groups needed to be created on the back of this, as we had not identified those specific roles. For example, Learning Technologist was not an option for participants to select, but emerged as a useful category based on the number of respondents who had this as their job title. 

After this assessment, we were in a better place to begin analysis, as these groups gave us a more useful basis for comparing responses while still reflecting the range of roles represented.

Analysing the survey results required two approaches 

The survey produced both quantitative and qualitative responses, and we used different approaches depending on the type of question and response. 

For the role-specific questions, we used FigJam (Figma’s whiteboard for online collaboration) to review and compare responses across the different groups. This included both quantitative and qualitative responses, allowing us to look at the detail within each role as well as compare responses across the wider dataset. We used Power BI, a data visualisation platform, to explore the common quantitative questions, which gave us a consistent set of responses across all participants. 

We used FigJam to explore the role-specific responses 

We created a large collaborative FigJam board to organise the responses. FigJam supported discussion within the project team, allowing us to work in tandem and analyse the data as a group (in person and asynchronously).

We read through responses from each group, compared them across different roles, and identified recurring patterns and themes. FigJam also allowed us to consider the quantitative responses alongside the more detailed qualitative answers, giving us a fuller picture of ways of working. 

Screenshot of three frames on FigJam full of stickies. There is a blue section, titled Developers, an orange section titled Marketing and Communications, and a green section titled Graphic visual and UI design.

Section of our analysis on the FigJam board

Power BI helped us explore the common quantitative responses 

Power BI allowed us to visualise responses across the opening and closing questions. We wanted to do this as they were common questions asked of all participants. Power BI allowed us to bring our data to life by presenting the data in a more visual way, highlighting the common patterns and themes more easily.

Screenshot of Power BI visualisations. There are seven individual bar graphs of different colours, alongside a larger bar graph with these seven combined. The large bar graph has a right skewed narrow tail. There are also two sets of pie charts, each consistening of seven smaller charts and one larger combined. The data itself is not visible.

Section of our Power BI visualisations for the project.

Grouping responses helped us identify recurring themes 

The open-ended questions in the role specific sections had more detailed responses. This required us to compare responses across the different role groups and group similar comments together to identify recurring themes. 

As we worked through the responses, we also noted areas where a follow-up conversation with a participant could provide more context.

We also captured key quotations that illustrated what participants were telling us in their own words. These will be useful for when we playback findings to colleagues and complete a written report. 

The research will inform the next stage of the project 

The research highlighted both the diversity of digital working practices across the University and common themes across different roles. 

The next stage will bring these findings together into a report. It will highlight where Figma currently supports existing workflows and where its integration will provide more consistent, unified delivery of digital practices across the University.

LibrePods: AirPods Features for Android and Linux

Liberating AirPods Beyond Apple’s Ecosystem

If you’ve ever paired a pair of AirPods with a non-Apple phone, you’ll know the experience can be… basic. They play audio just fine, but those clever features Apple shows off aren’t available when you’re on Android or Linux. Until now. LibrePods is a free, open-source project on GitHub which is reshaping what’s possible by unlocking the hidden capabilities of Apple’s wireless buds on other platforms. 

Created by a young developer with a knack for reverse-engineering proprietary tech, LibrePods is rapidly gaining traction in developer circles and among tech-savvy listeners craving more from their hardware. Instead of settling for ordinary Bluetooth audio, this project gives Android and Linux users a taste of what has long been exclusive to iPhones, iPads and Macs. 

Why LibrePods Matters (Even If You’re Deep in Apple Land)

On Apple devices, AirPods benefit from tight integration with system software — everything from noise cancellation switching to automatic ear detection is baked into iOS and macOS. It’s one of the reasons AirPods feel so polished and magical. On Android or Linux? Not so much. Outside the Apple ecosystem, most devices fall back to a generic Bluetooth profile, leaving most advanced features dormant. 

LibrePods changes that by effectively speaking the same language AirPods use with Apple products. Instead of accepting the rudimentary experience most devices offer, LibrePods lets a non-Apple system interact with AirPods in a much deeper way, bringing functionality that was never officially supported before. This isn’t just a niche enthusiast novelty — it’s a meaningful step toward breaking the walls built around modern hardware. 

Behind the Scenes: A Brief Look at How It Works

At its core, LibrePods doesn’t reinvent the wheel — it deciphers it. AirPods use a proprietary communication protocol to share rich data with Apple devices. LibrePods analyses and implements enough of that protocol so an Android or Linux host can mimic an Apple device, coaxing the buds into sharing advanced status info and accepting commands that would otherwise be ignored. 

The result is an experience that feels much more like native integration than a hacky workaround. Granted, there are technical hurdles: on Android, full support currently depends on specific system frameworks (such as Xposed) or root access due to limitations in how Android’s Bluetooth stack exposes device capabilities. But even with those constraints, the gains are undeniable. 

What You Actually Get — Real World Impact

Unlike typical Bluetooth audio apps that simply display a battery percentage, LibrePods gives you context and control. Users report that once set up, their device responds as if it were part of Apple’s ecosystem. Features that were previously sealed away — from adaptive audio modes to clever gesture detection — become available. Reviews and community reactions highlight:

  • Automatic behaviour that feels intuitive: Music pauses when you take an earbud out, reconnects smoothly, and transitions audio sensibly without manual toggles.

  • Smarter audio control: Noise modes and environmental awareness kick in from your device’s UI rather than relying on the buds to guess what you want.

  • Gesture support: Unique input methods like nodding to answer a call — once only available on Apple hardware — start working elsewhere.

  • Battery and connection insights: No more guessing how much life is left in your buds.

  • Customisation potential: Developers can experiment with settings and tweaks that Apple doesn’t expose even on its own platform. 

These improvements make AirPods a far more capable companion on non-Apple devices — and for listeners who switch between Android and Linux boxes throughout the day, that’s huge.

Open Source, Community-Driven, and Evolving Fast

LibrePods isn’t a polished consumer app from a multinational tech giant — it’s the product of community effort and open collaboration. That means anyone can explore the code, learn from it, or contribute improvements. It’s licensed under GPL-3.0, ensuring that future innovation builds on a free and transparent foundation.

This community aspect is a big part of why LibrePods is exciting. Contributors from around the world are refining compatibility, expanding platform support, and pushing the project forward with a brand new UI. Compared to many proprietary audio tools, this kind of collective refinement often leads to better long-term outcomes, particularly for under-served platforms like Linux.

LibrePods new UI for Linux

The Apple Geek Take — Why You Should Care

At The Apple Geek, we celebrate how great hardware and software together can elevate everyday tech. But we also recognise when thoughtful innovation opens doors beyond corporate ecosystems. LibrePods isn’t about tearing down Apple’s achievements it’s about extending choice and agency for users who don’t want to be boxed in. It’s a reminder that, with enough ingenuity, even the most tightly controlled tech can be explored and expanded. 

For Apple aficionados who dabble outside the orchard, or for anyone curious about how deep open source can go, LibrePods is a fascinating project worth watching. Its success doesn’t just bring features to new platforms it inspires a broader conversation about ownership, interoperability, and the future of connected audio devices.

Want to Try It Yourself?

If you’re technically inclined and comfortable with community-built software, check out the LibrePods repository on GitHub for installation instructions and contribution guidelines. The project is evolving quickly, and support for different devices and configurations continues to improve. 

Testing with users informed the Institute for Academic Development’s content migration

28 October 2026 at 16:27

The User Experience Service worked with colleagues from the Institute for Academic Development to test their content with users. Results from the testing supported content decisions in migration work that these colleagues carried out later in the summer.

This is part two of a two-part series. Part one is available here:

How we helped the Institute for Academic Development to establish user needs for their website

We had established some user needs but wanted to learn more

In two online sessions, we had worked with Institute for Academic Development (IAD) staff to establish a shared understanding of what users needed from their service.

We now wanted to find out about the experience of students who use the IAD website. Specifically, we were interested in two audience groups:

  • Postgraduate research (PGR) students
  • Students from all stages who might need academic skills support

Along with tests on the existing site, we also wanted to try out some new layout ideas and learn about what types of content these audiences would find most useful.

An in-person event gave us an opportunity to hear from PGR students

We knew that presenting information about workshops would be a priority for the new sites and we wanted to know the best way to present this. To inform the design, we needed to speak to people who might use the website to look for these workshops.

Fortunately, the perfect opportunity was just coming up. On 17 June, a large group of research students would be attending PhD Horizons, an all-day careers event at McEwan Hall. We planned two simple research tasks that we could carry out on the day. Emma Horrell and I attended the event with UX team interns Hannah Watson and Shlok Gupta. This was a great opportunity for Hannah and Shlok to gain hands-on experience of in-person UX research.

Usability testing helped us to learn about the existing site

The first task was a quickfire usability test asking PhD students to use the IAD website. For the testing, we handed PhD students an iPad and presented them with two scenarios:

  • Imagine your viva is coming up. How would you find a workshop to help you prepare for this?
  • You’re going to a conference and want to get better at presenting. What can you find on this site that could help you to do this?

Paper prototyping gave us insight into alternative designs

For the second task, we presented four paper prototypes of potential homepages for postgraduate researchers. PhD students compared the prototypes and talked about which areas of the site they would find most useful. This gave us an indication of how closely these homepages aligned with their needs, and it also provided insight into how the language used in the prototypes might be understood.

Clipboards and sticky dots on a table.

We used paper prototypes of homepages to test ideas with students.

A piece of A4 paper with a rough mockup of a webpage. Page is titled Support for postgraduate researchers. There are 4 boxes with titles Explore our workshops and courses, Plan your PhD journey, Browse our writing support courses, and Not sure what training you need? Launch the Development Needs Analysis tool. There are sticky dots on the page.

Students used sticky dots to indicate which areas of the paper prototype would be most useful to them.

What we learned from the usability testing and paper prototyping

In the end, we heard from about 20 PhD students who told us how they might search for workshops on the IAD website. From these conversations, we learned how these students responded to items presented on the live site and what they thought of some potential alternative ideas.

In the usability testing activity, we learned which ways of presenting workshops were perceived as being more useful than others. For example, most participants did not use the embedded PDF brochure, despite it being prominently located on the PGR landing page. Instead, we saw users gravitate to webpages showing workshops grouped by theme, or as an A to Z list.

Screenshot of the Postgraduate Researchers page on the Institute for Academic Development website. An embedded brochure is at the top of the page.

Users did not interact with the embedded PDF brochure.

Observations like this gave us a steer on which categories and methods of presenting workshops would be most useful to PGR students in future designs of this content.

In the homepage paper prototype activity, one of our mock-ups included an option to complete a Development Needs Analysis. This is a form that new PGR students can complete to assess their learning needs. But when we presented the text ‘Development Needs Analysis’ in our prototype homepages, most students could not guess what this was. That seemed like something that could be addressed in the new website.

We shared the findings with colleagues tasked with developing the new site for postgraduate researchers.

We ran usability tests on the academic skills content

Alongside this work, we were helping IAD staff to develop content for a new academic skills website. We agreed that a short round of usability testing on the existing IAD site would help us to get a better understanding of what it’s like to use it. We wrote a script for a 15-minute test and recruited four students working on summer internships at the University. A week later, we were on a Teams call with those students, watching them use the site.

The tasks we set in the usability tests were as follows:

  • You’re an undergraduate student at the University of Edinburgh. You’ve just started a new course. You’ve got your reading list, and you’re feeling overwhelmed by it. Your student advisor has said to book a one-to-one meeting with the Institute for Academic Development (IAD). You land on the IAD website homepage. Can you find out how to book a one-to-one?
  • You’re a postgraduate taught student. You’ve seen a poster advertising dissertation workshops. You arrive at the IAD homepage. Can you find a workshop that will help you with writing your dissertation?
  • You’ve just completed your first year of your History degree. Your exams didn’t go so well and you have a resit coming up in August. Your friend said there’s some advice on preparing for exams on the IAD site. Starting from the homepage, can you show me what advice you can find?

What we learned from testing the academic skills content

None of the participants clicked on the Study Hub resources. The Study Hub contains valuable content that could help students with the problems we presented in the test. But none of the participants followed links to the Study Hub, despite these links being present on several of the pages that participants used.

The Exam Bootcamp page did not lead participants to other exam content. When looking for support for exams, participants scanned the homepage for any mention of exams. This led them a page about Exam Bootcamp, a resource available on the Learn VLE. Participants seemed pleased to find this but didn’t find any of the other available resources or workshops about exams.

Participants did not seem phased by the amount of dissertation workshops on offer. When tasked with finding a workshop to help with dissertations, participants reached a page that listed 17 different workshops on the topic of dissertations. We had anticipated that that might be a problem. But none of the participants seemed worried about how they would choose a workshop to attend. They scanned through the list and picked those that looked like they might be relevant.

The new sites are now live

The teams working on the new sites took the findings from the strategy sessions and the user research and fed this into the development of four new sites. The new sites went live in July, using layout, wording and information architecture choices that reflect some of the insights gained from the content review work.

For example, the Postgraduate Researcher and Career Development site puts PGR workshops in a prominent location on the homepage. Users can browse all workshops, or view them grouped by theme. Next to that, a card shows development support options for PGR students at different stages of their studies (‘Starting out’, ‘Keeping on track’ and ‘Final stage’), echoing the variation between needs at different stages that we identified in the content review.

Postgraduate Researcher and Career Development

Screenshot of the Postgraduate Researcher and Career Development homepage. There are cards on the homepage reading Explore our PGR workshops, Find development for every stage, and Not sure what training you need?

In a similar way, the new Academic Skills homepage leads with the priority content we identified in the review. Study Hub is given the most prominent location at the top left of the screen on desktop, and at the top of the screen on mobile. Cards for workshops and one-to-one meetings show the support services that are available to students. Elsewhere on the page, students can find support for topics such as writing, making notes, literature reviews and exam preparation.

Academic Skills

Screenshot of the Academic Skills homepage. Cards on the homepage are titled Visit Study Hub, Browse our workshops, and Book a one-to-one.

Reflections on this work

This work was a great example of how you can take an evidence-informed approach to content strategy when you’re working to a tight deadline. It also showed how you can use a website migration as an opportunity to review the content you have and think about how it supports your service. By drawing on existing knowledge about users, and testing ideas and prototypes with them, the teams were able to make decisions about their new websites with user needs in mind.

If you’re reviewing your content

If you’re thinking about reworking what you have on your website, get in touch. The User Experience Service can help you to evaluate what you have, develop your content strategy and bring user research into the process.

Contact the User Experience Service

How we helped the Institute for Academic Development to establish user needs for their website

28 October 2026 at 16:26

This summer, the User Experience Service worked with colleagues from the Institute for Academic Development to review their content ahead of a website restructure. In this post, we look at how we developed a shared understanding of user needs to help guide this work.

Supporting the migration of IAD content

At the end of the academic year 2025 to 2026, the services performed by the Institute for Academic Development (IAD) moved to different areas of the University. As part of this change, the IAD website was being shut down.

Content from the IAD website was moving to four new sites:

In June 2026, there were 900 published pages on the IAD website. Time was tight, with the content needing to have moved to its new location by August.

Members of the User Experience Service (Emma Horrell, myself, and interns Hannah Watson and Shlok Gupta) worked with colleagues from the IAD to prepare for this move. In this post, I’ll outline how we worked together to establish who uses the content and what user needs it supports.

We ran two online sessions to identify service users and their tasks

In a content review, we typically start by working out who’s using the site and what they’re trying to do when they arrive at it. It’s also useful to know what kind of events trigger people to visit the site and what information is likely to be most valuable to them at that point.

To answer these questions, Emma Horrell and I ran two online sessions with colleagues who were familiar with the existing content and who would be involved in creating the new sites. We wanted to draw together existing knowledge about users of the IAD’s services so we could establish what these users need from the IAD website. Each online session brought together a small group of specialist staff. We met over Teams and used Miro to gather the information.

Session 1: Postgraduate research students

In the first session, we focused on content for postgraduate research (PGR) students. Through discussion, it became clear that this audience group has shifting needs as they complete their programme of study.

We grouped the student needs on Miro and three stages became evident:

  1. They become a PGR student
  2. They get started with their PGR programme
  3. Later in the programme
Screenshot of Miro showing three circles with sticky notes in each one. Text on the sticky notes is too small to read.

We collected user needs and grouped them into three stages.

New PGR students have distinct needs

We learned that new PGR students might hear about the University’s academic development services in Welcome Week or in a conversation with their supervisor.

At this early stage in their programme, their tasks might include:

  • find workshops that are relevant to me
  • sign up for newsletters that tell me about future workshops
  • learn what I can expect from my upcoming programme of study
  • connect with other PGR students at the University of Edinburgh

PGR student needs change as they progress in their studies

Later in their PhD, these same students will likely have different needs. For example, they might be looking for a particular workshop that will help them to:

  • write a dissertation
  • put together a literature review
  • prepare for a viva

They might also be thinking about what comes after their PhD and what they need to do when they take the next steps in their career.

Some tasks apply at all stages of a PGR student journey

At all stages, PGR students could have these needs:

  • find out which services support academic skills development
  • find out what these services do
  • engage with these services in the event of questions
  • find out what’s on (workshops, support sessions)
  • get updates about upcoming workshops (for example through a newsletter)
  • access policy and standards information

At times, PGR students may also need to know about other University services that can support them. For example, Edinburgh Research Office and Edinburgh Innovations can provide support with funding applications. The Student Counselling Service can support with health and wellbeing issues.

Presenting available workshops was the priority

Our discussions made it clear that presenting information about workshops was going to be the top priority on the new site for PGR students. On the IAD website, workshops were presented in a variety of ways:

  • in an A to Z list
  • listed by theme
  • on a page called “At a glance – workshops this month”
  • in an embedded PDF brochure

Session 2: Users of academic skills content

Alongside this work, other IAD staff were preparing content for the new academic skills site. This would have a different purpose to the site for PGR students, and it would be pitched at a wider audience of students at all stages of study.

An online session helped us to understand user needs

We ran a second session with a small group of IAD colleagues to learn about the existing academic skills content. Specifically, we wanted to know:

  • who uses academic skills content
  • how they arrive at it
  • what they need from it

As in the first session on postgraduate research students, we gathered together known user needs and looked for common themes.

Screenshot of sticky notes on a Miro board. Groups of sticky notes are titled Writing, Workshops, AI, How to get in touch, Exams, Wellbeing, Finding literature and Planning and organising time.

We used Miro to collect the needs of students looking for academic skills support.

Through these discussions, we developed some scenarios to illustrate how a student might arrive at the site. For example:

An undergraduate student gets a poor grade for an assignment. They speak to their student adviser about how to improve their essay-writing skills. The adviser directs them to the IAD. The student goes on the IAD website to look for resources or workshops about essay-writing.

By thinking about user tasks in this way, we developed our understanding of what it might be like to be a student scanning the homepage, looking for content that will help them to complete the task they have in mind.

We also established that the priority for the new academic skills website would be content that supports the following:

  • Booking on a one-to-one study skills consultation session.
  • Finding a study skills workshop.
  • Finding online resources to support study skills such as writing and presenting.

Understanding student users and their priority content like this gave us a foundation for what we needed to do to assess the site and consider alternative designs.

The sessions uncovered a need for testing

Through these two sessions, we collected existing understanding of who was using the IAD website and what they needed from it.

This led us to the next stage of this work. We wanted to know what it was like for these users when they interacted with the site. Could they find what they were looking for? What might be the best way of organising this content on the new sites?

To answer these questions, we carried out two sets of user research:

  1. To support the work developing content for PGR students, we joined a Careers Service event at McEwan Hall to hear directly from those students, seeing how they responded to existing pages and some prototyped alternatives.
  2. To support the work developing academic skills content, we ran a short series of usability tests to observe students using the existing IAD website.

Read more about this work

This is part one of a two-part series. In the next post, I’ll explain how we used paper prototypes and usability testing to learn how users interacted with various site layouts.

Testing with users informed the Institute for Academic Development’s content migration

Architecting a new website to support dementia research at the University

23 October 2026 at 12:32

Alzheimer’s and dementia research is a flagship strength of the University.  Websites of different research units play a key role in supporting this work. The UX Service worked with the Alzheimer Scotland Dementia Research Centre to design and launch Dementia.ed, a new home for dementia research at the University.

The University of Edinburgh is internationally recognised for research on dementia and Alzheimer’s, with different research activities occurring across groups, labs, centres in and across the various Colleges. The team at the Alzheimer Scotland Dementia Research Centre had identified a need to join up different research activities, to ensure connections could be made across different research initiatives by facilitating an interdisciplinary University network.

A website was the proposed way to meet this need, with the intention that this site would provide visibility of the different research areas, to enable academic researchers to exchange knowledge and expertise within the wider dementia and ageing research community. The site was also anticipated to have a secondary, non-academic audience: people with a general interest in learning about and supporting dementia research.

With the go-ahead to build an EdWeb2 site confirmed, Angel Garmpi from the ASDRC contacted the UX Service for help to shape the new site.

Before creating a site, we thought through a content strategy

In the seminal textbook on content strategy, ‘Content strategy for the web’ by Kristina Halvorsen and Melissa Rach, the authors introduce content strategy as a way to avoid being tormented by a burden of excess content to be managed. Starting a site from scratch is a golden opportunity to make decisions upfront to prevent content spiralling out of control, leading to website bloat and content debt further down the line.

The framework in the book outlines four elements of content strategy:

  1. Substance – what content does the site need and why?
  2. Workflow – how does the content get created and maintained?
  3. Governance – who owns the site and is responsible for its content?
  4. Structure – how should the content be organised so it can be found?

These elements served as a useful way to tease out key considerations from the start, setting a path for good decision-making and planning for the longer-term, past the website launch.

Substance: Content for dementia researchers and for people interested in dementia research

By considering questions about what the site was for, and who would visit the site and why, we were able to establish the site substance.

The ASDRC team had identified five main purposes for the site:

  1. To facilitate a network where researchers could come to collaborate with others on research work
  2. To showcase and bring together the different groups, centres and parties involved with and supporting dementia research
  3. To be a source of information where people interested in dementia research could come to read about latest insights
  4. To serve as a volunteer hub to capture details of people wishing to participate in dementia research (or make tissue donations)
  5. To act as a payment portal where supporters of dementia research could make financial donations.

Using these purposes as a starting point, we defined primary and secondary site audiences and their associated tasks to flesh out detail of the site substance.

Site audience 1 (primary): Academic researchers working on dementia and ageing

Needs and tasks:

  • Meeting other researchers and groups working in related fields
  • Establishing peers to collaborate with and exchange knowledge
  • Getting support and help with grant and funding applications

Content to support:

  • Contact details of the different groups
  • An entry point to join the network
  • Ways/touchpoints to stay informed such as events

Site audience 2 (secondary): People interested in tracking dementia research developments

Needs and tasks:

  • Finding out about dementia research in relation to a specific condition of interest
  • Staying up-to-date with advances in specific areas of dementia and/or ageing research
  • Identifying relevant academic papers and publications to form the basis of journalistic content

Content to support:

  • Publications and updates about dementia research
  • News articles about topical research areas

Site audience 3 (secondary): People wishing to take part in dementia research

Needs and tasks:

  • Registering to donate brain tissue
  • Volunteering to participate in academic research studies

Content to support:

  • A place to register interest in becoming a research participant

Site audience 4 (secondary): People wishing to make monetary donations

Needs and tasks:

  • Donating money to contribute to the progress of dementia or ageing research

Content to support:

  • A portal where financial donations can be made

Workflow: content is curated and published by the ASDRC

Considering the site substance led us to think about where this content would come from – the sources and the subject matter experts behind it. All too often, websites are built and filled with content for a launch, but without mapping out the content sources and understanding the underlying creation processes, launch-day content is at risk of quickly going stale because there is no plan in place to maintain it.

To fulfil its primary purpose of facilitating dementia research networks, the bulk of the content for the Dementia.ed site was planned to come from the different University-wide dementia research groups and initiatives. This content would be captured as links to the different sources, to ensure it was current. Events from the different groups needed to be highlighted as network-forming opportunities, so these were planned to be pulled together in a single location on the Dementia.ed site by the ASDRC team. It was also felt that the site should provide a round-up of news from different areas, which again would be curated by the ASDRC team.  Finally, the site would include static content such as: practical information about the ASDRC and the dementia research network, contact details, information about how to join the network and details for how to contribute, either donations or by participating in a study.

Taken together, this meant the initial content-related work requirement from the ASDRC team would be: to create the static content for the site in the different sections and to establish the correct links for the different research groups. Going forward, there would be a maintenance required to check the static content and the links remained correct, and to produce events and news content, which all  seemed doable given resource in the ASDRC team.

Governance: ASDRC team owns the site and manages the content

Considerations of how the new site would be governed were related to the workflow processes. A prerequisite for obtaining an EdWeb2 site is the need for a named site owner to take overall responsibility for the site, and the same ASDRC team member responsible for creating, curating and maintaining the site content had been assigned the role of site owner. This kept things straightforward in terms of decision-making about the site’s content and overall direction, although there was a need for the site owner to forward-plan a content calendar for maintenance, curation and creation tasks, and to assign responsibility to other ASDRC team members as a back-up to avoid a single point of dependency.

Structure: content arranged under common user tasks

Starting the design of a new website from a blank canvas can be difficult as there are lots of questions to consider at once. What should the menu contain? What should be on the top of the homepage? How should the content link together?

Another core textbook useful in site building is ‘Information Architecture’ by Peter Morville and Jose Arango. In this book, the authors encourage thinking about how to group or categorise content (in an organisation scheme) as well as how to establish relationships between those groups or categories (in the organisation structure).

Typically, websites adopt ambiguous organisation schemes – with content arranged by topic, subject, audiences and/or tasks to encourage browsing and discovery. This approach was appropriate for the Dementia.ed site to enable it to support the different audience groups and their associated needs and areas of interest. We considered a task

For the organisation structure – a non-hierarchical flat arrangement made most sense. Given the site was anticipated to have a relatively small number of pages, and would have clear calls-to-action for the different audiences, it didn’t seem necessary to plan a heavily hierarchical structure. For the content in the different research group sites, a hub-and-spoke model could be adopted, with Dementia.ed acting as the central hub, linking off to the different sources.

Before building, we needed to sense check the proposed site map with users

With ideas for the site mapped out, it was tempting to just get building in EdWeb2. Before creating the new site, it was wise to test assumptions with some testing.

Usability testing – where audiences are given a task to perform online and are observed as they do it – always provides an excellent source of insight into how audiences naturally interact with a digital artefact like a website, how they make sense of the menu labels and use on-page content elements to find their way to complete their tasks.

When it comes to new sites, however, it can be difficult to know what to test with users. If you mock-up a prototype, which parts should you include and which can you omit? Asking participants to make sense of menu labels that lead to empty pages can feel unnatural, and setting participants tasks can fall flat if there’s no real-life site content where they can find the information they need to complete tasks authentically. All that said, it’s impractical to build out an entire site just for testing purposes, as it’s likely the testing will reveal ways it needs to change which can end up adding more work.

We used another research network site as a proxy to test with

Thinking through the options with the ASDRC team, we came up with a plan. The ASDRC team had started looking at other research network sites for inspiration and ideas about how to build Dementia.ed, so we decided to adopt one of these sites for the basis of a test.

We chose the Edinburgh Mental Health Network (EMHN) as a testing site. This site included top level menu items: People, Research, News, Events, Blog and Contact. It had a total of 13 main pages with additional pages within the News, Events and Blog sections.

Access the Edinburgh Mental Health Network website

Since the site supported researchers in mental health as well as audiences with a more general interest in the topic, we were able to shape a usability testing protocol to use the site to assess how two audience types sought to complete representative tasks:

Audience 1: Academic researcher wanting to join the research network

Representative tasks:

  1. Find out what the network is, and its goals and values
  2. Find out how to become part of the network and what this would entail
  3. Find out about upcoming activities
  4. Find research opportunities in the network
  5. Find out how to develop your research project and involve people with lived experience
  6. Find content you can use in support of a funding application

Audience 2: Non-academic with a personal interest in the research area

Representative tasks:

  1. Find out what research is being done across the network
  2. Find out how the network is managed
  3. Find out how to keep up with what’s happening in the network
  4. Find out how you can contribute as a research participant for studies
  5. Find out how to donate money to support the research

Some of the tasks mapped clearly to specific sections of the EMHN site, whereas others were more ambiguous – they could have been completed in multiple sections. In all cases, it was useful to see how participants approached the tasks, so we could use their expectations to design Dementia.ed in the most audience-focused way possible.

We learned which menu labels worked, and which didn’t

The results of the testing gave us a clear steer on which elements of the Edinburgh Mental Health Network site supported the different user groups completing their tasks and therefore would be a good fit to adopt in the new Dementia.ed site. The tests also showed areas where the approach of the EMHN site was lacking – and therefore where different structuring and/or labelling was more appropriate.

The Events and News sections worked well

To complete tasks about finding out about activities and keeping up with what was happening, participants naturally gravitated towards the Events and News sections of the EMHN site, where their expectations of finding events to sign up to and articles to read were met.

The EMHN site was lacking a specific place for information about the network

When working on tasks geared at finding out what the network was, what its goals and values were, and detail about how the network was run, participants looked for an ‘About’ section when they used the EHMN site. When they realised this didn’t exist, they tried multiple other locations including the homepage and the Research section. This suggested an ‘About us’ section would be useful to include in the Dementia.ed site.

The People section didn’t resonate as the way to become part of the network

The EMHN site presented information for academic researchers to join the network in a ‘People’ section, which also contained information about the management of the network as well as researcher support resources. In the tests, participants struggled to find this content when tasked with finding out how to join the network, suggesting that a more explicit ‘How to join’ section would be more helpful to support this key task.

The Research section was too broad to usefully support specific tasks

Test participants gravitated towards the ‘Research’ section of the EHMN site for various tasks: to find research opportunities, to find help with research project development, to find content to support funding applications, to find out how to be a research participant and to find out how to financially support research activities.

On arrival in this section, when they realised it only contained content detailing different research activities, they went elsewhere. This suggested the need to separate out content about research activities from content supporting specific research-related tasks and to label it accordingly. In other words, instead of having a large, general ‘Research’ section, opt for smaller, more specific sections such as: ‘Research areas’, ‘Participate in research’ and ‘Donate’.

The new site has a flat structure, with content arranged by topic and tasks

Keeping site of the content strategy work, and using the results of testing the proxy site to make key decisions about structure, the new Dementia.ed site was built and launched.

The site contains six main sections, adopting a mix of topics and tasks to signpost the different sorts of content. The ‘About’ section contains background information about the dementia research network, with a dedicated page bringing together links to the different research centres and groups in a hub-and-spoke approach. A ‘What’s On’ section combines pages to Events and News content. The other four sections are labelled in task-focused ways, to ensure relevant audiences can quickly get to the content they need to complete their tasks: Join the network, Get involved, Contact us and Donate.

To ensure audiences reach content in the most direct way possible, the content in each section is either available as a top-level page, or a sub-page, avoiding long pages and deep hierarchies which may confuse those visiting the site.

Access the Dementia.ed website

If you need help architecting your website, get in touch

From start to finish, the process to design and launch the Dementia.ed website took a few months, including a few meetings between the UX Service and the ASDRC team, some short usability tests and an overall site review.

The ASDRC team provided the vision of what they wanted to achieve, and subject matter knowledge of their audience base and their associated tasks. With this information, the UX team could apply expertise to translate goals into a user-centred website, which is manageable for the ASDRC team to maintain.

We’re happy to offer help, advice and support to other University teams. If we can help, please contact us through the UX Service website.

Contact the UX Service

We have reached a new threshold in genAI gloom, with a game dev cancelling a demo for fear of copycats ripping them off before release

16 October 2026 at 16:50

In what I suspect is the start of a trend, assuming it isn't one already, the creators of Drunken Goddess Reflux have yanked a planned public demo partly because they're concerned about people using generative AI to clone their game and release a copy before they even launch.

Read more

UX for real-world higher education – UCISA UX Community Day recordings now available

15 October 2026 at 09:03

If you design, build or manage digital experiences in higher education, the content from this year’s UCISA UX Community Day has plenty for you. The day included a panel discussion, case studies and practical advice from UX professionals, all focused on user-centred approaches in the university context.

As co-chair of the UCISA UX Group, a highlight of my year is planning and organising our annual UX Community Day, which sits alongside our regular webinars. Now in it’s third year, this all-day event is our flagship. It’s aimed at anyone striving to make digital products, services and platforms better for those who use them.

Read more about the UCISA UX Group on our UCISA webpage

Read more about previous UCISA UX Community Days in previous blog posts:

Growing our UX maturity by leading a Community Day for UK higher education institutions

Sharing and gaining knowledge at UCISA’s UX Community Day 2025

Eighty UX HE professionals sharing, collaborating and ideating: The magic of UCISA UX24

Clearly, I’m biased, but here are my top five reasons why this event is worth your time:

  1. It provides a safe-space, non-performative opportunity for higher education professionals to speak and share – to present ideas and work and gain feedback and input – no conference pressure, no vendors or suppliers, just a supportive community ready to listen.
  2. Depending on the UX maturity of your organisation, doing UX in higher education can be lonely at times, as UX practitioners can be outnumbered by other roles. Bringing user-centred folks together to talk openly about their UX work not only fosters welcome discussions, critique and questions, it also provides reassurance, boosts confidence and sparks new ideas to take forward for everyone taking part.
  3. It offers the chance for attendees to build and expand networks and in the process, get real-life practical help from those in-the-know. Not sure how to structure a workshop? Struggling to analyse your research data? Looking for some metrics to show impact? Show up and ask your questions – chances are, someone will be able to assist.
  4. Often said, but people make our universities what they are. Taking time out for this event, to specifically think about the digital experiences of those groups of people, and how we can work to make them better, is the right thing to do and is therefore time well spent.
  5. It’s completely free to UCISA members (which includes most UK universities). Need I say more?

So much for the plug. If you missed attending the event live on 26 September 2026, don’t worry, the recordings are now available. More details below.

This year’s theme spoke to UX trends as well as the broader state of the sector

Our chosen theme for the 2026 community day was UX for the real world: having lasting impact in higher education. This theme served a dual purpose. Firstly, it acknowledged how UX practice in higher education is changing: less by-the-book, more adaptable to the realities of the way things work in the ecosystem. Secondly, it captured the potential for UX to be a ‘north star’ – a prioritisation mechanism to bring clarity and direction to the sector at a time when change often has to happen fast, decisions need to be made quickly and therefore unpredictability is rife.

The theme therefore worked at two levels:

  • Top down (strategic): it reflected a growing move to ‘do UX without telling me you’re doing UX’. In other words, treating UX as part of how the organisation already works, rather than as a separate function.
  • Bottom up (practical): it spoke to the need for UX practitioners to be opportunistic and adaptable in the midst of shifting conditions – for example, moving between short- and long-term priorities, bringing users and designers closer together, and keeping track of successes.

With this in mind, the overarching theme cascaded into five sub-themes:

  1. UX within the machine: Making UX happen relies on aligning with ‘how things work’ in your organisation – understanding how things actually get done in an organisation, and planning UX work to fit.
  2. Playing the long game: You’ve reached the end of the project or the initiative, but now what? Projects are often short term, so how do we keep UX going once they end?
  3. Putting numbers on it: How have you demonstrated the impact of UX in ways decision-makers understand? Making the case for sustained UX means showing its value, including in numbers.
  4. Designing with, not for: Co-designing with students, staff and other audiences – creating a more direct link between user needs and user-centred design.
  5. AI in UX: Beyond the chatbot: AI is everywhere – but how is actually being used in UX practice? Using AI as a tool to support UX work, and recognising its growing role in shaping user experiences.

With the theme set, we went public, we started accepting speaker proposals and opened the event for sign-ups in July, ahead of the event date on 16 September 2026.

The event was met with a positive community response – from the proposals, to the sign-ups to engagement on the day

A real test of a theme is the speaker submissions and the response was strong, particularly for the ‘UX in the machine’ subtheme. It’s always a great privilege to work with the UCISA events team and fellow committee members to select and sequence the sessions and to curate the schedule for the day. We aimed for a balance of themes, talks that would appeal to seasoned UX practitioners and newcomers alike, with a mix of formats. Taking on board feedback from previous events, we also built in time to pause, reflect and interact.

The event attracted nearly 200 registrations from UCISA members, with over 100 people from 49 institutions attending on the day. It was interesting to see a split across job roles of attendees. As expected, UX/UI design and content roles were the best represented. But the audience stretched well beyond them, taking in leadership and strategy, digital learning and education, as well as technical and systems roles. We were also joined by people working in digital experience, engagement and communications and people in library services and data and accessibility positions.

I’ve often found activity in the shared chat to be a good gauge of the success of an online event. On the community day, the Teams chat was lively from the start, with people introducing themselves at the start, then going on to share comments, questions and resources, right up until the event closed at 4pm. Even once the event was over, messages were being exchanged to set up follow-ups, suggesting the day had succeeded in bringing the community together over shared goals and challenges.

Watch the recorded sessions in order, or just pick those of interest

There’s nothing quite like attending a community event live to experience it as it happens and to be part of the conversations in your own way. That said, it’s not always possible to take a day out of the working week, so thankfully UCISA records the event and makes the recordings available through the UCISA Connect portal (free to access for all UCISA members).

Access the recordings through UCISA Connect portal (log in required)

You’ll find the recordings available in two slots – one morning and one afternoon. Underneath the recordings, you’ll also find slide decks provided by the speakers to help you follow along in your own time and revisit specific topics of interest.

Here’s a synopsis of each of the sessions to guide you through:

UX Within the Machine: Making user experience work inside complex institutions (Sam Fanning, Director of Digital Experience at University College London)

Long-standing UX community contributor Sam Fanning shared how UX works at UCL. She covered UCL’s product delivery model, how the digital experience team is set up, and how they measure the success of their UX service. Sam also explored how UX can get involved earlier, and the challenge of managing dependencies between the SaaS products and bespoke builds that underpin many UCL services.

How usable is it, really? When UX evidence starts to add up (Juliana Matos, UX Manager, King’s College London)

Juliana shared her experience of tackling a long-term UX problem: demonstrating impact through metrics. She discussed sample sizes, the familiar ‘five users is enough’ rule, and the difficulties of producing statistically significant numbers. Using the Moodle VLE as a case study from King’s, she showed how the team applied the well-established System Usability Scale (SUS), and why hearing directly from users was necessary to add qualitative depth to the scores.

‘Clearing’ a path through the chaos: transforming operational processes one-on-one (Jen Doyle, Senior Content Designer (Content Operations), University of Edinburgh)

Improving a key stage of the student journey is something anyone doing user-centred work in higher education can relate to. Jen Doyle described how she and her team analysed each stage of the Clearing process at Edinburgh, looking for ways to improve the content and streamline the processes behind it. They were able to make changes and improvement resulting in easier, more efficient updates for staff and a more consistent experience for everyone.

UX within the machine – panel discussion (Chaired by Emma Horrell, UX Manager, University of Edinburgh, Panellists: Sam Fanning, Juliana Matos and Neil Allison)

 Clearly I’m biased (again), but this 30-minute panel flew by and is well worth revisiting, even if you caught it first time round. Sam, Juliana and Neil described what ‘the machine’ looks like in their organisations, sparking ideas for making UX fit. They shared how they prioritise UX resource, show impact, and win buy-in and championing from the top, along with honest reflections on what has and hasn’t worked and advice for people new to the field. If you’ve ever wondered how to get UX applied where you work, there was plenty to take away.

Designing for students: Using quantitative UX research methods to design a new VLE student experience (Adam Ellison, Phil Tubman and Stephen Owens, all from Lancaster University)

The team from Lancaster shared a case study on improving the UX of their VLE, tackling inconsistent structure, content overload and unclear navigation. For me, this talk was a welcome chance to revisit how my own UX Service approached work on Learn, the primary VLE at Edinburgh. It was a chance to learn from Lancaster’s experience, and join a wider conversation about why VLEs deserve more UX attention.

Designing the Digital Journey to Wellbeing Support: Co-creation in Practice (Holly Thomson and Jade Alexander, User Researchers at the University of Glasgow)

Holly and Jade shared how Glasgow co-designed Wellbeing Home, a one-stop shop for wellbeing services, and Support Finder, a self-triage tool, working together with students with lived experience. They described how they used card sorting and a build-your-own homepage activity to work out how to organise services in ways that made sense to students and explained how they tested designs based on students’ real-life needs and scenarios, to ensure every user journey had clear steps for students to follow. They concluded with tips on making co-design work in practice.

AI in UX. Beyond the chatbot (Paul Boag, Boagworks)

UX expert Paul Boag shared practical ways to get more value from user research data using AI. Drawing on examples, he shared how feeding AI forgotten reports, surveys and slide decks on can surface fresh patterns and insights, and can shape virtual personas. He also revealed how AI can highlight gaps, to signal where more research is needed. His talk sparked discussion about the importance of being transparent when using AI to analyse and apply research data.

Exploring AI and the UX process (Madeline Linnell, Website and Application Developer, Oxford Lifelong Learning, University of Oxford)

Madeline shared the process her team at Oxford followed to develop an AI-assisted way for users to discover courses on the Lifelong Learning website. She covered the research process (including use of AI tools such as Google AI and Cursor) the ideation phase (using AI to brainstorm creative ways to discover academic learning opportunities), prototyping (using Google AI to generate interactive screens from static files) and user testing (using AI to analyse the findings), concluding with what the team learned and their plans for implementation.

Workshopping essentials: the fundamental principles for inclusive, democratic engagement and design (Neil Allison, Head of Prospective Student Web, University of Edinburgh)

Neil gave a practical talk which served as a primer on designing workshops. He unpacked when something should be a workshop rather than a meeting or an email, with workshops best suited to collaboration, democratising decisions, generating ideas and prioritising. He explored how to strike the right balance of facilitation to guide people through the divergent, emergent and convergent stages, and shared examples of successful workshops he has run at Edinburgh.

Thoughts, suggestions, reflections? – reach out to me on email

A UXer through-and-through, I take my responsibility of organising a user-centred UX Community Day seriously – therefore I’m always looking for feedback to guide how we do things better. If you signed up for the UX Community Day, you will have received a feedback form. If you didn’t, or the window to complete the form passed you by, you can still share your thoughts by emailing me directly. Drop me a line at ehorrell@ed.ac.uk I would love to hear from you.

 

 

Your artwork could be featured in the next Debian release

9 October 2026 at 18:33

The Debian Linux project has opened a call for community artwork submissions ahead of the release of the upcoming Forky (Debian 14). If you think you've got the artistic chops, your art could appear on the boot screens, login prompts, and desktop wallpapers of millions of users. The submission deadline is November 26.

Continuing Debian's community-driven ethos, the artwork submission process mirrors that of previous releases. The artwork must feel distinctively "Debian," integrate cleanly without the need for core software patching, and remain visually appealing for the long term.

Elise Couper's "Ceratopsian" theme was chosen as the winning default for Debian 13 Trixie. For anyone who might not be up on the latest from the Toy Story franchise, the release names echo character names from the animated films. Trixie was a triceratops introduced in Toy Story 3, hence the "Ceratopsian" wink in the winning submission. It makes sense that the next version of Debian continues this trend with Forky, a character introduced in the franchise's fourth entry. The Debian team cautions against overly busy designs that may cause user fatigue, but if anyone can successfully incorporate Forky's googly eyes into the design somehow, know that you'd at least win the contest for my Debian desktop wallpaper.

Read full article

Comments

Nobody Wants Your Damn App

24 September 2026 at 15:57
Nobody wants another app cluttering their phone—so why does every website keep begging us to install one? The web already perfected the experience: click, load, done. Maybe it’s time we stopped trying to ruin it.

Steam snap using core26 is now available for testing

20 September 2026 at 20:01

Steam logo with Ubuntu logo inlaid and Snapcraft logo backgroundUbuntu gamers can help test a new version of Canonical’s Steam snap that uses a core26 base and an updated Mesa graphics driver stack. A new testing channel sees the Steam snap’s underlying base runtime bumped to a version based on Ubuntu 26.04 LTS, paired with a matching gaming-graphics-core26 content snap providing a newer set of GPU drivers – and potentially, better performance. Users can opt in by running snap refresh steam --channel stable/core26 from the terminal, and test by doing what they’d normally do in Steam: install and play games, adjust settings, and so on. Because the Steam snap uses its […]

You're reading Steam snap using core26 is now available for testing, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

❌
❌