❌

Normal view

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

Scottish Web Folk 2026: Humans vs Machine

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

You can read about my previous experience here:

Scottish Web Folk 2025: Challenging times, brilliant people

Old rules no longer apply

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

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

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

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

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

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

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

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

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

Digital practitioners have moved from theory to practice

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

Only thinking about human users can have unintended results

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

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

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

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

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

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

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

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

I look forward to applying new best practice

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

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

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

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

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

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

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

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

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

Or in other words:

Advocate. Defend. Decide.

MyEd updates – building for the future

20 July 2026 at 13:41

Last month we released more improvements for MyEd, the University’s web portal. We deployed updates to several key pieces of functionality, including Calendar, Notifications, Collaborate, Library and My finance. Although end users won’t see any changes in functionality, these updates are an important step in the work we are doing to make MyEd sustainable for the future.

Building a MyEd for the future

MyEd has been around for a long time. Some of the technical components it relies on are old, and need to be upgraded or replaced to make sure that MyEd remains reliable and sustainable. One of these is uPortal, the open-source application which provides the MyEd backend. Some of the functionality that relies on uPortal are the components that integrate with other University services and systems.  These include the email and calendar previews, the Library, Notifications and My finance, and are some of the most heavily used features in MyEd. These components use uPortal to securely connect to the APIs that provide data and services, and to control what users are allowed to access and do.

Planned changes to uPortal mean that we need to make changes to ensure that these components continue to work. Changes will also be needed if we decide to replace uPortal with a different technology rather than upgrading it.

We therefore decided to explore how we might redevelop our this functionality to make it less dependent on the MyEd backend.  This would mean that we would be ready for the changes planned for later versions of uPortal, and that it would be much easier to switch technologies in future if required. 

New opportunities and new approaches

From last summer MyEd has been using Microsoft Entra for authentication. The University has a central platform known as Choreo for integration middleware and publishing APIs.  Together, Entra and Choreo offer a solution to remove the dependency on uPortal for our integrations. The use of Entra and Choreo means that we are using technologies which are well understood at the University, and which also offer potential for re-use beyond MyEd.

Although both Entra and Choreo have been in use at the University for several years, using them for our components means using them in new ways. Decoupling from uPortal means that we can no longer rely on uPortal to manage authentication and authorisation. Instead, MyEd’s front end now uses Entra to authenticate users. Additional information in Entra access tokens is used to determine whether a users should have access to functionality within an component, and if so, what level of access they should have, and what information they should see.  In Choreo, newly developed services for MyEd handle the API calls to University or external services for the components. and make relevant information and functionality available to the user, according to the role based access controls that have been defined.

Implementation and success

Once the new architecture for components had been agreed, the process for updating them and testing the new approach could begin.

Although the changes are invisible to end users, they are significant, and we needed to do extensive testing to ensure no functionality was adversely affected. We also had to carry out load testing as this was a new way to use Choreo, and MyEd is a high use system.

As expected, we did encounter various issues along the way which had to be resolved, and some of these took longer to resolve than we would have liked, delaying our progress. However, we were able to find solutions, and successfully decoupled six of our most used integrations from uPortal.  These were updated on the live MyEd service in June, and have been very successful, with no issues arising post-deployment.

This work has been a key step forward for MyEd, significantly reducing our reliance on uPortal, and opening up MyEd to new opportunities, both technical and business related.

Information Resources Intern’s first lessons: Time to unlearn “I like the look”?

By: Fan Fei
30 June 2026 at 16:12

My time at the Forrest Hill office as an Information Resources intern began four weeks ago under Edinburgh’s summer brilliance. Working as a part of the Portal Services team, I am responsible for creating and improving existing information resources about MyEd (the University’s online portal), including editing EdWeb2 pages, producing instructional videos, and refurnishing help and support SharePoints.  

Experiences designing promotional graphics, videos and syllabi for societies and events since high school made me a veteran of CapCut and Canva. It didn’t take me too long to get the gist of less familiar platforms like SharePoint and EdWeb2 (the University’s content management system) either, thanks to the self-paced online training courses. Freshly equipped with all the essential tools, I hit the ground running with high spirits. Like in any independent projects and commissions I did before, my creative visions, personal judgements and the mere intuition of “I like the look” carried me through the planning and proposal stage. I audited the existing EdWeb2 pages about MyEd to propose improvements, planned the refurbishment and new structure of the SharePoints, and storyboarded for the upgrade of the “How to use MyEd” video. Everything progressed beautifully smoothly and swiftly. The big frameworks and ideas were set up and ready to go.  

 

When “I like the look” starts to fail  

But as they say, the devil’s in the details; mine was waiting right around the corner at the execution stage.  

I was the most ambitious and eager with the upgrade of the “How to use MyEd” video, as it would be my first time creating official video for an organisation rather than for smaller commercial causes. My initial aspiration for upgrading this video was to make it as eye-catching and engaging as the promotional videos made by big companies like Substack: intricate transitions, animations, and rich colours. I wanted it to not only be informative, but charming enough to excite the new students about university life and this new portal system they’re starting it with. I spent nearly a week adapting to the PC version of CapCut, learning new transition techniques, and adjusting the properties of millions of key frames for about the millionth time until the movements are natural and the timings are perfect. With fondness and personal satisfaction towards the visual, I submitted the first draft for review.  

My manager responded:  

“Have you reviewed it with the accessibility checklist?” 

