❌

Normal view

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

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

What I learned at UX Scotland 2026

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

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

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

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

The challenge: dividing up content and naming groupings

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

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

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

OOUX involves favouring nouns over verbs

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

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

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

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

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

The City of Edinburgh Council:

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

West Lothian Council:

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

 

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

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

Renfrewshire Council

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

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

City of Sydney

OOUX helped Renfrewshire Council to create templates

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

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

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

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

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

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

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

And on the ‘Graffiti’ page, you have:

  • Before you report it
  • How to report it

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

My reflections on how templates could work at Edinburgh

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

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

Other highlights

Sara Wachter-Boettcher on burnout

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

Sara Wachter-Boettcher

Craig Abbott on AI and accessibility

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

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

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

Craig Abbott

James Chudley on digital sustainability

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

James has posted his slides here:

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

Another great conference

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

UX Scotland

❌
❌