That’s when the design I was so proud of began falling apart like a house of cards. It became clear to me the first time that I’m no longer designing resources for a class of 30, but a community of 53,000+ students within a large institution. “I like the look” hardly stood valid against objective, rational standards like the WCAG (Web Content Accessibility Guidelines) and the University’s editorial guide for effective digital content. The sliding animations I designed turned out to be rather disruptive, as they create moving backgrounds under the text. This compromised the minimal contrast requirement (as text might blur into background) and created more challenges for users with attention or vestibular disorders. After re-reading the WCAG sections on video accessibility, I reduced the speed and frequency of motions on screen, avoided all-caps titles (which troubles users with dyslexia), and carefully checked font size and color contrast section by section.  

Around the same time, I came across Katie’s wonderfully illuminating blog on when videos and images genuinely add value to digital content: 

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

Although the blog was more about websites, its message inspired me to remove stock footage in my videos, which I previously employed for pure aesthetic reasons to make sections appear less static. Not only did they not add much informational value, but they also increased the video file size and created more moving backgrounds that hinder accessibility.  

Another lesson came through collaboration. Unlike society and event projects where I made every creative decision myself, this video formed part of the Pre-arrivals team’s “How to” series and therefore needed to follow an established visual identity. I will need to adapt the current draft to their prescribed templates, formats and requirements. With the same logic of branding in mind, I also replaced all colors in the video with colors from the University’s official branding palette. This way, in the long term, it could seamlessly fit into university websites, whether uploaded to Media Hopper or embedded into EdWeb pages.  

It would be dishonest to say it wasn’t a little heartbreaking to undo and cut work I had spent hours creating. Nonetheless, I came to understand that information resources differ from creative projects exactly because clarity, effectiveness, and accessibility must always come before visual aesthetics. I began seeing various guidelines and requirements less as constraints. They taught me a more rational and methodical approach to creating information resources than relying solely on the easy intuition and judgement of “I like the look”. Where I designed with my own palate and assumptions before, now I truly began my journey of designing for others. 

 

But does “I like the look” truly have no merit at all?  

Surprisingly, I would argue that it still does. “I like the look” is not something to unlearn completely, but it should be treated as the beginning rather than the end of the design process. From a different perspective, I have come to think that that instinctive thought is where UX (user experience) thinking begins. 

When I first opened the Notifications Service SharePoint that I was supposed to redesign, my immediate reaction was “I don’t like the look.” Except this time, rather than concluding the thought and jumping straight to redesigning based on personal preference, I attempted to find a rational “Why” by referring to all the guidelines and effective digital content tips I have learnt.  

The SharePoint was comprehensive, containing all the information staff would need to understand what notifications are and how to send different types of notifications. Yet as a first-time user that knows near nothing about the Notifications Service, I found it difficult to know where to begin. The original homepage was filled with large blocks of text and links with equal visual weight regardless of importance; Navigation of all the pages and materials relied heavily on users have prior knowledge on terminologies like “Notifications Template” and “Emergency Notifications”, and there was little visual hierarchy to guide attention or suggest the next step.  

That’s when I realised when users say they “like the look” of a website, they are often responding to not just colours or typography, but how intuitive, organised and effortless it feels to use. I decided not to simply edit the existing pages, but to rebuild the site’s structure in a separate testing environment.  

For instance, instead of letting the homepage act as a page of plain text, I plan to make it a clearer starting point for all types of users. I intend to include an image of Notifications Backbone (the system used to send notifications) alongside a direct button to access it. This way, experienced staff can access the system immediately, while first-time users are given some introductory visual and textual context before they continue exploring the site. The content changes minimally; my focus is to reorganise them around users’ journeys. Similarly, rather than presenting users with a long list of pages whose titles assume prior knowledge of relevant terminologies, I plan to reorganise the content into a small number of category cards based on what potential tasks users are trying to accomplish. I also hope to introduce a clearer hierarchy within the navigation menu, so that related pages are grouped more logically, and any information can be found more intuitively.   

Original homepage  v.s. New draft hompage 

  

Original information list  v.s. New draft categorisation  

New draft menu bar  

Being a student unexpectedly became an advantage in this process. Since I had similarly little prior knowledge of the Notifications Service as a new user, every point where I became confused while visiting the original SharePoint highlighted somewhere a common struggle might occur. Looking at the site with fresh eyes helped me identify problems that familiarity can sometimes hide. 

 

From “I like it” towards “We like it”  

But of course, just as I learnt with the review of the MyEd video draft, the work does not end once I think the design “looks right”. Everything I design  – SharePoint, websites, and videos – still need to be checked against the accessibility standards, follow editorial and branding guidelines, and most importantly, be tested with the people it is actually designed for (e.g. test MyEd video with students, the Notifications SharePoint with staff). Nick’s excellent guide on running usability tests has been particularly helpful in shaping how I plan to continue with the next steps.  

How to run a usability test – Website and Communications Blog 

“I like/dislike the look” has carried me through countless creative projects before. Four weeks later, I don’t think that instinct has been unlearnt but simply found its proper place. Rather than a justification for me to blindly follow personal preference and biased judgements, it has become the starting point for me to ask better questions about accessibility, usability, and the needs of the people I’m designing for. That is the perspective I’ll continue carrying into MyEd information resource that I will continue to create and develop throughout the rest of the internship.  

 

 

❌
❌